Version 1.0.0-alpha.7 is out!

Announcements
,
2

From reddit:

When I follow the upgrade instructions I get an error in the logs that a file is missing. If I switch back to main image it works fine though. Out of curiosity I also check the beta image and that works too.

The :beta image is actually still on v0.9.1, as I’ve only made alpha releases of v1.0.0 so far. I’ll muster some courage and promote the next build as a beta. :muscle:

I’m using the following volume for config. I’m working out of /opt/docker/photostructure and have manually created /opt/docker/photostructure/config.

  • type: bind
    source: “./config”
    target: /ps/config

Error: ENOENT: no such file or directory, open ‘/ps/config/PhotoStructure/settings.toml’

{“fatal”:true,“exit”:true,“status”:14,“pid”:21,“ppid”:14,“error”:“main setup failed: Error: code ENOENT: ENOENT: no such file or directory, open '/ps/config/PhotoStructure/settings.toml’¹”}

I wonder if docker-compose is resolving your relative source: path correctly? I’ve always used full path names.

It might be enlightening to enable debug logs, if you add this

    environment:
      # PhotoStructure has _tons_ of settings. See
      # <https://photostructure.com/faq/environment-variables/>

      - PS_LOG_LEVEL=info
      - PS_LOG_STDOUT=true
      # - UID=1000 # < this is the new v1.0.0 way to run as a non-root user
      # - GID=1000

and then run docker-compose up (omit the -detach) to get logging on your terminal.