Repository files navigation

Docker environment required to run Laravel (based on official php and mysql docker hub repositories).

Source code

• Docker version 18.06 or later
• Docker compose version 1.22 or later
• An editor or IDE
• MySQL Workbench

Note: OS recommendation - Linux Ubuntu based.

1. Apache 2.4
2. PHP 7.3 (Apache handler)
3. MySQL 8
4. Laravel 5.7

1. Build and start the image from your terminal:

   docker-compose buildmake startmake composer-installmake make env-local

2. Add domain to local 'hosts' file:

   127.0.0.1    localhost

3. Set key for application:

   make sshphp artisan key:generate

4. Make sure that you have installed migrations/seeds:

   make migratemake seed

5. Configure Xdebug:
   • In case you need debug only requests from frontend in Firefox:
     • Edit /docker/development/xdebug.ini:

     xdebug.remote_autostart = 0

     • Restart container
     • Install locally in Firefox extension "Xdebug helper" and set in settings IDE KEY: PHPSTORM
     • Have fun with debugging
   • In case you need debug any request to an api:
     • Edit /docker/development/xdebug.ini:

     xdebug.remote_autostart = 1

     • Restart container
     • Have fun with debugging

```make startmake stopmake restartmake sshmake ssh-supervisordmake composer-installmake composer-updatemake infomake drop-migratemake migratemake seedmake phpunitetc....```Notes: Please see more commands in Makefile

• Laravel 5.7
• laravel-migrations-organiser
• phpunit
• phpunit-result-printer
• laravel-ide-helper
• scriptsdev

• General

1. For new feature development, forkdevelop branch into a new branch with one of the two patterns:
   • feature/{ticketNo}
2. Commit often, and write descriptive commit messages, so its easier to follow steps taken when reviewing.
3. Push this branch to the repo and create pull request intodevelop to get feedback, with the formatfeature/{ticketNo} - Short descriptive title of Jira task".
4. Iterate as needed.
5. Make sure that "All checks have passed" on circleci and status is green.
6. When PR is approved, it will be squashed & merged, intodevelop and later merged intorelease/{No} for deployment.