• 4 Posts
  • 709 Comments
Joined 2 years ago
cake
Cake day: July 3rd, 2023

help-circle







  • Portainer is a container management system. It’s purpose is to allow you to manage containers in an easy to use GUI.

    ZaneOps is a PaaS that allows you to automatically build and deploy web apps into containers without having to configure the underlying infrastructure at all.

    For example, to deploy my static site on Portainer, I’d have to build my static site, containerize it, upload the container image to a registry (or directly to Portainer), then use Portainer to configure the environment and deploy the container. Then I’d have to configure a reverse proxy or web server to serve the contents of the container. If I wanted to continue working on that static site I’d need to configure some kind of CI/CD pipeline to try and automate all that previous work.

    With ZaneOps, I store the Astro/11ty/other SSG files in a Git repo, and on any commit ZaneOps will automatically recognize the SSG framework I’m using, use Docker Swarm to spin up a container to build the site into static files, containerize the resulting files for me, and deploy the container. It then uses Caddy underneath to serve what’s in the container including provisioning SSL certs for the site. It will health check the new container before deploying it in a blue/green deployment model so that the old site is removed only after the new one is up and available. It’s the same workflow as deploying a site to GitHub Pages using GitHub Actions if you’ve ever done that.

    Ultimately. You end up with the same result, a containerized workload, but ZaneOps takes your GitHub Repo and turns it into a built, running, containerized workload automatically. Automating the deployment of my own web apps using Portainer would be at the very least clunky and require a lot of surrounding infrastructure. It’s not something Portainer just does out of the box.

    Cockpit isn’t much like either, it’s just a web based server management tool.