feat(app): configurable Modrinth endpoints through .env files #4015
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Gaming32
reviewed
Jul 17, 2025
Gaming32
approved these changes
Jul 21, 2025
IMB11
pushed a commit
that referenced
this pull request
Jul 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
These changes make the API and website endpoints used by the Modrinth app to referring to Modrinth services configurable through a
.envfile located atpackages/app-lib, which is read at compile time. This brings the app environment configuration method in line with that used by the frontend and Labrinth.As a result, developers can easily test any combination of Labrinth backend and frontend directly from the app without modifying any source code. Additionally, build workflows now clearly have to define which environment the app is using, allowing them to select the staging environment when appropriate.
After this PR is merged, a
.envfile must be present atpackages/app-libwith the appropriate variables in order to build the app. You can initialize a suitable.envfile with a command likecp packages/app-lib/.env.prod packages/app-lib/.env.