Container startup does not set APP_KEY about docker-bookstack

[thelamer]

Edit: sorry I spoke too soon. The problem is it is wrapped in the logic for setting the database endpoint for the application.

Though I cannot think of many situations where you would not want to set those using the docker env, it should not be restricted from generating that key.

I will create a PR shortly.

[rveachkc]

The APP_URL looks to be a documentation issue that should be fixed with this pull request: #19

...and honestly, I built the image off master, tried to reproduce the issue, and it's working every time now.
It's possible that I had a bunk config from when I was trying to work through the APP_URL stuff.

As far as de-coupling from the db config env vars, that might be nice, but not mandatory.

[thelamer]

We still need to update from that config file though created #22 .

[homerr]

Hi @rveachkc did you create the container with DB_USER set in the environment?

[rveachkc]

It's been a while, so I'm a bit fuzzy on the order in which I tried everything, but this was the last container definition I tried before I started configuring the .env file. Honestly, once I got that up and running, I didn't touch it.

Partial definition in ansible yaml:

- name: Bookstack Container
  docker_container:
    name: bookstack
    image: linuxserver/bookstack
    env:
      PUID: "{{ bookstack_user_task.uid }}"
      PGID: "{{ bookstack_user_task.group }}"
      DB_HOST: "{{ mysql_container_name }}"
      DB_DATABASE: "{{ bookstack_mysql_db }}"
      DB_USERNAME: "{{ bookstack_mysql_user }}"
      DB_PASSWORD: "{{ bookstack_mysql_pw }}"
      APP_URL: "https://{{ bookstack_host }}"
      APP_KEY: "{{ bookstack_app_key }}"
      APP_DEBUG: true

[homerr]

@rveachkc yeah that'd be it if that was the one, the DB_USER variable is used to determine whether it runs through and configures the .env from the environment settings. If it is not set, the container doesn't do anything and leaves the user to configure the .env manually.

Is it all working ok now?

[rveachkc]

So sorry for the delay, I suck.

My container took an update a while ago, and my custom .env file config broke.

When I flipped it to using environment variables, it works great!!

I am still setting the APP_KEY with an env variable though.

[homerr]

If you took the env variable out and made sure it matches in the bookstack_key.txt does it then work ok?

[thelamer]

This is resolved in the latest image please pull and redeploy or simply update.