Ensure app deploys work as expected on Fly.io machines #475
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
gerhard
force-pushed
the
migrate-app-to-fly-machines
branch
from
6415118
to
ec2cf79
Compare
gerhard
changed the title
gerhard
force-pushed
the
migrate-app-to-fly-machines
branch
from
ec2cf79
to
464e4a9
Compare
|
@jerodsanto we are now running 2 instances of our app. Everything is OK. flyctl status
App
Name = changelog-2022-03-13
Owner = changelog
Hostname = changelog-2022-03-13.fly.dev
Image = thechangelog/changelog-prod:2c261662860cd0062c8d91a065d11ac0a89cb2ec.dev
Platform = machines
Machines
PROCESS ID VERSION REGION STATE ROLE CHECKS LAST UPDATED
app 1857264a157478 286 iad started 1 total, 1 passing 2023-07-15T10:50:18Z
app e784457f422618 286 iad started 1 total, 1 passing 2023-07-15T10:50:48Z |
Following the migration to machines, we needed to make sure that:
- deploys work as expected
- 👍 all good since bluegreen is now supported:
https://community.fly.io/t/finally-bluegreen-deployments-for-appsv2/13851
- there is an extra app instance - `flyctl scale count 2` did the trick
- 👍 we are now running 2 app instances, no request degradation or
error traces in Honeycomb.io, and no new exceptions in Sentry.io
- existing `fly.toml` is valid
- 👍 yes, the config works fine for machines, only tweaked a few values
All in all, this was much smoother than expected. All merit goes to Fly.io 💪
Other improvements:
- bump `flyctl` to latest
- bump `dagger` to latest-1 (waiting for
dagger/dagger#5450)
- fix local deploys
- yes, we still have the option to deploy straight to production from local 💚
Next step: migrate PostgreSQL manually & upgrade to latest `14.x` while at it.
Signed-off-by: Gerhard Lazu <[email protected]>
gerhard
force-pushed
the
migrate-app-to-fly-machines
branch
from
464e4a9
to
4586f51
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.
Following the migration to Fly.io machines, we needed to make sure that:
flyctl scale count 2did the trickfly.tomlis validAll in all, this was much smoother than expected. All merit goes to Fly.io 💪
Other improvements:
flyctlto latestdaggerto latest-1 (waiting for 🐞 Some operations stopped caching since 0.6.3 dagger/dagger#5450)Next step: migrate PostgreSQL manually & upgrade to latest
14.xwhile at it.