harbormaster
Portainer
Our great sponsors
harbormaster | Portainer | |
---|---|---|
27 | 336 | |
- | 28,644 | |
- | 1.5% | |
- | 9.8 | |
- | 7 days ago | |
TypeScript | ||
- | zlib License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
harbormaster
- Harbormaster: The Tiniest Container Orchestrator
-
Ask HN: What hardware are you running for your home server?
I use an HP ProLiant Microserver with four drives in a ZFS RAIDZ array and an SSD for the OS. For software, I mostly run it in Docker using a very small container orchestration program I wrote:
- MRSK vs. Fly.io
-
I am a one-man show: Deployment and infrastructure for a 150k/m visits webapp
I needed something that would restart containers automatically when I pushed to a branch, so I wrote a few lines of code to do it:
https://gitlab.com/stavros/harbormaster
As far as PaaSes go, it's probably the simplest, and works really well.
-
My VM is Lighter (and Safer) than your Container
I was in the same boat as you and built something simple that I really like:
https://gitlab.com/stavros/harbormaster
It'll just pull some repos, make sure the containers are up, and make your configuration simple and discoverable. It really works great at that.
-
Exposing a web service with Cloudflare Tunnel
I do this for our services, it works great and we can easily put SSO in front of them with CF Access. I publish a Docker container that you can use as a sidecar for your Compose deployments:
https://gitlab.com/stavros/docker-cloudflared
I use this with Harbormaster (https://gitlab.com/stavros/harbormaster) so I can expose containerized stuff without ever forwarding any ports outside of Docker.
-
I Miss RSS
I use Dokku for that (I can share my Bitwarden repo if you want, the entire thing is four lines or something). I also made https://gitlab.com/stavros/harbormaster for things that weren't so "web server -> app -> database" and love it.
-
Self-Hosting Dozens of Web Applications and Services on a Single Server
I had the same problem and didn't want to manage things by hand, so I wrote Harbormaster:
https://gitlab.com/stavros/harbormaster
It basically pulls Compose apps from the git repositories you specify, builds the containers and makes sure they're running. Pretty simple and works really well for me.
-
Setting Up Cloudflare Argo and Access on a Raspberry Pi
(This post should read "Argo tunnel" instead of just "Argo")
I did the same to enable secure access to services via SSO at work. I used Harbormaster[1] to deploy Compose files, but it's otherwise the same setup.
One of the big advantages this has is that the services can't be accessed any other way (not even from the same host, as they only listen inside the Docker network). That makes it hard to forget some port exposed because you listened to 0.0.0.0 instead of localhost.
Cloudflare access is very easy to set up SSO with, as well. I'd recommend this setup if you need it, though for home usage I usually just set up Caddy as a reverse proxy with basic auth, as I'll be the only person using this and I don't want Cloudflare MITMing my personal stuff.
-
What is the cleanest way to deploy a docker-compose stack to a remote server?
Something like harbormaster? https://gitlab.com/stavros/harbormaster
Portainer
-
Runtipi: Docker-Based Home Server Management
> Any tips on the minimum hardware or VPS's needed to get a small swarm cluster setup?
From my testing, Docker Swarm is very lightweight, uses less memory than both Hashicorp Nomad and lightweight Kubernetes distros (like K3s). Most of the resource requirements will depend on what containers you actually want to run on the nodes.
You might build a cluster from a bunch of Raspberry Pis, some old OptiPlex boxes or laptops, or whatever you have laying around and it's mostly going to be okay. On a practical level, anything with 1-2 CPU cores and 4 GB of RAM will be okay for running any actually useful software, like a web server/reverse proxy, some databases (PostgreSQL/MySQL/MariaDB), as well as either something for a back end or some pre-packaged software, like Nextcloud.
So, even 5$/month VPSes are more than suitable, even from some of the more cheap hosts like Hetzner or Contabo (though the latter has a bad rep for limited/no support).
That said, you might also want to look at something like Portainer for a nice web based UI, for administering the cluster more easily, it really helps with discoverability and also gives you redeploy web hooks, to make CI easier: https://www.portainer.io/ (works for both Docker Swarm as well as Kubernetes, except the Kubernetes ingress control was a little bit clunky with Traefik instead of Nginx)
- Cómo instalar Docker CLI en Windows sin Docker Desktop y no morir en el intento
-
Setup Portainer for Server App
In this section, we will add Portainer to help us in managing our Docker containers. You can find more details about it here. To integrate Portainer into our EC2 project, we can follow these steps:
-
Old documentation url on Github issues gives ERR_TOO_MANY_REDIRECTS.
Git issues pointing to: https://docs.portainer.io/v/ce-2.9/start/install/agent/swarm/linux gives a ERR_TOO_MANY_REDIRECTS.
-
Docker CI/CD with multiple docker-compose files.
I am currently running Portainer, but webhooks (GitOps) appear to be broken ( [2.19.0] GitOps Updates not automatically polling from git · Issue #10309 · portainer/portainer · GitHub ) and so I cannot send webhook to redeploy a stack. So, looking for alternatives. Using this as a good excuse to learn more about docker and CI/CD etc.
-
Ask HN: How do you manage your “family data warehouse”?
A Synology NAS running Portainer (https://www.portainer.io/) running Paperless NGX (https://github.com/paperless-ngx/paperless-ngx)
This works better than I can possibly tell you.
I have an Epson WorkForce ES-580W that I bought when my mother passed away to bulk scan documents and it scans everything, double-sided if required, multi-page PDFs if required, at very high speed and uploads everything to OneDrive, at which point I drag and drop everything into Paperless.
I could, thinking about it, have the scanner email stuff to Paperless. Might investigate that today.
Paperless will OCR it and make it all searchable. This setup is amazing, I love living in the future.
-
Bare-Metal Kubernetes, Part I: Talos on Hetzner
> I've come to the conclusion (after trying kops, kubespray, kubeadm, kubeone, GKE, EKS) that if you're looking for < 100 node cluster, docker swarm should suffice. Easier to setup, maintain and upgrade.
Personally, I'd also consider throwing Portainer in there, which gives you both a nice way to interact with the cluster, as well as things like webhooks: https://www.portainer.io/
With something like Apache, Nginx, Caddy or something else acting as your "ingress" (taking care of TLS, reverse proxy, headers, rate limits, sometimes mTLS etc.) it's a surprisingly simple setup, at least for simple architectures.
-
What are some of your fav panels and why?
casaos it just makes things like backups, offsite syncing and many other nas related things so much easier to manage. And gives you a proper nas like experience similar to that in which you'd fine on companies like tnas or synology. I actually also use it as a replacement for portainer when i don't need the more advanced features it offers
-
Kubernetes Exposed: One YAML Away from Disaster
> I moved to docker swarm and love it. It's so much easier, straight forward, automatic ingress network and failover were all working out of the box. I'll stay with swarm for now.
I've had decent luck in the past with the K3s distribution, which is a bit cut down Kubernetes: https://k3s.io/
It also integrates nicely with Portainer (aside from occasional Traefik ingress weirdness sometimes), which I already use for Swarm and would suggest to anyone that wants a nice web based UI: https://www.portainer.io/
Others might also mention K0s, MicroK8s or others - there's lots of options there. But even so, I still run Docker Swarm for most of my private stuff as well and it's a breeze.
For my needs, it has just the right amount of abstractions: stacks with services that use networks and can have some storage in the form of volumes or bind mounts. Configuration in the form of environment variables and/or mounted files (or secrets), some deployment constraints and dependencies sometimes, some health checks and restart policies, as well as resource limits.
If I need a mail server, then I just have a container that binds to the ports (even low port numbers) that I need and configure it. If I need a web server, then I can just run Apache/Nginx/Caddy and use more or less 1:1 configuration files that I'd use when setting up either outside of containers, but with the added benefit of being able to refer to other apps by their service names (or aliases, if they have underscores in the names, which sometimes isn't liked).
At a certain scale, it's dead simple to use - no need for PVs and PVCs, no need for Ingress and Service abstractions, or lots and lots of templating that Helm charts would have (although those are nice in other ways).
-
What kind of Alpine user are you?
The control panel is called Homepage. I like it more than Heimdall. To manage Docker I use Portainer.
What are some alternatives?
swarmpit - Lightweight mobile-friendly Docker Swarm management UI
Yacht - A web interface for managing docker containers with an emphasis on templating to provide 1 click deployments. Think of it like a decentralized app store for servers that anyone can make packages for.
ufw-docker - To fix the Docker and UFW security flaw without disabling iptables
nixos-infect - [GPLv3+] install nixos over the existing OS in a DigitalOcean droplet (and others with minor modifications)
podman - Podman: A tool for managing OCI containers and pods.
docker-box - A lightweight docker application platform for single servers.
OpenMediaVault - openmediavault is the next generation network attached storage (NAS) solution based on Debian Linux. Thanks to the modular design of the framework it can be enhanced via plugins. openmediavault is primarily designed to be used in home environments or small home offices.
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
CasaOS - CasaOS - A simple, easy-to-use, elegant open-source Personal Cloud system.
neural-hash-collider - Preimage attack against NeuralHash 💣
podman-compose - a script to run docker-compose.yml using podman