Vagrant, Docker or what?

Do you mean for development or production? The use case matters.

@gthell - Yeah, what @ejdelmonico said. :) Personally, I stopped using vagrant in dev in favor of valet. I've got Docker in production and I really love a lot of things about it. That said, it isn't all rainbows and unicorns over in the Docker camp. I'm still stubbing my toes on things that wouldn't be an issue on an old school, everything-on-one-machine-and-one-OS installation.

@gthell I use docker for both. No point in using docker "only in production". Surely the idea is to duplicate your environment in a dev/test/live workflow?

I would suggest looking at minikube for local stuff. Allows you to run many docker containers inside an orchestration tool called Kubernetes. Maybe a bit much but a great thing to learn, very micro service focused if you like that stuff.

I'm setting up for production. My plesk panel is messy with php, composer and node. I'm thinking of reinstalling it. On my dev machine there is no need for environment because, you know, my macbook only has 128gb.

We use docker and vagrant. If we use docker on a project in production, that's what we use in dev. If we use just a traditional ubuntu stack in production, we use vagrant to mirror it in dev. Basically, just use whatever you're using in production while in dev, and you will rarely run into problems. It's when you mix them that you potentially open yourself up for gotchas and head scratchers. We just like things to work on deployment and not sit there "hey, but it's working on my dev box, why isn't it working on production?" That's just a giant waste of time and resources.