Say I want to host 20 php projects on one digital ocean server. How would I 
go about using PuPHPet and setting puppet scripts up in general such that I 
could host all 20 projects on the same server, residing in e.g. 
/var/www/project1, /var/www/project2 etc.
but each project would be able to have its own Vagrant file, and each 
project with the help of the Vagrantfile you could set up your own PHP 
environment for that one project. So e.g. you'd have a versioned Vagrant 
file for project1 which sets everything up so you could work with the 
environment very similar to production, making sure all the PHP extension 
dependencies are installed for that PHP project, placing the project into 
/var/www/project1 inside the Vagrant machine BUT not installing all the 
other, unrelated PHP projects next to it with their dependencies as it 
would take a lot of time to set all of them up every time someone does 
`vargant up`

So does this make sense? I basically want to be able to support hosting 
multiple projects of PHP in a server, but being able to make a 99% accurate 
virtual environment for each as well.

Normally all the tutorials for using PuPHPet and Vagrant assume that you 
want to 1 project onto 1 server and gives you a great virtualization for 
that which is 99.99% accurate, but I want to cut off a little bit accuracy 
and add some complexity in exchange for saving costs by not having to 
always open an entire new VM for every single project especially if many 
projects are very small.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/9b3d268d-d781-4b01-848e-4060026d889e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to