found a way with caddy to display an error when an app is down, guess it needs to be translated to use with docker labels:
handle_errors {
@502 expression `{http.error.status_code} ==…@decentral1se did you ever get the custom error pages working? I made an attempt at a805f5de26 (not working yet)…
May be good to also expose docker image prune (ideally even as a flag to autorun after a deploy) which should be enough for cases where you didn't undeploy and just need to keep a handle on…
By contrast when that happened the volumes got correctly re-associated
Well maybe it doesn't actually remove them, but if you remove a container they don't get re-associated correctly when you redeploy it?
I don't mean as an abra thing, just when running docker system prune directly on the server when your app isn't running
Well I'm not sure what's expected behaviour but in my experience I had to recreate and readd the secrets after redeploying an accidentally pruned
+1 for an abra prune command (I have to ssh on to the server and run it often because of deploying incremental and the old docker images taking up space) It would be nice to show a list of…
I don't see any problem with it because the env vars shouldn't contain any sensible data. All sensible data should be stored in secrets.
So far I've been using secrets for auto-generated…
@3wordchant yeah makes sens to have a yml override as there may end up being other differences too, just noting the feasibility (I use that to be able to specify a different images for a specific…
oh great to see! btw this approach would also work:
image: ${APP_DOCKER_IMAGE} and in the .env simply APP_DOCKER_IMAGE=codeberg.org/forgejo/forgejo:1.18.0-1-rootless or the gitea one by…