Keeping up with upstream on the forked images? #2

New Issue

decentral1se · 2021-12-04T15:46:04Z

decentral1se commented

2021-12-04 15:46:04 +00:00

How best to do this? Something something repo something something drone auto-build?

decentral1se commented

2021-12-04 16:29:15 +00:00

https://github.com/snikket-im/snikket-server/issues/88 👀

decentral1se commented

2021-12-08 12:21:21 +00:00

We can put our forks in https://git.coopcloud.tech/coop-cloud-chaos-patchs perhaps?

decentral1se commented

2021-12-11 16:56:03 +00:00

Each main branch of these repos is the branch used by 3wc to roll out the patches.

We can rebase / merge latest in and keep rebuilding the containers as needed.

Hopefully the patches go upstream One Day ™️

- https://git.coopcloud.tech/coop-cloud-chaos-patchs/snikket-server - https://git.coopcloud.tech/coop-cloud-chaos-patchs/snikket-web-proxy Each main branch of these repos is the branch used by `3wc` to roll out the patches. We can rebase / merge latest in and keep rebuilding the containers as needed. Hopefully the patches go upstream One Day ™️

decentral1se commented

2022-01-19 14:22:20 +00:00

265e2d4c02 gets on back on mainline with forked configs which might be easier to keep up with sec fixes then. And otherwise, we're just waiting for something to happen on https://github.com/snikket-im/snikket-server/issues/88.

https://git.coopcloud.tech/coop-cloud/snikket/commit/265e2d4c020cdd3826c906aec21c1f26ebfc8d52 gets on back on mainline with forked configs which might be easier to keep up with sec fixes then. And otherwise, we're just waiting for something to happen on https://github.com/snikket-im/snikket-server/issues/88.

decentral1se closed this issue

2022-01-19 14:22:33 +00:00

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/snikket#2