improve deployment stage time execution + prevent loosing data in prod

[Gwada]

This pull request improves the deployment steps.

• Significantly reduced deployment time.
• Use of a lighter docker image.
• Docker layer management for advanced cache usage
• Removal of volumes to boost performance and reduce consumption of hardware resources
• Use of pnpm for installing dependencies (you know why)
• Prevent database dropping on each deployment

[rocambille]

Impressive one for improvement of deployment 🚀

Prevent database dropping might cause issues during development/deployment: SQL queries should be constructed and executed very rigorously from schema.sql with alter queries to allow column additions/deletions/modifications. This might be complex to handle for students. What do you think?

[Gwada]

Impressive one for improvement of deployment 🚀

Prevent database dropping might cause issues during development/deployment: SQL queries should be constructed and executed very rigorously from schema.sql with alter queries to allow column additions/deletions/modifications. This might be complex to handle for students. What do you think?

I agree with you. Managing migrations is complicated, and I think it's necessary for learners to be aware of the rigor these files require. It's good practice for their professional careers. Moreover, my learners have worked with this constraint and have not been hindered. Of course, they still have the option to delete the database if necessary, and the instructor can also do it in production via phpMyAdmin. Other solutions are also conceivable, such as using an ORM like Sequelize, which allows for better migration management.

• p3 Birdies-schema.sql
• p3 only-famous-schema.sql
• p3 street-art-hunter-schema.sql
  ...