Automating generation of nginx reverse proxy configuration using Go program by listening to docker meta data and provide reverse proxy configuration on fly.

1. `
Droplets Doc Versioning by
automating NGINX proxy
Paruchuru, Arihant Sai
aparuchuru@informatica.com

2. What is Versioning?
Versioning is known as existence of multiple models
of same product where each model varies based on
the features it provides.

3. 3 © Informatica. Proprietary and Confidential.3
Why Droplets-Doc needs Versioning?
Why this droplets
function is not working,
this is provided on the
doc website.
This is because you
are using older
droplets but referring
the latest
documentation
To avoid the above confusion
Droplets Consumer Droplets Developer

4. 4 © Informatica. Proprietary and Confidential.4
Issues doc-versioning can help us
address?
• Conveys breaking API changes in efficient manner
• Eases in switching to different versions of Droplets for consumers of droplets
• Enable DROPLETS team to build and maintain their own CI/CD pipeline (because we
know our code better than anyone)
PS: With this project DROPLETS will become the first product of Informatica to have it’s own CI/CD pipeline

5. 5 © Informatica. Proprietary and Confidential.5

6. 6 © Informatica. Proprietary and Confidential.6
Components and it’s Roles
NGINX
It works as a reverse proxy which helps us determine from which
docker container the request ahs to be served based on “Host” header.
Docker-Gen
A GoLang program which notifies any docker events on our docker host.
This helps us generating a new NGINX conf file whenever a new docker
container is launched. Every container has to be launched using ENV
variable “VIRTUAL_HOST”. The nginx conf file is written using GoLang
“Text/Template” library. This helps us providing zero downtime and
automatically restart nginx.
Each droplets-doc-website corresponds to a
unique docker container

7. 7 © Informatica. Proprietary and Confidential.7
Droplets doc CI/CD Pipeline
Every release of Droplets should be accessible to Droplets consumers immediately, rather than asking
our DevOps team to deploy it who will always cause a delay because of their own responsibilities.
Introduction of Jenkins pipeline will help us slowly kill our dependency on DevOps team. DROPLETS
team later will reap benefits given how rapidly DROPLETS is growing. For ex : Droplets playground
can start compiling against latest versions of Droplets within few minutes.

8. 8 © Informatica. Proprietary and Confidential.8

9. 9 © Informatica. Proprietary and Confidential.9