Merge strategy for minor/patch updates of database containers #25

Open
opened 2026-01-20 15:11:02 +00:00 by p4u1 · 2 comments
Owner

Should we just merge minor/patch updates for database updates like #3 or #2 even though we do not deploy it ourself? I would be okay with it. Major upgrades would have to be tested by someone who deploys it thoug

Should we just merge minor/patch updates for database updates like https://git.coopcloud.tech/coop-cloud/forgejo/pulls/3 or https://git.coopcloud.tech/coop-cloud/forgejo/pulls/2 even though we do not deploy it ourself? I would be okay with it. Major upgrades would have to be tested by someone who deploys it thoug
Owner

we're on sqlite too but i think it should be ok

we're on sqlite too but i think it should be ok
Owner

but i wonder if we really need to support other databases that maintainers don't use / can't test and defaulting to sqlite when possible sounds like a good way to keep coopcloud deployments simpler to maintain.

otherwise at some point we'll have to deal with autoupgrade images

but i wonder if we really need to support other databases that maintainers don't use / can't test and defaulting to sqlite when possible sounds like a good way to keep coopcloud deployments simpler to maintain. otherwise at some point we'll have to deal with autoupgrade images
Sign in to join this conversation.
No Label
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/forgejo#25
No description provided.