KamalakannanRM

Blue/Green deployments with NGINX

Blue/Green deployments is nothing new and the benefits of the methodology are well documented and already extensively discussed. For a quick description, it is when we have two identical copies of the production environment (one is called “Blue”, one is called “Green”) and only one of them is visible to the customers. We deploy to the inactive one and once we are happy the deployment is OK, we then switch them.

Config files

First we have the nginx.config that includes the server blocks for both the active and inactive versions of the app:

##################################

KamalakannanRM

ssl_certificate                 /etc/nginx/ssl/jenkins.domain.tld/cert.pem;
ssl_certificate_key             /etc/nginx/ssl/jenkins.domain.tld/privkey.pem;

upstream jenkins {
    server                      127.0.0.1:8080       fail_timeout=0;
}

server {
    listen                      80;
    server_name                 jenkins.domain.tld;

KamalakannanRM

ssl_certificate                 /etc/nginx/ssl/nexus.domain.tld/cert.pem;
ssl_certificate_key             /etc/nginx/ssl/nexus.domain.tld/privkey.pem;

upstream nexus {
    server                      127.0.0.1:8081       fail_timeout=0;
}

server {
    listen                      80;
    server_name                 nexus.domain.tld;

KamalakannanRM

ssl_certificate                 /etc/nginx/ssl/sonar.domain.tld/cert.pem;
ssl_certificate_key             /etc/nginx/ssl/sonar.domain.tld/privkey.pem;

upstream sonar {
    server                      127.0.0.1:9000    fail_timeout=0;
}

server {
    listen                      80;
    server_name                 sonar.domain.tld;