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
Having a solution that works for you is never a bad thing.
Now it comes down to what you want to archive: Do you want something that just works? Great, you're done - now go on and do some other things that you like, that's perfectly fine. Or do you want to learn more about servers, virtualization, linux, networking and selfhosting in general? Then there are a million ways to get started.
I'd suggest to setup a little lab, if you haven't already. Install Proxmox on your server and run CasaOS inside a virtual machine. Now you've learned about hypervisors and virtual machines. Afterwards you could create a second virtual machine to play around - maybe install debian and get used to the linux cli. Install docker manually, run some apps using docker-compose. Now you're already doing some stuff that CasaOS does under the hood.
The possibilities are endless, the rabbit hole is deep. It can be a lot of fun, but don't force youself to go down there if you don't want to.
I second this - virtualization is the easiest way to branch out and try new things. You can keep the working system you already have, and also experiment with other systems.
A further advantage is that you can run services in separate VMs, which helps if you need isolated contexts for security, privacy, or stability reasons. And, if you break something while you're learning you can just delete that VM and start over without affecting your other working services.