HTTPS-Portal: Automated HTTPS server powered by Nginx, Let’s Encrypt and Docker

Re:HTTPS-Portal: Automated HTTPS server powered by Nginx, Le... by zmmmmm on Friday September 14, 2018 @04:27AM (#17985599)

I've been using Docker for lots of things. To be honest, the dependency part has been helpful but still weak: we inevitably end up finding that our containers are built from things that go stale (apt-get sources, pip, broken URLs, stale SSL certs, etc). I guess there is a skill to doing it well so that this doesn't happen, but there you are - it didn't really solve the problem it's now an extra skill we need to have to solve a problem we had already mostly solved.

What has really sold me is more the orchestration side, with docker-compose allowing us to easily launch a whole fleet of independent services. I assume swarm and kubernetes etc., make this even better. It's really this that lets us decompose our software into finer grained independent components which has a number of other benefits. I don't think we could manage it otherwise.

[ Parent | on HN ]

Re:HTTPS-Portal: Automated HTTPS server powered by Nginx, Le... by unilynx on Friday September 14, 2018 @10:32AM (#17987457)

You still need to do a frequent build to detect broken dependencies, but at least setting up a daily docker build in CI is so much simpler and faster (and cross-platform!) than doing this with vagrant or live systems. At least you'll catch problems a lot sooner.

If you want to protect yourself from breaking dependencies, mirror them locally, and use a network-isolated docker build to verify you've actually got everything you need.

[ Parent | on HN ]

Re:HTTPS-Portal: Automated HTTPS server powered by Nginx, Le... by ric2b on Friday September 14, 2018 @01:47PM (#17989251)

The build process might break because of stale links, like you say, but already built images should continue to function everywhere unless you're doing something really weird.

[ Parent | on HN ]