Helge Rausch 9b1ed05a5f Fix CRON (#24)
* Use docker-compose to run database setup
* Build sidekiq image in test script
* Fix db migration startup script
* Let Runit deal with services

Sidekiq was started by a blocking script in my_init. This lead to the init process not getting to run Runit, which is in charge of CRON among other things. To fix it, I moved Sidekiq to be run by Runit as well. I also moved the postfix start script, while I was at it.
2022-11-23 15:09:34 +01:00
2022-11-15 10:27:41 +01:00
2022-11-23 15:09:34 +01:00
2022-11-23 15:09:34 +01:00
2018-01-09 10:04:59 -08:00
2015-10-29 09:04:07 +01:00
2022-11-23 15:09:34 +01:00
2022-11-23 15:09:34 +01:00
2018-04-02 21:05:30 +02:00
2022-11-23 15:09:34 +01:00

Docker images for opensnp.org

Currently two images - a opensnp.org-docker image and a dev image. The opensnp.org-docker image in the root folder pulls all gems and other dependencies. The dev image adds a few dummy files so that you can run the image in a local container.

How to build the images

Start the docker server (screen/tmux/service if your system supports that)

docker daemon

Then in the root folder:

docker build -t opensnp.org-docker .

This builds the opensnp.org-docker image and sets the name to opensnp.org-docker. This step takes ~10 minutes since it installs all dependencies and gems.

Then to build the dev image:

cd dev_image
docker build -t dev .

To see all images:

docker images

This should show two images, one named opensnp.org-docker and one named dev.

Now you can either build a container based on the dev image or on the opensnp.org-docker image.

Building the dev container

docker run dev

To run with environmental variables, in this case setting FOO to bar:

docker run -e FOO=bar dev
Description
No description provided
Readme 94 KiB
Languages
Dockerfile 71.3%
Shell 28.7%