Feat: add new docker for production & development environment

[toofff]

• [x] add new docker-compose.yml & Dockerfile layer divisions
  • [x] service php & configuration (env PROD & DEV)
    • [x] use php:74-fpm-alpine
    • [x] add docker-healthcheck
    • [x] update docker-entrypoint
      • [x] use php.ini PROD or DEV
      • [x] create important folders for the use of the project (public/files, public/theme, public/thumbs, var/cache, var/log & var/sessions)
      • [x] install vendor for development environment
      • [x] test BDD is active
      • [x] use php bin/console bolt:info instead of launching after installing vendors (because it is looking for the version of the database which might not be launched in time)
      • [x] if the theme does not exist, it will copy it
      • [x] if this project use DoctrineMigrationBundle then launch migrations (all env) else reset & create schema (only env DEV & TEST)
      • [x] launch fixtures
  • [x] service nginx & configuration (env PROD & DEV)
    • [x] copy public folder of php container
  • [x] service db with MySQL 5.7 version (only env DEV)
  • [x] service h2-proxy to have SSL (only env DEV)
  • [x] service mailcatcher to do (only env DEV)
• [x] add .dockerignore file
• [x] add .editorconfig file
• [x] replace .env.dist by .env file, to respect symfony's good practice
• [x] rework the .gitignore file
• [x] rework the Makefile file
• [x] rework the README.md file
• [x] rework the composer.json file & update dependencies
  • [x] bolt/core 4.0.1
  • [x] bolt/themes 3.3.2
• [x] update the symfony.lock file
• [x] fix the use of API-Platform
  • [x] the configuration (add path %kernel.project_dir%/src/Entity for the use of our own entity)
  • [x] install assets with the copy file
• [x] add dev dependency for ECS & PHPStan
• [x] upgrade documentation
• [x] rework commit in pull request

I added a CI for the installation of a Bolt project with Composer or Docker Compose.

• [x] Bolt project installation test with docker-compose, PHP 7.4 and MySQL
  • [x] Validate composer.json
  • [x] Run PHP-CS-Fixer
  • [x] Run PHP-CS-Fixer with fix flag
  • [x] Run PHPStan
  • [x] Run Security Checker
  • [x] Check HTTP reachability
    • [x] http://localhost:8080
    • [x] http://localhost:8080/bolt
    • [x] http://localhost:8080/api/contents
    • [x] http://localhost:8080/api/fields
    • [x] http://localhost:8080/api/relations
    • [x] https://localhost:8443
    • [x] https://localhost:8443/bolt
    • [x] https://localhost:8443/api/contents
    • [x] https://localhost:8443/api/fields
    • [x] https://localhost:8443/api/relations
• [x] Bolt project installation test with composer, PHP 7.4 and MySQL
  • [x] Validate composer.json
  • [x] Run PHP-CS-Fixer
  • [x] Run PHP-CS-Fixer with fix flag
  • [x] Run PHPStan
  • [x] Run Security Checker
  • [x] Check HTTP reachability
    • [x] http://localhost:8000
    • [x] http://localhost:8000/bolt
    • [x] http://localhost:8000/api/contents
    • [x] http://localhost:8000/api/fields
    • [x] http://localhost:8000/api/relations

The continuous integration is not yet working on this pull request because nothing is merged into the Bolt repository yet in my opinion. On the other hand you can see it working on my pull request in my fork

[toofff]

• Yes I deleted the .gitignore file in the public folder. I prefer to have the project rules at the root but above all it forces you to have server rules so that this file is not accessible in production if it is forgotten during deployment.

• Yes I deleted the .env.dist file in the root project. Here are the new specs on this file since Symfony / flex and Symfony 5

• For PHP 7.4 it is a proposal, I can downgrade if you wish? Even though I personally prefer to be on the last minor version of the 7.x branch for creating a new project.

I'm glad you welcome this work like this. I still have some work to do but you can already test it with a simple docker-compose up. Everything is functional at home.

If you have more proposals, I am interested ;)

[toofff]

@bobdenotter

Little question, do you know why we had a "node" container in the docker?

Great news, I think I finished it all this week. Don't hesitate to test and give feedback ;)

[bobdenotter]

Little question, do you know why we had a "node" container in the docker?

No, i'm afraid I don't.. I don't really use Docker myself.

Perhaps @JarJak (🛎️) knows?

[toofff]

@bobdenotter I still have the documentation to finish, I hope to deliver it to you this week for the review :smile:

[bobdenotter]

@toofff Excellent! Looking forward to it!

[toofff]

@bobdenotter Now I pass the torch to you for proofreading and testing locally. I remain at your disposal for any questions and changes to be made. :)

[bobdenotter]

@toofff Thanks!

It'll take me a little while to review, because I'd like to do it with care. Will let you know if any questions arise.

[simongroenewolt]

Little question, do you know why we had a "node" container in the docker?

I don't know if you still have this question, but I think the node container is to build/process the javascript for the (vue based) editor support in /bolt

[toofff]

Thanks @simongroenewolt I'm watching this this week.

[toofff]

@simongroenewolt @bobdenotter

For me the container node is not necessary here. From what I could understand, this container is only needed for "bolt/assets" development. So not necessary for end developers who will develop websites with "bolt/project"

[toofff]

@bobdenotter did you have time to test with and without docker?

[bobdenotter]

@toofff Is this 'good to go' for now? If so, we'll merge it in shortly, and we fine-tune it before release of a new version of this repo.

[toofff]

I try to finalize tomorrow and do my rebase so that it is mergeable

[toofff]

@bobdenotter It's good for me, I made the last corrections of the CI, the rebase of the master branch, the update of composer 2.

You can test by following the README.md file and merge if you like.

If you want to view the CI, it is available on my fork