I was dealing with a vagrant file, but it didn't work out for me. This made the whole process difficult and slowed down. Moreover, now I need to prepare for writing work for the academy. I've got not an easy topic, so it made the task doubly difficult for me. And this source helped to cope with this https://studentshare.org/education/1455293-impression-of-teaching-as-a-profession-with-the The examples of work were very useful in preparation and I got a lot of ideas and inspiration for writing.

A Vagrant box will be very helpful so that in conjunction with the Staging option on Cloudways we could have a LOCLA DEV > STAGING > LIVE setup

I would really love anything that helped me to replicate the server locally. This suggestion was made over 2 years ago. What progress is being made on this request?

Any progress on this initiative?

Would love a vagrant file! You can provision to docker via Vagrant anyways so, vagrant file would be the most ideal. being able to build on the same platform as live would be awesome!

Vagrant is more simple and more practial option for developers although Docker will work too.

Would love a docker image!

Hi Guys, another option for this is to just install apt-clone on the server. We can then use that to replicate the installed modules on a local/dev server.

If i could edit the title I would change it to allow us to replicate server locally. Vagrant, Docker or apt-clone are all valid ways to do this.

Thanks

Docker would be the container of the application that can be managed by Vagrant, so yes Docker image would be great to provide for testing purposes.

Personally I prefer Vagrant it has a slightly different use case to docker, because it works with any virtual infrastructure, I think its even included a docker provisioner as well.

https://www.quora.com/What-is-the-difference-between-Docker-and-Vagrant-When-should-you-use-each-one

I think the learning curve with Vagrant is less, and people can use whatever they already have, so you might find it easier to hit a wider userbase with Vagrant.

IF you go down the docker route, just provide a simple vagrant file so we can provision that, it is really just a single file, so would help.
https://www.vagrantup.com/docs/provisioning/docker.html

Paul

Thanks Paul. Would a docker image suit the same needs?. Assume so. We are leaning towards it for the exact same problem you mention.

Cloudways Team