So while troubleshooting my other thread regarding the thumbnails, I was trying to do some testing without automatically processing things on startup. To that end, I set the following environmental variable in compose:
However, upon initially saving my settings and clicking start, which I believe is required for the settings files to be written, the processing and import on
/ps/library began. I’m wondering if its possible to debug this, or if I’ve simply made a careless error. Here is my updated compose:
## HTTP Routers
## HTTP Services
For reference I am running docker version 20.10.7, compose version 1.29.1, and my compose is version 3.8 - all on Ubuntu server 20.04 LTS.
Thanks very much!
When I used Docker Compose my environment vars were in double-quotes, and they seemed to work:
Thanks for the suggestion. I had previously used quotes in my compose file around my labels but recently removed them. If you run a
docker-compose config, you’ll be able to simulate exactly how compose interprets the file, including substituting in values for variables, etc. as a test.
Just to double check, I did this:
On the left is original and on the right the variables were quoted, so that seems to not be affecting things. I verified in Portainer as well.
I should clarify that the video transcode flag appears to be working, as is my temporary redirect of the previews directory. It specifically only seems to be the start paused? Unless I am misunderstanding how start paused works. I thought I could turn it on, click save on my settings, and it would not begin to scan my folders.
docker-compose.yml should support both dictionaries and arrays:
startPaused causes the
main process to set
paused to true at launch, which should prevent
sync from starting. Is this not working for you?
On initial launch after saving my settings and logging into billing, it appears to still scan all loaded folders after I hit ‘return to library’ the first time when it should be paused.
Oh man: I always tested it with an existing library. I actually had to make a couple changes to make this work as expected, and those changes will be in beta.10 which I hope to release shortly.
Thanks for reporting this!
Also: if you want to see what non-default settings are set, run the
info --child-env command. Here’s an example via docker:
$ docker exec -it psdc_photostructure_1 ./photostructure info --child-env
Looking forward to it! Thank you. Very hand too regarding the non-default settings reporting. Does this seem reasonable or expected? I only set 4 of the
PS_ prefixed settings. (start paused through transcode videos)