-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploying changes from staging #2966
Merged
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
Removed a lot of retry/reconnect logic from ApiHandler and ChainData, as it was spawning a lot of PJS instances, which also handling reconnects on its own. This change also properly adpots the idea of talking both to relay chain and to parachains, depending on queried data. With new logic, each ApiHandler instance governs an interface to a single chain, where it can switch endpoints and do reconnects on its own. `ApiHandler.getApi()` returns a PJS instance that should work, and will block in case we're reconnecting. PeopleApi endpoints now live in configs, instead of being hardcoded. Instead of passing around ApiHandlers, passing a ChainData instance now, as it contains both ApiHandlers instance now, and as it is an intended abstraction for it
apiPeopleEndpoints in kusama configs
releaseTagFormat is configurable
ApiHandler / ChainData refactoring
[Chart] Removal of default values of resources
* Removed Dockerfiles in all auxiliary packages * Removed entrypoints (e.g. run.ts) in all auxiliary packages * Removed Dockerfile-dev's, as they served no purpose * Removed esbuild and build:prod commands, as they weren't used in production setup * Removed worker package, as it's not used in monolith setup * Removed everything regarding redis * Removed docker-compose.yml and docker-compose.microservice.yml (docker-compose.current.yml became docker-compose.yml) * Removed configs for microservices setup * Updated docs
Querying decimals instead of hardcode
Dropping microservices setup
Master sync
Fix min rank message
* Removed esbuild leftovers * Nodejs upgrade * Removed bullmq and bullboard, as a leftover from microservices setup * Removed unused dependencies * Upgraded turbo * Sorted out deps/devDependencies placement * Fixed turbo codependence: sometimes we had failed builds because `common` package wasn't built yet when `core` was building
This way, `yarn test:all` works locally as well. Also removed old test commands from `core`, as there's no jest and no tests.
By splitting build into two stages, we'll take only docs/build into the layers. `yarn workspaces focus --production` removes all devDependencies, which also aren't needed after build. `date-fns` wasn't specified in deps at all, but needed at runtime. Fixed. The result: image went from 1.26GB to 472MB
Deps upgrade/cleanup
Making docker image thinner
ironoa
reviewed
Jun 14, 2024
PJS upgrade
Fixed wrong Kusama endpoint
bump versions
ironoa
approved these changes
Jun 14, 2024
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.
No description provided.