Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
And another thing I have not heard yet. Dokploy looks really enticing just from a brief look at their site, I'll definitely add it to my list of things to look into. Thank you!
How long have you been running this type of setup?
How is swarm support/integration with Dokploy? Are you able to initiate the swarm and also connect other docker nodes to that swarm all through the webgui or does Dokploy just see and attach to the swarm after its been setup? Are you able to manage it all through the gui? Swing/motion containers to other nodes, etc.
I'll definitely need to deploy it in a test environment and see how it all works. Thank you again!
I've been running it for 2 years.
The swarm support integration is first class, but there is not much to do in the gui, you can add nodes and see basic info about them and thats it basically.
Most of the stuff happens in the compose files where you can define how many copies of a container you run and what nodes you want to restrict them to. etc.
I'm not sure about the moving features tbh. It should move them automatically when a node is down. In my setup I don't use that at all, all my containers are pinned to specific nodes by feature flags (one node has lots of hdd storage, another has more ram, another has a gpu).
You can see the container logs, but you have to select "swarm" in a dropdown when the container is not on your master node.
And also when deploying a new app you have to select "Compose" and then in a further dropdown "Swarm".