[BUG] email config envs only get passed down using env_file option with docker compose

[etranger7]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

To configure email functionality, I added the email settings in the .env file inside the same folder as my docker-compose.yml

After running docker compose up, I still got the email sending error trying to use localhost:587
Only after adding

   env_file:
      - .env

I'm not sure if this is intended or not since docker compose treats variables .env by itself vs when referenced as env_file: further exposing them to commands such as
docker exec -it bookstack env

If this is by design, perhaps explicit directions here to add env_file: .env might be helpful.

Expected Behavior

No response

Steps To Reproduce

As explained above.

Environment

- OS: Debian
- How docker service was installed: docker.com debian install method

CPU architecture

x86-64

Docker creation

Please see above.

Container logs

Not needed.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[ssddanbrown]

I added the email settings in the .env file inside the same folder as my docker-compose.yml

Yeah, that wouldn't do anything by itself.
The linuxserver provides the BookStack .env file at www/.env within the volume folder you have mounted to /config for the container.

BookStack will use environment options over the .env file options, where set, hence why then passing the file via the env_file made the options work (since they become environment variables inside the container).

[etranger7]

Got it, I wasn't aware of the location of the linuxserver env. I guess this is a non-issue then.