feat: added configuration to use a local token registry #873
Conversation
This file contains 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
…t 8080, so switched to 8091
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.
Context
The global token registry has a limit of how many requests can be send. This leads to long resync times, if all assets are needed. To avoid that I want to introduce a local token registry. This solution won't suffer from any limits, since the sync can be done locally.
Proposed Solution
Adding the Token Registry to an additional docker-compose file, so the user can choose which to use. The background service will then start syncing everything from the local registry.
In a future PR it could be possible to directly use the database within this application to avoid syncing twice, but for now this will help and solves the issue regarding the limits.