8 Commits (46b85e5a47f01c25250df8df39057f8d54a92a2f)

Author	SHA1	Message	Date
Markus Kahl	c375646dc0	docker dev and test setup fixes (#9135) ... * docker dev and test setup fixes * added missing > * include test instructions in quickstart * fixed typo Co-authored-by: Philipp Tessenow <tessi@bitcrowd.net> * removed obsolete comment Co-authored-by: Philipp Tessenow <tessi@bitcrowd.net> * amendments Co-authored-by: Benjamin Bädorf <b.baedorf@openproject.com> Co-authored-by: Philipp Tessenow <tessi@bitcrowd.net>	4 years ago
Markus Kahl	47a752d889	make sure to use latest patch level of ruby base image (#9052) ... * make sure to use latest patch level of ruby base image * how to handle outdated images	4 years ago
Markus Kahl	1c8aaf031f	Maintenance: ruby patch level update to 2.7.2 (#8951) ... * Update ruby to 2.7.2 * make sure to pull latest base image * minor comment update	4 years ago
Benjamin Bädorf	660884f50a	Fix various problems with the docker setup and frontend changes (#8846) ... Fix various problems with the docker setup and frontend changes * Set the node version to the same one that is used in the final packages and that is required in package.json * Change the order of operations for backend container building * Set the npm dependencies back to where they were * Change browserslist rules for firefox * Fix some docker commands for pullpreview * Add b12f as a pullpreview admin Co-authored-by: ulferts <jens.ulferts@googlemail.com>	4 years ago
Cyril Rohr	28347a4eab	Fix paths for pre/post install with prod docker	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	686f12315e	Revert changes to setup_dev ... They were unnecessary, and were not backwards-compatible with non-docker development	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	8b74bffac7	Revert changes to setup_dev ... They were unnecessary, and were not backwards-compatible with non-docker development	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