Closed asitemade4u closed 2 years ago
Hey, thanks for reporting!
I think I found the issue - I forgot to set the right default for PHOTOFIELD_DATA_DIR
in the published Docker image making it look in /app
instead of /app/data
for the yaml.
I'll fix it soon, but meanwhile, you should be able to fix it by adding the PHOTOFIELD_DATA_DIR=./data
env var.
I've published v0.1.10 that should fix this, please let me know if it works for you! 😊
Latest #13 should also print the configuration path 👍
Describe the bug When using docker-compose, the stack is unable to open the
configuration.yaml
file and, as a result, does not publish photosTo Reproduce Steps to reproduce the behavior:
configuration.yaml
file (following the defaults in the documentation) into the local directory bound to the/app/data
directory in the stack777
access rights to the file (not secure, but for now I want to eliminate any access right issues)docker-compose up
or, in my case, use PortainerI checked within the container for the
configuration.yaml
file: it is indeed there with the right content.Expected behavior The container should publish photos on the chosen port.
Environment Debian 10