This repository was archived by the owner on Dec 20, 2023. It is now read-only.
Convert to SQLite+S3 backend rather than a dedicated PostgreSQL database #33
Conversation
This file contains hidden or 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
tgriesser
approved these changes
Nov 21, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We are migrating this application to a new hosting platform and no longer want to run it with a dedicated PostgreSQL database to streamline maintenance and operations. Since we typically don't run this application at large horizontal scale, I've refactored it to leverage a local SQLite database that gets pulled from S3 (or created) on startup, and pushed to S3 on shutdown.
I also fleshed-out the readme a bit more with some of the new env variables I added and some more ELI5 running instructions.