chore: Litestreamを用いてDBを永続化 #38
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
sou1118
force-pushed
the
feature/issue-37
branch
from
c934249 to
b34ce14
Compare
r4ai
previously approved these changes
Nov 17, 2024
3w36zj6
reviewed
Nov 18, 2024
sou1118
force-pushed
the
feature/issue-37
branch
from
2d10af7 to
e7b4609
Compare
r4ai
approved these changes
Nov 18, 2024
3w36zj6
approved these changes
Nov 18, 2024
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.
close #37
Summary
This pull request introduces significant changes to the database backup and persistence strategy by integrating Litestream for SQLite databases. Additionally, it updates related configurations and documentation to reflect these changes.
Database Backup and Persistence:
ARCHITECTURE.md: Added a detailed section on database backup and persistence using Litestream, including a flowchart, operational mechanism, limitations, differences in development environment, deployment settings, and troubleshooting tips.Dockerfile: Updated to install Litestream, SQLite, and related tools. Modified database paths and added steps to handle database migration and backup. [1] [2]compose.yaml: Updated volume and environment configurations to reflect the new database path.litestream.yml.template: Added configuration for Litestream to replicate the database to Google Cloud Storage.run.sh: Added a script to handle database restoration from Cloud Storage, ensure compatibility with Prisma, and start the application with Litestream replication.Documentation:
README.md: Added a link to the architecture overview document for more detailed information on the new database backup and persistence strategy.