faucet-api/env-vars/demo.secrets
Setup is ONLY for dev
Setup pure proxy to sign transactions (whitelisting & transfer tokens).
/initProxies
to create the pure proxy, fund it, and give it sufficient permissionsMEMBERLIST_ADMIN_PURE_PROXY
(onboarding-api) and REACT_APP_MEMBERLIST_ADMIN_PURE_PROXY
(centrifuge-app)To add other repositories to this monorepo while preserving the Git history, we can use the following steps: https://medium.com/@filipenevola/how-to-migrate-to-mono-repository-without-losing-any-git-history-7a4d80aa7de2
To set a pool into maintenance mode, add the pool id to the environment variable NEXT_PUBLIC_FEATURE_FLAG_MAINTENANCE_MODE
.
To make sure repository admins can control the full workflow of our apps to production safely this repository provides the following flow:
Opening a new PR will deploy cent-app using the PR number to app-prXXX.k-f.dev - There should be a comment with these links in your PR after deployment. Forks do not trigger a PR deployment
Merging code into main
will deploy buckets and functions pointing to: app-dev.k-f.dev
Demo deployments must be manually triggered. They are not required for the release process.
Catalyst deployments are triggered by pushing a tag containing centrifuge-app-v*
in the tag name.
Altair and staging are triggered by creating a pre-release
on the Github repository
Centrifuge is deployed by editing an existing release and unmarking pre-release
to fully release it, it will promote the staging artifacts to app.centrifuge.io
Using the github release manager the pre-release can be promoted to production (app.centrifuge.io) using the artifacts generated in the pre-release. The production release must be approved by a reviewer.
(Coming soon: release web-bundle to IPFS)
You can follow your deployments by going to the Actions section of the github repo
HackMD docs: https://centrifuge.hackmd.io/MFsnRldyQSa4cadx11OtVg?view
More info on our release process rationale can be found in our HackMD (Private link, only k-f contributors)
-> Deploys to app.staging.centrifuge.io and app.altair.centrifuge.io
Navigate to create a new pre-release. Make sure to tick the pre-release
option.
centrifuge-app-vX.YY
tag on the release screen. Only tags starting with centrifuge-app-v*
will meet the requirements for deployments:
CentrifugeApp vX.X
Set as a pre-release
checkboxPublish release
to trigger the build. You can follow progress on the Actions dashboardWhen the deployment is finished a notification will be sent to the #eng-apps channel on Slack.
-> Deploys to app.centrifuge.io
The deployment to staging from point 1. needs to have been finished first. The production deployment uses the artifacts generated in the pre-release.
Navigate to the release summary and select the pre-release you want to publish.
Set as a pre-release
checkbox and then tick the Set as the latest release
checkboxUpdate release
to trigger the prod deployment. As with the pre-release, the production release must be approved by a reviewer.When the deployment is finished a notification will be sent to the #eng-apps channel on Slack.