New v7.6.0 docker install on debian - no .env or other familiar settings from v6?

[ajohnson30]

I had a small docker site on V6/debian which I tried to upgrade, didnt go well, and I thought it'd be "cleaner" to just start over, do I did a new install with the docker-compose.minimal.yaml. Initial access to the machine by ip at x.x.x.x:8000, going just fine. I quickly noticed however that I couldn't find any trace of a .env file, as a mount or otherwise. There are copies of the docker-compose.minimal.yaml in various docker volumes, so I suppose these could be updated in some manner, but I'm sort of lost here as to how I'd switch the access. I normally access the site via a proxy url, so I think I need the TRUSTED_PROXIES setting and possibly APP_URL, APP_DIR, but I'm not sure. I should've saved my old env files.

[ildyria]

If you use the new docker-compose & docker images, you no longer need to mount the .env.
You can still have a .env, it will be loaded by default by the docker-compose.yaml and used to populate some of the values in the env section.

You can modify the docker compose env section: https://github.com/LycheeOrg/Lychee/blob/master/docker-compose.yaml#L92
Those are directly forwarded to the container and loaded by Lychee. You can see all the possible env values in https://github.com/LycheeOrg/Lychee/blob/master/.env.example

Important to note that if you change an env value, they are no longer directly applied, you will need to restart the container.

TRUSTED_PROXIES=* (if you are lazy)
APP_URL=https://lychee.example.com

If you use docker, you should not use APP_DIR unless you make a weird proxy that redirect https://example.com/lychee to your container. However I would really not recommend that and instead use a sub domain (see above).

[ajohnson30]

lol. I'm not in a hurry or anything, but I'm happy to know it wasnt me

[ildyria]

Found the fix.
#4453

Now need to wait for the CICD to run.

[ildyria]

So for some reason 7.6.1 it works fine on my machine and on the demo server, but as soon as I run on my docker instance, it dies... To be investigated. :(

[ildyria]

Validated by :
taking the 01-validate-env.sh from version 7.6.0
and mounting it on my docker compose stack on my server.

      - /docker/01-validate-env.sh:/usr/local/bin/01-validate-env.sh

[ildyria]

lol. I'm not in a hurry or anything

Unfortunately, I am. :D

Lychee has an self-check on vulnerabilities. When an advisory is published here https://github.com/LycheeOrg/Lychee/security/advisories
Lychee checks the running version of the server against the list and figures out if you are vulnerable or not.

There are two vulnerabilities published in version 7.6.0 which are going to tell people to update to 7.6.1+...
As you can imagine, I can't ask them to update to something broken...