-
Notifications
You must be signed in to change notification settings - Fork 20
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
Use Docker instead of dbdeployer for local testing #187
Labels
Comments
I like dbdeployer, but I agree predicated on two assumptions:
|
Since this issue was created, dbdeployer has reached end of life. I'm adding the help-wanted tag to this issue. |
sahilm
added a commit
to sahilm/spirit
that referenced
this issue
Jun 24, 2024
TODO: 1. Tests with replicas 2. Docs (holding off docs till support is complete) See also: cashapp#187
2 tasks
sahilm
added a commit
to sahilm/spirit
that referenced
this issue
Jun 24, 2024
TODO: 1. Tests with replicas 2. Docs (holding off docs till support is complete) See also: cashapp#187
sahilm
added a commit
to sahilm/spirit
that referenced
this issue
Jun 24, 2024
TODO: 1. Tests with replicas 2. Docs (holding off docs till support is complete) See also: cashapp#187
sahilm
added a commit
to sahilm/spirit
that referenced
this issue
Jun 25, 2024
sahilm
added a commit
to sahilm/spirit
that referenced
this issue
Jun 25, 2024
sahilm
added a commit
to sahilm/spirit
that referenced
this issue
Jun 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I propose we use Docker rather than dbdeployer because Docker is industry standard, and I bet it's far more common with developers than dbdeployer. It's also pretty easy to set up multiple version with Docker Compose.
If you agree, I'll do a PR later.
The text was updated successfully, but these errors were encountered: