Simão Gomes Viana

I'm guessing that the currently installed version is not checked in https://github.com/caddyserver/caddy/blob/f6bb02b303d4a24c6932fd832f7aa9de224b6833/cmd/commandfuncs.go#L582 and thus it just downloads the stable and installs it?

Would it be possible to have an API endpoint (or maybe just a file in each GitHub release) containing its own version? For example: https://github.com/caddyserver/caddy/releases/download/latest/version.txt And then just parse the...

What about doing commit --amend whenever possible and do a force push when e.g. updating the leaderboards so that you dont have many many commits doing the same thing. Git...

Well, i mean the leaderboard updates of that enkibot...

Would shrink down the size of the repo a little bit tho

What about like pushing the stuff to a git server of yours, and like every week push the stuff to github... I guess that would still give that commit streak...

Maybe another way could be to connect to tailnets together in the admin panel and use ACLs to grant cross-tailnet access for users/groups. Is this something that will be implemented?

I'd like to see this as well.

Perhaps it would be sufficient to just specify the env files in docker-compose.yaml which is already supported: ``` # ... env_file: # whichever you prefer - ${ENV}.env - .env.${ENV} ```...

Gonna look into this too. @Thunderbottom we need to improve intent handling here