Lychee not importing S3 config from environment vars #2486
Unanswered
RickyRomero
asked this question in
Bugs
Replies: 2 comments 2 replies
-
That is because only part of the environment are passed to the |
Beta Was this translation helpful? Give feedback.
0 replies
-
If I were to open a PR to fix it, would that be helpful? 🙂 |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Lychee version
v5.5.0
Which PHP version are you using?
PHP 8.2
Detailed description of the problem
I'm using Lychee with Docker Compose, configuring it via environment variables fed in from a
.env
file adjacent to mydocker-compose.yaml
file using theenv_file
property.For many of these variables, Lychee automatically copies them from my Docker environment into
/conf/.env
. I would expect Lychee to do the same when I specify an S3 config, however it doesn't do that. I had to manually move my S3 details into/conf/.env
before Lychee recognized there was an S3 config at all.(note: in the config below, I've specified
AWS_IMAGE_VISIBILITY=private
. I don't know what the correct value is for this yet, but I don't think it's related to this bug. I'm still figuring this out due to a lack of documentation. It sends the photos to S3 okay, but reading them back using pre-signed URLs isn't working yet.)Steps to reproduce the issue
docker-compose.yaml
.env
file next to yourdocker-compose.yaml
..env
/conf/uploads
.config/conf/.env
with the S3 config values in the Docker.env
.Diagnostics [REQUIRED]
Browser & System [REQUIRED]
Server: Debian 6.1.76-1 (2024-02-01) x86_64, Docker 27.0.2 build 912c1dd, Lychee v5.5.0 image behind Caddy v2.8.4
Client: macOS 14.5, Chrome 126.0.6478.127
Please confirm (incomplete submissions will not be addressed)
Beta Was this translation helpful? Give feedback.
All reactions