huginn/docker
Dominik Sander 1a87133b1f Delete stale delayed_job pid file when starting docker containers
When a (single-process) docker container is not shut down cleanly
delayed_job does not have a chance to delete it's PID. When restarting
this container delayed_job refused to boot because it found the old PID.

Since we always start from a clean state in docker containers we can
remove the PID.

Fixes #2269
2018-10-03 11:29:34 +02:00
..
multi-process Extract database vars and source them via env_file 2018-08-23 09:53:31 -05:00
scripts Delete stale delayed_job pid file when starting docker containers 2018-10-03 11:29:34 +02:00
single-process Extract database vars and source them via env_file 2018-08-23 09:53:31 -05:00
test Extract database vars and source them via env_file 2018-08-23 09:53:31 -05:00
mysql.env Extract database vars and source them via env_file 2018-08-23 09:53:31 -05:00
postgres.env Extract database vars and source them via env_file 2018-08-23 09:53:31 -05:00
README.md Replace cantino/huginn* with huginn/huginn* 2017-05-17 21:18:50 +02:00
secrets.env Extract database vars and source them via env_file 2018-08-23 09:53:31 -05:00

Huginn Docker images

Huginn is packaged in two docker images.

huginn/huginn multiple process image

This image runs all processes needed by Huginn in one container, when the database is not linked it will also start MySQL internally. This is great to try huginn without having to set up anything, however maintenance and backups can be difficult.

huginn/huginn-single-process multiple container image

This image runs just one process per container and thus needs at least two container to be started, one for the Huginn application server and one for the threaded background worker. It is also possible to every background worker in a separate container to improve the performance. See the PostgreSQL docker-compose configuration for an example.