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
So I am a total amateur, but i set up a TrueNas server that hosts my Plex server, then set up a linux VM to host a PiHole.
I also set up nextcloud vm on that machine too, i wanted to autobackup my phone pics and have a sync'd, shareable calendar with the family.
Nextcloud was the biggest pain in my ass and i never truely got it working as advertised. I ended up scrapping that part just because of how god-awful nextcloud was, and god forbid you try and update it to the most recent version.
You should really use the Nextcloud docker-compose files to setup Nextcloud. They make it stupidly easy to deploy. Pair that with SWAG as a reverse proxy and you get a pretty secure Nextcloud deployment complete with SSL certs.
Come to think of it, why not also run pihole in a docker instead of a full VM?
I ran it with the nextcloud docker-compose, and it was flaky af. I know for lots of people it runs great, and I’m glad for that. For me, I had to scrap it.
Could have been the db software you were running with it. It’s best to do that externally with something like mariadb. Not trying to convince you, just in case others are trying to make a decision between vm or docker.
For what it’s worth, I just checked my docker-compose and when I was running it, I was using a separate mariadb container for the db.
What sort of flakiness?
Scrapped nextcloud for the same reason. I was able to get it running the way I wanted, but goddam if nextcloud didn’t irrevocably break if you so much as cut a loud fart near the server.
Updating nextcloud was out of the question.
I did the same as you, but wanted native performance on my Linux machine, so what was awesome was I was able to export my zfs pool from truenas and spool up a Linux distro and import it. There's a project called cockpit and it has a zfs plugin which makes it easy to manage like truenas, but you can also use it as a whole ass pc at the same time
I agree that Nextcloud is a pain in the ass most of the time but FWIW the official AIO + reverse proxy method has served me well. I run it in a proxmox LXC container so it's pretty tidy, upgrades tend to work well and it doesn't force its own reverse proxy/certificate management on me.