2 Commits (51a40c97eb0315fd2a5dd86dfd7333f9d8d15d92)

Author	SHA1	Message	Date
Markus Kahl	5511a765b3	Fix: compose schema issues (#8900) ... * load structure rather than migrate for the greater good most importantly to fix the race condition during the docker-compose setup we face when migrating which causes the web process to use an outdated schema cache * ensure database is migrated before starting worker/web processes	4 years ago
Benjamin Bädorf	5f45ee07ab	Move development docker-compose file to the main directory (#8798) ... * Move development docker-compose file to the main directory This requires us to move some other files around, like the pullpreview and example docker-compose file for production setups. This commit also does some housekeeping, like removing some old files and deduping configuration. * Updated to selenium grid * Fix in-Docker Selenium tests The Selenium tests now run inside a Docker Chrome Container. Backwards compatability with non-docker setups is not guaranteed, though it should not be hard to implement with a couple of small fixes. * Updated docker development documentation * Improved test timings, changed the documentation * Updated docker testing again * Run npm in the frontend directory * Really run npm in the frontend directory * Also run npm in frontend when setting up travis cache * Change directory for one command only * Change default test driver name * CI test change fixes * Fixed syntax error * Added dev check * Trying to fix firefox resizing * Trying to get tests running * Stop resizing firefox * Fixed apple icon spec * fix host in url helpers for omniauth spec * Fix omniauth specs * Fix docs * Small fixes to docker tests * Added package.json back in * Change env variables Co-authored-by: Markus Kahl <machisuji@gmail.com>	4 years ago
Cyril Rohr	1cc7fedac0	Provide docker-compose v3 with one process per container	5 years ago
Cyril Rohr	cbd2c93bb7	Allow to override settings when executing the worker in --seed mode	6 years ago
Cyril Rohr	cc95391a69	More involved than expected, since we were not starting the container as root. ... So, adding a default entrypoint that switches to the APP_USER, and chown the APP_DATA folder to make sure it has the correct permissions. (By default, docker creates volumes owned by root, so in the previous version the APP_USER couldn't write to the folder). This is what's done in postgres: 2f0f505894/10/docker-entrypoint.sh	7 years ago
Cyril Rohr	97ac309fe6	dockerize	9 years ago