Live data from Hacker News

Raspberry Pi as a local server for self hosting applications

cri.dev

231–240 of 321 posts

Re: Raspberry Pi as a local server for self hosting applications

#231
post #230

Earlier quoted context omitted.

Run it in a docker container

That solves nothing.

My assumption here was that you didn’t like some rando script running on your machine with escalated permissions.

I figured running it in a sandbox in a rocker container would be safer to you. Also, it’s easier to get up and running, though more difficult to update.

Re: Raspberry Pi as a local server for self hosting applications

#232

The hardware is there (RPi + USB storage). The server software is there (NextCloud, Plex, n8n, etc). What isn't there is the plumbing. The next logical step after this blog post is making your services accessible to your phone over the public net. You'll immediately find yourself mired in domain name registration, VPS management, TLS cert management, dyndns, port forwarding, hole punching, etc etc. There are lots of…

Cloudflare -> Router (only allows 80 443 trafic from cloudflare ips) -> nginx -> all selfhosted services (wiki, hass...)

Problems with the "easy" one click ones is that they tend to not be very secure. If they are supposed to be public access. Plex uses their cloud to secure the access and Synology to

Re: Raspberry Pi as a local server for self hosting applications

#233
post #30

I like my rpi but my life got better when I bought a mini pc instead. Its pretty common to get a 16GB mem micro for not much more than an rpi with power supply, sd card, case. https://computers.woot.com/offers/lenovo-thinkcentre-m73-240...

Yup, similar. I have a thinkcenter m600 series. Quite old but works really well.

I looked at these but got an old ThinkPad laptop instead. Integrated UPS, keyboard and mouse...

Re: Raspberry Pi as a local server for self hosting applications

#234
For simple, web-based speedtests on a local LAN/WLAN, I like librespeed[1]. Really helps identify subpar WiFi coverage (for example), better than just signal strength. Runs nicely on a Pi, up to line rate (1 Gbps) on a Pi 4.

[1] https://github.com/librespeed/speedtest

Re: Raspberry Pi as a local server for self hosting applications

#235

The hardware is there (RPi + USB storage). The server software is there (NextCloud, Plex, n8n, etc). What isn't there is the plumbing. The next logical step after this blog post is making your services accessible to your phone over the public net. You'll immediately find yourself mired in domain name registration, VPS management, TLS cert management, dyndns, port forwarding, hole punching, etc etc. There are lots of…

Start by having a look at subspace https://github.com/subspacecloud/subspace

Re: Raspberry Pi as a local server for self hosting applications

#236
post #66

Earlier quoted context omitted.

Very true for a given value of true 8) You need to evaluate all the components. The RPi itself is a decent piece of kit, well tested and safe to use. Get a decent power supply to it - either a RPi branded one or at least a decent mobile charger from a brand that you trust. I generally use a decent USB stick nowadays. RPi 4 from about a month or so ago onwards will do this out of the box. You can also put a second USB…

I am curious why you would use a fleet of them instead of a larger server.

I am an IT consultant and own the business. Home and work blur somewhat! I have a Dell tower (ESXi), a pfSense appliance, a micro mainboard based box, two ESP32s and a 24 port PoE+ switch in my attic. With a UPS and smoke detector. There's rather more stuff hidden away in cupboards and under the stairs. There's a 50m run of ethernet and SWA 240V (all ducted and marked etc) down to our summer house in the garden, which sports an eight port PoE+ switch, 2.4 and 5GHz wifi, and four double IP66 power outlets.

"Fleet" is a bit of an excessive term but I have four RPis at home, mainly for TV frontends for MythTV. There are rather more in the office.

The above is just a sample and not the whole story 8)

Re: Raspberry Pi as a local server for self hosting applications

#237
post #62

Earlier quoted context omitted.

I use a $15/year vps for this. Acts as a bastion to all the servers I connect to.

Where did you get $15/yr VPS?

You can find many low priced (and low spec) VPS deals on https://lowendbox.com. Just keep in mind you generally get what you pay for.

Re: Raspberry Pi as a local server for self hosting applications

#238
post #174
post #45

I'm using my old Thinkpad T510 as a home server. It's been running for 7+ years already. I only need to dust the vents once in a while. It has PiHole, Nextcloud, my humble little Netflix clone, and a few other things. If you use ffmpeg a lot, you ought to have more power than the RPi offers. I often SSH into it to use it as a SOCKS proxy in other countries.

Yep, older laptops make perfect home servers/routers. Built in "KVM switch", built-in UPS, low power/noise, etc. Before I switched to Ubiquiti I ran pfsense on a VM on my old 410s for many years, among other virtual machines for home lab use.

>low power/noise

how does that compare to RPI?

Re: Raspberry Pi as a local server for self hosting applications

#239
post #124

Setting up a pi-hole DNS server for my wifi network was one of the best decisions I've ever made. Horrifying to see what percentage of traffic is on the ad server blacklist though...

I wanted to do that, but I had a look at Pi Hole and ran away screaming. Instead of proper packaging, they have a 3000 line install script they want you to pipe into Bash. I went a saner route, and used dnsmasq and a blocklist[1] updated nightly via cron. Dnsmasq in turn queries Stubby that talks to uncensoreddns.org via DNS-over-TLS. Boom, DoT on my entire LAN. [1] https://github.com/notracking/hosts-blocklists

Would you feel better with a 3000 line install script inside a package? Or maybe you would prefer the same 3000 lines of code nicely compiled in a single binary?

Re: Raspberry Pi as a local server for self hosting applications

#240
post #180

This is probably way better achieved by a $5/mo VPS. Benefits: - way faster - always on (presumably battery backed) - you're not responsible for disk or hw failures - better internet (faster, redundant connections) - cheaper ($60/year vs $100 upfront) - not fighting architecture differences - comes with a public v4 address - usually comes with a v6 address too Downsides: - data isn't under your control and is subject…

$60/year is not cheaper than $100 one time, unless you plan to run the RPi for one year and then throw it away.
Post reply on HN