By Amit Behere
We have a very basic setup with a single droplet. Currently in order to test changes we have to push them to the droplet and then they are available to all users. We don’t want that. We want a staging server. I have been reading articles about floating IPs and Blue-Green deployments. From what I understand, just floating IPs won’t be enough. There would still be a need for two droplets for code to be deployed. One having production code and one having staging code. The floating IPs would be use to switch from one to another once testing and QA is done. Am I correct in my assumptions?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
That all sounds right. Technically if may be possible to set up staging and production for some types of apps on a single droplet by using multiple databases and virtualhosts going with two seperate ones would be best practice to ensure that things stay separated.
I don’t think you want a floating IP for this. I think you want domain.com pointing to your production droplet and qa.domain.com pointing to your staging droplet.
Otherwise, when you repoint domain.com to your staging droplet, all users would be using your untested staging code (same effect as deploying the update directly to your production droplet).
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.