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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, your post is exempt from this rule as long as you continue to engage in comments.
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
So, in my case at least, having services spread across LXC containers and VMs, instead of various dockers stacks directly under on host, allows me to provide each service with its own internal IP address as opposed to having to worry about setting up 2 services with the same port because I can't remember I was already using that port. It's just cleaner that way.
Additionally, I get to create containers with the specific needs for each service to run comfortably.
It also allows for easier deployment and testing without much danger of ruining the host in something like CasaOS for example. If I have to make some adjustments to the host machine to make a docker stack run better, have more accesses, etc., I can have at it without fear that those changes could affect other docker stacks in the same host, because all hosts are contained.
Then there's the ease of management and deploying fully functional services with one line in the CLI of the host.
After running UnRaid, OMV, CasaOS and a few others, Proxmox has been the one system that is just so intuitive that I don't really have to think about it much. For the most part, deployments of pretty much anything just work.
Time to revisit my old habits
oh cool! all thoughts i have had to cross. i’ll check it out! thanks!
Any time.
You can run docker stacks with external IPs, no? I run all mine from Unraid, through Dockhand as compose stacks, with some ports on the host, others as external IPs on VLANs. But yes, like you I would actually like to move them to VMs so it's easier to backup, and service, without taking the host server offline.
It starts to get like Inception levels of depth on VMs and hosts!
Maybe I didn't get that far, plus, in UnRaid I had 1 tunnel for all the docker stacks, which made it mandatory (for me at least) to expose those services to the internet by having to play with the ports in many of them.
Just to reduce my ignorance, I'll research your suggestion. It seems like I never got that far. Thank you.