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 posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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
This is opening a can of worms. Are you going to be their support person? What if one person destroys the environment and someone elses work?
Exactly, I can’t let two users into the same VM server as administrators, like you said, they could manipulate other user’s resources. The front end to online VPS sites kinda give each user a cordoned off sandbox of resources to play in. Maybe if I gave each their own virtualized proxmox instance they could VPN into?
You might want to try Openstack. It is set up for running a multi-tenant cloud.
Heard of this. Need to look into devstack. Thank you for putting it back on my radar
This is the way.
It can be done. It's not worth the work involved. You could firewall off the two proxmox instances from each other and your own network. Then allow VPN access into the environment. You'll have to allow the machines access to the Internet to get software updates. The moment you do that you're opening the door to them making an outbound tunnel to make services publicly accessible. Then you've got every bot on the internet scanning your services for vulnerabilities/exploits.
Access to the outside world is where I start to not know what to do. If this was just locally run, I know how it would try and attack it, but the fact they they have to have access to the internet, that’s a hurdle I do not know how to get over.
I mean you could. Shell accounts did this back in the day but yes users could still abuse the system.