[kcole16]

Cool idea. I especially agree with this problem:

"It's hard for multiple developers to share one staging server".

My company has two staging servers, but with a team of 6 devs, someone often has to wait. Does anybody know of any solutions to spin up/down staging servers in a cost-effective way?.

[juliangregorian]

Partition them into VMs?

Alternately, I use vagrant-aws (https://github.com/mitchellh/vagrant-aws) to quickly do this on Amazon. Just be very careful to not check your keys into source control.

[smacktoward]

Yeah, VMs were my thought too -- VMs are easy to spin up and cheap/free, so why bother having everyone share one staging server? Use a configuration management tool like Chef/Puppet/Ansible/etc. to make sure everyone's staging VMs are configured the same, and you're good to go.

[tjmehta]

Hey Kcole, we are actually currently building product to solve this problem at Runnable, http://runnable.io. Email us at [e-mail] and we will be happy to give you an invite. We would love to hear what you think

[ac2u]

If your application is *nix based, then running a system with Docker at it's core could be an option. Some folks have a staging domain for their application, then use the SHA/tag of a release in a subdomain, and route based on subdomain to a running container.