-
Notifications
You must be signed in to change notification settings - Fork 891
chore: deploy workspace proxies on fly.io #10983
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
Conversation
TOKEN_PARIS: ${{ secrets.FLY_PARIS_CODER_PROXY_SESSION_TOKEN }} | ||
TOKEN_SYDNEY: ${{ secrets.FLY_SYDNEY_CODER_PROXY_SESSION_TOKEN }} | ||
TOKEN_SAO_PAULO: ${{ secrets.FLY_SAO_PAULO_CODER_PROXY_SESSION_TOKEN }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fly.io doesn't have a way of adding secrets in their dashboard?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They do have but I prefer we store all secrets in GitHub Actions. I can move if you disagree.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you use --env
on the flyctl command does it store the secrets in plain text visible on the fly.io dashboard? If so then we should probably move them to secrets on fly.io instead of GH
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fly.io has no environment section on the dashboard, so they do not appear anywhere.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
meant to approve that, please see comments above
Co-authored-by: Dean Sheather <dean@deansheather.com>
This pull request adds a new job called
deploy-wsproxies
thst is responsible for deploying the workspace proxies to the fly.io platform. The deployment is triggered only when the pull request is made from themain
branch.The
deploy-wsproxies
job updates our workspaces proxies in 3 fly.io regionsThis pull request ensures that the proxies are up-to-date with
main
btanch.