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.
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.