aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Downgrade to docker-compose file version 2.4.Alec Warner2021-01-011-1/+1
| | | | | | This enables memory limits; to help prod not get stuck in memory limbo. Signed-off-by: Alec Warner <antarus@gentoo.org>
* Add selfcheck component to docker-composeMax Magorsch2020-11-081-0/+19
| | | | Signed-off-by: Max Magorsch <arzano@gentoo.org>
* Add the possibility to customize the web pageMax Magorsch2020-10-061-0/+2
| | | | | | | | | | Different customization options have been added, so that it's possible to change the contents of the web page to the visitors needs. Cookies are currently used to store the preferences. Signed-off-by: Max Magorsch <arzano@gentoo.org>
* Add docker files for development purposesMax Magorsch2020-05-241-7/+10
| | | | Signed-off-by: Max Magorsch <arzano@gentoo.org>
* Add image: titles in the override.Alec Warner2020-05-151-0/+2
| | | | | | | | | | | | | | | When I run docker-compose up; it attempts to build the containers. This is correct, but on my Ubuntu box for some silly reason go thinks my kernel is bad and needs a higher ulimit set to memlock the signal stack (a known golang bug.) I can do this in docker build (via --ulimit to docker build) but docker-compose offers no such luxury when calling docker build. So by naming them in the docker-compose file, I can run docker build by hand to produce the containers, and then docker compose just starts and stops them. Signed-off-by: Alec Warner <antarus@gentoo.org>
* Add a docker-compose.override.yml for the developmentMax Magorsch2020-05-121-0/+63
Signed-off-by: Max Magorsch <arzano@gentoo.org>