and review) All-in-one approach Fast, unified CI feedback Better DX (less time for deployment and installation, more code examples) Disadvantages dev.json management (should be automated) Short history in case tree was imported Symlinks on Windows =)
installed AND I have docker installed AND I have docker-compose installed WHEN I do git clone https://github.com/laboro/dev AND Go to application folder (application/platform) AND Run docker-compose up -d THEN webserver, php, DB containers are created AND I can run Composer AND I can install platform application
AND I have docker installed AND I have docker-compose installed WHEN I do git clone https://github.com/laboro/dev AND Go to application folder (application/platform) AND Run docker-compose up -d AND Run install script THEN webserver, php, DB containers are created AND I can open in my browser platform.oro.dev
installed AND docker installed AND docker-compose installed WHEN Do git clone https://github.com/laboro/dev AND Open application folder (application/platform) AND Run docker-compose up -d AND Run install script THEN webserver, php, DB containers are created AND CI can run UNIT tests AND CI can run FUNCTIONAL tests AND CI can run BEHAT tests
have GIT installed AND I have docker installed AND I have docker-compose installed WHEN I do git clone https://github.com/orocrm/platform-application to platform folder AND git clone https://github.com/orocrm/environment to environment folder AND Change dir to platform folder AND Run docker-compose up -d THEN webserver, php, DB containers are created AND I can run Composer AND I can install platform application
nodes • performance tuning (cpu shares, memory, I\O) • apply for community packages and applications • make environment stateless (parallel and files with php files) • selenium support for behat tests • stable release Next steps