from docker-php.

Every solution has its use.

1. Monolith: every software runs on 1 host including 1 filesystem
2. Monolith deployed in 1 container, same as 1. - the entire app in one container
3. Separate database: dedicated host providing more resources, easy to connect through TCP - slower than UDS
4. Database cluster: higher availability, much greater performance
5. Separate services: static file serving, running the application, other services like a search service written in another language, e.g. https://github.com/meilisearch - you may have to use a shared filesystem
6. Service clusters: services can scale - there must be a load-balancer and a fully automatic deploy mechanism for each service

from docker-php.

Major Update:

• I've spent a lot of time cleaning these images up
• We have a number of production apps running these images (and things have been quite stable 😅🤞)
• I even added PHP 8.0 support

Special thanks

• @fideloper: Thanks for making such a kick ass course, Shipping Docker. The knowledge you shared is extremely valuable.
• @szepeviktor: Thanks for all of your help and feedback. I always appreciate learning from better developers. If you're interested, I created an issue specifically for you to roast my work 🤣: #16

Keep building awesome things! 🚀

from docker-php.

Update where I am leaving off today

• New structure is in place with the dependencies
• I have the Github actions working nicely with the different versions (https://github.com/serversideup/docker-php/actions/runs/637279973)
• I decided to follow the same structure of PHPDocker.io where everything is placed in its own DockerHub repo: https://hub.docker.com/orgs/serversideup/repositories

Next Steps

Time to start populating things with PHP 🤠

from docker-php.