Update sample apps & use default DB setup #223
Merged
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
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.
I ran
bundle updateon the sample apps to get them to run on a few newer versions of things, and updated the ones that require a PG database to use the default config from Rails so they can more easily run on a stock setup (lke a postgresql installed from brew without any changes, etc.), removing timescale-specific extensions/schemas that were sometimes dumped to these sample apps.I re-did the setup for SolidQueue since it now uses a schema (or a single migration file in case of using a single DB like this sample app setup), and updated it to latest v1