TWO_FACTOR_ENCRYPTION_KEY has no default, so instances upgrading to 3.3
without setting it hit an unhandled throw from encryptSecret: the setup
dialog only reported "Something went wrong", and where 2FA was required
the blocking dialog made the whole app unusable. The status endpoint now
reports 2FA as not required while the key is missing or invalid, and
setup initiation returns 503 with a two-factor-error-not-configured code
that the setup dialog renders as a readable message. Also documents the
variable in the README and the example compose file.
Closes#4443
When the `start-docker` script is executed, some process is not properly
cleaned up and ends up in a zombie state.
Using the `init` flag when launching the container runs an init process
inside the container that will forward signals to node and reap
processes.
Fixes: #1428
I'd like to propose to delete from docker-compose a redundant volume mapping. As I see that `sql` directory had been deleted and now umami-app is responsible for migration.
I'd like to propose a minor changes that can bring more stability in launching the umami server with docker-compose by adding a certain healthcheck for db container and a certain condition for depends_on directive for umami-app container
It might be a good idea to add a restart policy to the default `docker-compose.yml` file.
Either: `restart: always` or `restart: unless-stopped`
Useful in case Umami crashes for some reason (see #721)
This is also useful in case the server restarts, so Umami starts up again after rebooting.
https://docs.docker.com/config/containers/start-containers-automatically/
NoiceHax