Open boekhorstb1 opened 1 year ago
That's two different things.
Factoring out the scripts that install development tools for reuse. Everything that moves implementation detail into separate files and only keeps an (if file exists run file: foo.sh) block in the entrypoint is good.
How to run the development script. At the moment we have a switch for development mode that does two things: autoloader config for either production optimized or development optimized. Install some default extra packages. And we have an additional variable that allows to install extra software. We should not make it too complicated. If the user wants the production setup and sets variable to no, he can still install the development tools later. If the user wants the development setup and sets the variable to yes, he should get that. If waiting for development tools is too long, running the install script in the background (with &) may be the solution.
I find this practical because the container setup sometimes takes to long to install all the needed dev tools. With manual scripts one can start working and let the scripts to install all thats needed.