You either use the YAML file to configure ports or you blind-mount the configs in local env. Most of my laravel environments are copy-pasted from older ones with the difference of database engine and php extensions / presence of things like pcov or xdebug.Īnd you don't step into containers to open ports or change configs. What I do not want is to believe that one command can do it for me magically. It takes 5 seconds to swap projects.Īnd I do want to fiddle with configs of docker container since I do want to use that FPM instead of Apache + phpmod, I do want to enable opcache on my dev environment to check how well it boosts performance, and I do want to implement my own nf file on example to intercept the proxy header with real IP. Docker projects spins up very quickly, its not a VM. Whenever I work on one project the second one is down and opened ports are mostly 80/443 and one for database UI like adminer so let it be 8080. I am not going to remember which project uses which port. I do not run multiple docker projects at a time. It's good for a small company focused in Europe where we don't need 24/7 performance. We just pick the image and we only pay by execution time. The company I work for does, we use GCP's Cloud Run service which handles running the containers. You might even lose data from that.ĭo people actually use docker for production? You can't scale traditional setups like Forge gives you, you database/cache/web server on the same box means they're all fighting for resources so it can become a cluster fuck if one part misbehaves. Performance wise, it can be better but then, it depends if scalability is something you want. I'd say it's just as good, you should have everything in a private network ideally anyways. Natively providing more performance and security as well But even then the point is they're containers so if you have nginx/php on the same image so if they're accessed these containers can be destroyed instantly and redeployed. It's something you're supposed to lock down root in your final images. If I'm not mistaking docker still runs as root, right?
0 kommentar(er)
