5 Commits (318484f4e5cc5e492026f5e5a8f6687674180f62)

Author	SHA1	Message	Date
Markus Kahl	cc3a43ec70	make sure to remove dangling server.pid; remove one-off containers	4 years ago
Markus Kahl	be2c5ed347	Made docker dev setup more accessible, added Quickstart to docs.	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
Benjamin Bädorf	fbf375d480	Updated local development docker setup ... There are now separate containers for testing purposes, and the frontend container is a node-only image. Containers run with a user that has the current user id and gid, making sure that any files that are installed by bundler or npm are user-owned. Selenium tests can be ran, but not all of them work yet.	4 years ago
Benjamin Bädorf	a8dfb55345	Updated local development docker setup ... There are now separate containers for testing purposes, and the frontend container is a node-only image. Containers run with a user that has the current user id and gid, making sure that any files that are installed by bundler or npm are user-owned. Selenium tests can be ran, but not all of them work yet.	4 years ago
Markus Kahl	31546d91cc	docker-based dev environment	5 years ago
Markus Kahl	5c07f7bd95	docker-based dev environment	5 years ago