github: Deploy to prod and stage on merge to main #231
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
Improve regexp in href/URL replacement deploy script. There is no functional change.
juliaogris
force-pushed
the
housekeeping
branch
from
08835bc
to
bb135e8
Compare
|
firebase-deployment for 85b525c |
Deploy to prod and now also to stage on merge to main. We do this via separate GitHub environments: prod and stage and different GitHub actions job using different `FIREBASE_SERVICE_ACCOUNT_EVY_LANG` secrets wired to the corresponding firebase prod and stage environments. When the CI job (not the release job!) is run on `main`, rather than pull-request, we deploy to https://evystage.dev and its live channel, rather than the PR preview channel. We don't post preview channels to any PR. This is done via updates to the firebase-deploy script. Issue: evylang/todo#46
juliaogris
force-pushed
the
housekeeping
branch
from
bb135e8
to
85b525c
Compare
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.
Deploy to prod and now also to stage on merge to main. We do this via
separate GitHub environments: prod and stage and different GitHub actions
job using different
FIREBASE_SERVICE_ACCOUNT_EVY_LANGsecrets wired tothe corresponding firebase prod and stage environments.
When the CI job (not the release job!) is run on
main, rather thanpull-request, we deploy to https://evystage.dev and its live channel,
rather than the PR preview channel. We don't post preview channels to any
PR. This is done via updates to the firebase-deploy script.
While at it, add a minor, non-functional improvement to sed expression in
firebase-deploy script.
I've setup stage and prod GitHub environments
prodandstageseparately viaclicky-clicky-admin, hopefully using the correct Firebase Service Account secrets
and the correct branch protection rule for prod.
Fixes evylang/todo#46