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

Source code

• Docker Engine 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. Nginx 1.27
2. PHP 8.3 fpm
3. MySQL 8
4. Symfony 7
5. RabbitMQ 3
6. Mailpit (only for debug emails on dev environment)

For installing Docker Engine with docker compose please follow steps mentioned on page Docker Engine.

Note 1: Please run next cmd after above step if you are using Linux OS: sudo usermod -aG docker $USER

Note 2: If you are using Docker Desktop for MacOS 12.2 or later - please enable virtiofs for performance (enabled by default since Docker Desktop v4.22).

1.You can clone this repository from GitHub or install via composer.

If you have installed composer and want to install environment via composer you can use next cmd command:

composer create-project systemsdk/docker-nginx-php-symfony example-app

2.Set another APP_SECRET for application in .env.prod and .env.staging files.

Note 1: You can get unique secret key for example here.

Note 2: Do not use .env.local.php on dev and test environment (delete it if exist).

Note 3: If you want to change default web port/xdebug configuration you can create .env.local file and set some params (see .env file).

Note 4: Delete var/mysql-data folder if it exists.

3.Add domain to local 'hosts' file:

127.0.0.1    localhost

4.Configure /docker/dev/xdebug-main.ini (Linux/Windows) or /docker/dev/xdebug-osx.ini (MacOS) (optional):

• In case you need debug only requests with IDE KEY: PHPSTORM from frontend in your browser:

xdebug.start_with_request = no

Install locally in Firefox extension "Xdebug helper" and set in settings IDE KEY: PHPSTORM

• In case you need debug any request to an api (by default):

xdebug.start_with_request = yes

5.Build, start and install the docker images from your terminal:

make build
make start
make composer-install

6.Make sure that you have installed migrations / messenger transports:

make migrate
make messenger-setup-transports

7.In order to use this application, please open in your browser next urls:

• http://localhost
• http://localhost:15672 (RabbitMQ)
• http://localhost:8025 (Mailpit)

1.You can clone this repository from GitHub or install via composer.

Note: Delete var/mysql-data folder if it is exist.

If you have installed composer and want to install environment via composer you can use next cmd command:

composer create-project systemsdk/docker-nginx-php-symfony example-app

2.Build, start and install the docker images from your terminal:

make build-staging
make start-staging

3.Make sure that you have installed migrations / messenger transports:

make migrate-no-test
make messenger-setup-transports

1.You can clone this repository from GitHub or install via composer.

If you have installed composer and want to install environment via composer you can use next cmd command:

composer create-project systemsdk/docker-nginx-php-symfony example-app

2.Edit compose-prod.yaml and set necessary user/password for MySQL and RabbitMQ.

Note: Delete var/mysql-data folder if it is exist.

3.Edit env.prod and set necessary user/password for MySQL and RabbitMQ.

4.Build, start and install the docker images from your terminal:

make build-prod
make start-prod

5.Make sure that you have installed migrations / messenger transports:

make migrate-no-test
make messenger-setup-transports

After application will start (make start) and in order to get shell access inside symfony container you can run following command:

make ssh

Note 1: Please use next make commands in order to enter in other containers: make ssh-nginx, make ssh-supervisord, make ssh-mysql, make ssh-rabbitmq.

Note 2: Please use exit command in order to return from container's shell to local shell.

In case you edited Dockerfile or other environment configuration you'll need to build containers again using next commands:

make down
make build
make start

Note: Please use environment-specific commands if you need to build test/staging/prod environment, more details can be found using help make help.

Please use next make commands in order to start and stop environment:

make start
make stop

Note 1: For staging environment need to be used next make commands: make start-staging, make stop-staging.

Note 2: For prod environment need to be used next make commands: make start-prod, make stop-prod.

Please use next make commands in order to stop and remove environment containers, networks:

make down

Note: Please use environment-specific commands if you need to stop and remove test/staging/prod environment, more details can be found using help make help.

make build
make build-test
make build-staging
make build-prod

make start
make start-test
make start-staging
make start-prod

make stop
make stop-test
make stop-staging
make stop-prod

make down
make down-test
make down-staging
make down-prod

make restart
make restart-test
make restart-staging
make restart-prod

make env-staging
make env-prod

make ssh
make ssh-root
make fish
make ssh-nginx
make ssh-supervisord
make ssh-mysql
make ssh-rabbitmq

make composer-install-no-dev
make composer-install
make composer-update

make info
make help

make logs
make logs-nginx
make logs-supervisord
make logs-mysql
make logs-rabbitmq

make drop-migrate
make migrate
make migrate-no-test

make fixtures

make messenger-setup-transports

make phpunit
make report-code-coverage

make phpcs
make ecs
make ecs-fix
make phpmetrics
make phpcpd
make phpmd
make phpstan
make phpinsights

etc....

Notes: Please see more commands in Makefile

• Symfony
• doctrine-migrations-bundle
• doctrine-fixtures-bundle
• command-scheduler-bundle
• phpunit
• phpunit-bridge
• browser-kit
• css-selector
• security-checker
• messenger
• composer-bin-plugin
• composer-normalize
• composer-unused
• composer-require-checker
• requirements-checker
• security-advisories
• php-coveralls
• easy-coding-standard
• PhpMetrics
• phpcpd
• phpmd
• phpstan
• phpinsights
• rector

• Commands
• Development
• Testing
• IDE PhpStorm configuration
• Xdebug configuration
• Messenger component

1. For new feature development, fork develop 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 into develop to get feedback, with the format feature/{ticketNo} - "Short descriptive title of Jira task".
4. Iterate as needed.
5. Make sure that "All checks have passed" on CircleCI(or another one in case you are not using CircleCI) and status is green.
6. When PR is approved, it will be squashed & merged, into develop and later merged into release/{No} for deployment.

Note: You can find git flow detail example here.

The MIT License (MIT)