✳flâneur — a map of the web's best reading

My personal reasons to not run my Nginx reverse-proxy inside Docker - Ewald Benes

ewaldbenes.com · 927 words · saved by 1 readers

This text explains why, in my situation, wrapping my reverse-proxy (Nginx) with Docker is a disadvantage. Your situation is likely different. Docker is a useful technology that serves us software engineers well in many areas. I use it at work all the time although I do not consider myself a Docker pro. As with any technology, it has merits and demerits in certain situations. I will weigh the pros and cons carefully and explain my judgment. Explaining how my infrastructure looks like will help set a baseline for you to understand and compare it to your situation. I use Nginx as a reverse-proxy that serves 10 websites and web applications. They live on a single VPS that runs Ubuntu Linux. I update my Nginx configuration infrequently, typically to add a new website by configuring a new virtual host. A refresher on what Docker does for us developers. To assess situations like this in a qualitative way, I take inspiration from the "Failure mode and effects analysis". The FMEA was developed

My personal reasons to not run my Nginx reverse-proxy inside Docker This text explains why, in my situation, wrapping my reverse-proxy (Nginx) with Docker is a disadvantage. Your situation is likely different. Docker is a useful technology that serves us software engineers well in many areas. I use it at work all the time although I do not consider myself a Docker pro. As with any technology, it has merits and demerits in certain situations. I will weigh the pros and cons carefully and explain my judgment. My setup Explaining how my infrastructure looks like will help set a baseline for you to

Explore this link on the map →

saved by

related reading