Enable changelog.com devs to create prod db forks with a single command #508
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 507 is merged. Will you do a quick rebase of this branch so it's easier for me to grok its unique changes? |
Elixir 1.14.5 installed was segfaulting on macOS 12.7.3 ARM. Installing the Elixir `otp26` variant didn't fix it. Maybe an asdf issue... Will try again another time. Signed-off-by: Gerhard Lazu <[email protected]>
This is the next logical step after migrating to Neon.tech part of #492 cd changelog dagger call db-branch --neon-api-key=env:NEON_API_KEY To learn more, see `changelog/README.md`. Part of this, we also deployed a Dagger Engine v0.10.3 on Fly.io so that we don't need any sort of container runtime running locally. I know that Jerod will appreciate this. The beginning of a new generation of tooling, I'm sure of it. Signed-off-by: Gerhard Lazu <[email protected]>
|
Done! |
gerhard
added a commit
to gerhard/changelog.com
that referenced
this pull request
Nov 29, 2024
just dev-with-neon-branch gerhard-2024-11-29
To create a new Neon branch, run:
just neon-create-branch
All the new commands that go well together:
[team]
dev-with-neon-branch branch # Run app in dev mode with $branch
neon-branch-connection branch *ARGS # Show $branch connection details
neon-branches # List prod db branches
neon-create-branch # Create a new branch off the prod db
This is a follow-up to:
- thechangelog#533
- thechangelog#508
Signed-off-by: Gerhard Lazu <[email protected]>
gerhard
added a commit
to gerhard/changelog.com
that referenced
this pull request
Nov 29, 2024
Single command:
just dev-with-neon-branch gerhard-2024-11-29
The above uses a branch that I created on the 29th of November. You can
create a new Neon db branch today, using your $USER, with the following
command:
just neon-create-branch
This will create e.g. `USER-YYYY-MM-DD` prod db branch.
Here is a list of all the new commands that go well together:
[team]
dev-with-neon-branch branch # Run app in dev mode with $branch
neon-branch-connection branch *ARGS # Show $branch connection details
neon-branches # List prod db branches
neon-create-branch # Create a new branch off the prod db
This change also removes the now redundant way of creating Neon db branches.
This is a follow-up to:
- thechangelog#533
- thechangelog#508
Signed-off-by: Gerhard Lazu <[email protected]>
gerhard
added a commit
to gerhard/changelog.com
that referenced
this pull request
Nov 29, 2024
Single command:
just dev-with-neon-branch gerhard-2024-11-29
The above uses a branch that I created on the 29th of November. You can
create a new Neon db branch today, using your `$USER`, with the following
command:
just neon-create-branch
This will create e.g. `USER-YYYY-MM-DD` prod db branch.
Here is a list of all the new commands that go well together:
[team]
dev-with-neon-branch branch # Run app in dev mode with $branch
neon-branch-connection branch *ARGS # Show $branch connection details
neon-branches # List prod db branches
neon-create-branch # Create a new branch off the prod db
This change also removes the now redundant way of creating Neon db branches.
Follow-up to:
- thechangelog#533
- thechangelog#508
Signed-off-by: Gerhard Lazu <[email protected]>
jerodsanto
pushed a commit
that referenced
this pull request
Dec 5, 2024
Single command:
just dev-with-neon-branch gerhard-2024-11-29
The above uses a branch that I created on the 29th of November. You can
create a new Neon db branch today, using your `$USER`, with the following
command:
just neon-create-branch
This will create e.g. `USER-YYYY-MM-DD` prod db branch.
Here is a list of all the new commands that go well together:
[team]
dev-with-neon-branch branch # Run app in dev mode with $branch
neon-branch-connection branch *ARGS # Show $branch connection details
neon-branches # List prod db branches
neon-create-branch # Create a new branch off the prod db
This change also removes the now redundant way of creating Neon db branches.
Follow-up to:
- #533
- #508
Signed-off-by: Gerhard Lazu <[email protected]>
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.
Warning
This builds on top of #507. Please merge that PR first.
TL;DR
This is the next logical step after migrating to Neon.tech part of:
To learn more, see
changelog/README.md(added in this PR).What else changed?
Part of this, we also deployed a Dagger Engine v0.10.3 on Fly.io so that we don't need any sort of container runtime running locally. I know that @jerodsanto will appreciate this 💪
Screenshots or it didn't happen
Shout-out to @kislerdm for https://github.com/kislerdm/neon-sdk-go