Thanks for the reply Andrew!
Had a look at those links, and Im familiar with the auto deploy script/post hook having used that with bitbucket, but didn't like the fact that I couldn't deploy based on branch rather than always, so thanks for that bash script, thats pretty nifty!
Came across, bedrock ( https://github.com/roots/bedrock ) which is interesting but doesn't yet support Vagrant or a method of syncing dbs, but the closest Ive come across that implements pagoda/heroku is the dokku app.
1. What are your thoughts on easyengine ( https://github.com/rtCamp/easyengine ) or puphpet ( https://puphpet.com ) ?
2. Back to implementing gitlab as a nginx server block @ gitlab.domain.com, is that ideal/practical compared to having the gitlab.domain.com under its own droplet?
3. I love the idea of setting up a boilerplate so to speak, and creating a snapshot from it to easily create new projects! If using vagrant, however, you mentioned there might not be a need for it. If not using vagrant, would the best method for keeping teams in sync be to launch the droplet from the image, setup the wordpress install on the remote first, then pull it everything down w/ a sql dump?