view the rest of the comments
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!
Hosting personal websites on your own hardware is such a pain, and I would imaging doing it on a rpi would be even more of a pain than on x86 architecture. If at all an option I'd recommend hosting on something like github pages or better still on a VPS.
@railsdev @innercitadel Do you not write your web apps in assembler..?
Ah OK, I might have assumed wrong then that running a server on ARM is a little trickier. Never done it. Only ever used nginx for my websites on my VPS. Don't want to deal with the security and uptime headaches of running my websites on my home server.
I was a bit nervous about this too but I just set up a kbin instance on ARM (nginx, php, postgres, redis, and more) and didn't notice any difference. Totally straightforward. And the VPS costs half as much as the x86 equivalent from the same host.
Oh wow genuinely interesting. Thanks, I've learned something. I had the wrong impression.
Well thanks, I guess. But do you have a recommendation? I'm sure a simple website won't cause any problems on a raspberry pi.
The main issue is not the website itself, but opening your network to be reachable from the internet in a safe way.
and sometimes you literally can't. see CG-NAT, something my ISP is doing, so fuck me right.
Yeah CGNAT makes things a pain in the ass but it's not a show stopper. Get a cheapie cloud VPS and install NGINX Proxy Manager (NPM) on it. Then do a WireGuard tunnel between your server and the cloud VPS. Problem solved. Or you could use Cloudflare tunnels but I wouldn't recommend that.
I hosted websites on my own hardware for 20 years and it worked out well Recently I've been using a VPS, and that has many benefits and drawbacks. Is it worth paying for the VPS? Maybe. That all depends on your situation.
I run 4 websites on my one VPS, and 2 websites on another more restricted cloud container service. Three wordpress, one DICOM server and viewer (radiology image database), one moodle, and one complex git mediawiki setup. Plus some sandbox stuff. Get about 10,000 unique views a day in total across all sites.
I don't know enough about network security to run that safely nor how to get great uptime at home as I run it all single handed and my day job has little to do with computers (am a medical doctor). I do expose some docker apps to the internet that run on my home server but they are only used by friends and family.
When I've needed temporary simple static web pages I've used jekyll on github pages and found it great.
How so? I've been doing it for 6 months or so now without issue.