-
Notifications
You must be signed in to change notification settings - Fork 6
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
Coolify! #611
Coolify! #611
Conversation
Thanks so much for doing this. Please use Postgres if you can instead of a volume. The VPS should be considered stateless |
Won't Postgres be hosted on the VM? |
Yeah, but it'll be automatically backed up to the s3 backup destination so it can easily be restored. |
The database is currently synchronously replicated to S3 with Litestream |
Please don’t have it go to S3, we’re gonna shut down our AWS account. Goal
is to have less services and accounts to maintain. Can you have it be
automatically backed up to the S3 backups area in Coolify? Thank you!
…On Jan 14, 2025 at 1:05:42 PM, Matt Almeida ***@***.***> wrote:
The database is currently synchronously replicated to S3 with Litestream
—
Reply to this email directly, view it on GitHub
<#611 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHSH6FVQQIOA7KXNU6VBET2KVGXNAVCNFSM6AAAAABVFOL5WKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJQG42DSMJUG4>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
Oh, that's awesome! It looks like there might either be multiple Hack Club orgs in Hetzner Cloud (the one I have access to is owned by @maxwofford) or I just can't see the bucket in question. But this app needs persistent (not autocleaned like the backups one) storage anyway to store images and whatnot anyway, so should I just create a separate bucket under the org and use that one? |
Additionally, I'll need permissions to merge DNS PRs to minimize downtime unless someone else wants to take point on this. Feel free to add anything I missed to the migration plan above! |
@northeastprince let's schedule a time for us to do this together. How's tmrw 1pm PST? In the meantime, go ahead and create the DNS PRs and link them here. (make sure the |
That works! |
# get dump
ssh [email protected]
cd /var/lib/docker/volumes/hackathons-storage/_data
sqlite3 production.sqlite3
.output ./dump.sql
.dump
.exit
# copy dump to new server
scp dump.sql [email protected]:/var/lib/docker/volumes/l0k04cg840sww008o4cos0gs_storage/_data/
# restore dump
ssh [email protected]
cd /var/lib/docker/volumes/l0k04cg840sww008o4cos0gs_storage/_data/
sqlite3 production.sqlite3
.read ./dump.sql
.exit |
If possible, my strong preference would be to use Postgres instead of SQLite for the DB. That will allow people to access the DB while the app is running, and simplify backups. |
@garyhtou also pointed out the BI aspect which I hadn't considered - it's clear by now stats aren't going into the admin dashboard anytime soon 😆. I'll make sure to get around to migrating back soon! |
Awesome, thank you!!!
…--
Zach Latta
https://zachlatta.com <http://zachlatta.com>
@zachlatta <https://twitter.com/zachlatta> / fb
<https://www.facebook.com/crynix> / github <https://github.com/zachlatta>
On Feb 4, 2025 at 5:56:59 PM, Matt Almeida ***@***.***> wrote:
If possible, my strong preference would be to use Postgres instead of
SQLite for the DB. That will allow people to access the DB while the app is
running, and simplify backups.
@garyhtou <https://github.com/garyhtou> also pointed out the BI aspect
which I hadn't considered - it's clear by now stats aren't going into the
admin dashboard anytime soon 😆. I'll make sure to get around to migrating
back soon!
—
Reply to this email directly, view it on GitHub
<#611 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHSH6DZ7ODLOJQD2OX4L4L2OFATXAVCNFSM6AAAAABVFOL5WKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVGI2TAOJRGM>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
Migration Plan
Before operation commencement
M-minus A record's TTL (currently 10 minutes)
M-minus 0