Vagrant VS Puppet

You can give Vagrant a go (https://www.vagrantup.com). It is pretty handy for spinning up/down development VMs without even leaving your IDE.

Vagrant is a popular tool for launching virtual machines on your local desktop. https://www.vagrantup.com/

And, for the record, if you ever need to do something cross falls down on and Docker isn't suited to (eg. some of my sites are on a shared webhost that uses FreeBSD), the simplest way I've found is to use Vagrant with a script like this to run inside Vagrant to copy the project in, trigger a build, and then copy the binary out.

Have a look at vagrant to spin up VMs quickly, then use 'em to do stuff like configure a salt environment - you could incorporate cron jobs here ;)

I was building a new version of YugabyteDB vagrant box with packer and virtual box. Because we (Yugabyte) have a new preview release out.

I also suggest having a look at Vagrant (https://www.vagrantup.com/) for learning kind of work. It makes running isolated env easy and clean.

Another point to consider is how difficult is it to install the API Gateway or redeploy the gateway when changes are made. Check what installation options are offered. Most modern API Gateways can be installed in many different ways(Package based, Docker, Helm, RPM) in any environment (Linux, Windows, macOS). For example, one of the biggest advantages of Kong is its wide range of installation choices, with pre-made containers such as Docker and Vagrant so you can get a deployment running quickly.

Laravel wanted to make the entire PHP development process as seamless as possible. At the time, Laravel achieved this with Laravel Homestead, apre-packaged Vagrant box. Everything you would need would be bundled into a virtual machine, nice and neat, away from your OS. And this was how I was introduced to Vagrant. A means of packaging virtual machines into a portable format, so you could easily create local development environments. Vagrant worked by using a Vagrantfile to describe the virtual machine you would want to use, how it would be provisioned, the ports you would forward, and the filepaths you would want shared from host to guest. All of these tasks would be handled by the provider, the underlying virtual machine program itself, in my case, VirtualBox. Perhaps the one thing I liked the most about Vagrant, was the ability to provision my machine, clear down if I wanted to and have it back in a clean state for development.

I will happily direct your attention here: https://github.com/puppetlabs/puppet

We started by decoupling Puppet from Facter as much as we could, introducing the possibility of having multiple Facter backends. While Puppet would use the default Facter implementation when running on its own, external users would be able to define and pass their own Facter implementation when initializing Puppet, similar to how puppetserver configures Puppet to use its JRuby-compliant HTTP client.