WIP: Backup labels #9
No reviewers
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/hedgedoc#9
Loading…
Reference in New Issue
No description provided.
Delete Branch "wolcen/hedgedoc:main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Tested deploy & backup (have not yet apptempted restore).
LGTM 👍
@ -34,3 +34,3 @@
- internal
volumes:
- codimd_uploads:/home/hackmd/app/public/uploads
- codimd_uploads:/hedgedoc/public/uploads
Shall we do
codimd_uploads
->hedgedoc_uploads
also while we're here? Would be a breaking change on the recipe, people would need to migrate their volumes, but idk how many folks are using this right now? Up to you!I'm not personally sure it's worth breaking people's configs, but there are bigger issues than that, really. I'm a bit concerned about the existing deployments upgrade path - are there possibly upgrade hooks for this (for example, would be great to do a one-time tar/gz of the /hedgedoc/public/uploads if it is in the container)? People's volumes will be pointing to the incorrect folder, backups would not have been working, and just restarting the instance would kill their uploaded files otherwise, if I understand correctly?
Backups were not previously working (for me, at least), but at least this was what the recipe had reported, so hopefully no one was really trusting it for long-term pads (which we do intend to have).
FWIW, all the env vars for hedgedoc use codi's old "CMD_" prefixes, but it would probably be nice to see hedgedoc_uploads in your volume list.
If you'd prefer, I can do them in a different merge/pr, but I'm changing a few more things - I've added a health check for Postgres, and another CMD_ setting that I'll be using - I'm a little unclear how the versioning works at present, but just a note that if it'll require another version, more settings are inbound, one of which is the session secret in order to maintain logins between restarts.
Oh yeh, v reasonable, maybe bundling all your changes into a new major recipe release version is the way to go? The upgrade paths are sometimes a bit ad-hoc yeh, so we have this "release notes" feature 👉 https://docs.coopcloud.tech/maintainers/handbook/#how-do-i-write-version-release-notes 👈 You can write a short guide which will turn up in the shell when people run
upgrade
and realise they need to do some work before doing the upgrade. Anyway, up to you!mainto Backup labelsComing back to this @wolcen, any updates?
Backup labelsto WIP: Backup labels6bdde4622d
to1a2b3b9899
1a2b3b9899
tod299d5461d
Step 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Gitea.