Probably the handiest thing is https://git.coopcloud.tech/coop-cloud/swarm-cronjob. We could have a compose.cron.yml which runs standard, useful jobs. These could be configurable by env vars? Unsure. There could be further compose.$job.yml to swap them in/out if required. Example in
Probably the handiest thing is https://git.coopcloud.tech/coop-cloud/swarm-cronjob. We could have a `compose.cron.yml` which runs standard, useful jobs. These could be configurable by env vars? Unsure. There could be further `compose.$job.yml` to swap them in/out if required. Example in https://git.coopcloud.tech/coop-cloud/loomio/src/commit/949f952ae435dfe7edf351dda9debfd0c1c3fe6d/compose.yml#L130-L131 you need to have https://git.coopcloud.tech/coop-cloud/swarm-cronjob running on the swarm first
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Required for cache and media clearing on instances that use local stoorage unless you want your whole harddive filled with cat videos from months ago
Probably the handiest thing is https://git.coopcloud.tech/coop-cloud/swarm-cronjob. We could have a
compose.cron.ymlwhich runs standard, useful jobs. These could be configurable by env vars? Unsure. There could be furthercompose.$job.ymlto swap them in/out if required. Example inSaw https://codeberg.org/bath.social/server/issues/6 btw /cc @nicksellen (happens to be open on the wrong recipe 🙃 but maybe useful info above also).
This is the workaround that Autonomic is using meanwhile.