Expose LOG_MAX_AGE #55

2025-08-06T22:23:01Z

sixsmith commented

2025-08-06 22:23:01 +00:00

Expose LOG_MAX_AGE, Traefik's log retention setting for log retention (in days).

Expose [LOG_MAX_AGE](https://doc.traefik.io/traefik/observability/logs/#maxage), Traefik's log retention setting for log retention (in days).

🎉 1

sixsmith added 1 commit 2025-08-06 22:23:02 +00:00

Update to Traefik v3

continuous-integration/drone/pr Build is failing

Details

01c5b2a3a4

3wordchant commented

2025-08-07 18:25:22 +00:00

@sixsmith this looks incredible, thank you so much! 🤩

Only note is that TRAEFIK_YML_VERSION in abra.sh needs to be incremented with every change to the file, otherwise upgrades of existing instances will probably fail.

@sixsmith this looks incredible, thank you so much! 🤩 Only note is that [`TRAEFIK_YML_VERSION` in `abra.sh`](https://git.coopcloud.tech/coop-cloud/traefik/src/branch/master/abra.sh#L1) needs to be incremented with every change to the file, otherwise upgrades of existing instances will probably fail.

👍 1

sixsmith added 1 commit 2025-08-09 02:18:03 +00:00

traefik_yml_version

continuous-integration/drone/pr Build is failing

Details

8d7f9bd6a2

decentral1se reviewed 2025-08-09 10:45:09 +00:00

traefik.yml.tmpl

						
				@@ -4,6 +4,7 @@ core:

				log:

				  level: {{ env "LOG_LEVEL" }}

				  maxAge: {{ env "LOG_MAX_AGE" }}

decentral1se commented

2025-08-09 10:45:05 +00:00

Oh sorry, this is not exactly compatible with new upgrades that won't make use of this env var? E.g. if they don't add a LOG_MAX_AGE to their .env (there is a warning from abra buy yanno...) then they might have a broken config? I'm not sure. One way to avoid this is to use the ${LOG_MAX_AGE:-1} bash default value trick in the compose.yml inclusion of the env var (see other recipes for examples)? However, then you need to make sure this default is the standard default and doesn't have behaviour changing effects for other operators.

Oh sorry, this is not exactly compatible with new upgrades that won't make use of this env var? E.g. if they don't add a `LOG_MAX_AGE` to their `.env` (there is a warning from `abra` buy yanno...) then they might have a broken config? I'm not sure. One way to avoid this is to use the `${LOG_MAX_AGE:-1}` bash default value trick in the `compose.yml` inclusion of the env var (see other recipes for examples)? However, then you need to make sure this default is the standard default and doesn't have behaviour changing effects for other operators.

decentral1se marked this conversation as resolved

sixsmith added 1 commit 2025-08-27 16:35:12 +00:00

Set default LOG_MAX_AGE

continuous-integration/drone/pr Build is failing

Details

304915a396

sixsmith commented

2025-08-27 16:36:44 +00:00