Live data from Hacker News

Self hosting in 2023

grifel.dev

91–100 of 307 posts

Re: Self hosting in 2023

#91
post #77

Not sure why you'd self-host a public site from home when you can get a VM from https://www.hetzner.com/cloud for € 4.81 /mo (1vCPU / 2GB RAM / 20 TB bandwidth) with much better internet access. Residential internet connections are more unreliable, have poor upload speeds and requires running a server 24/7 with ongoing electricity running costs. Or if it's a static rendered website you can publish on GitHub Pages for…

I don't think people are seriously doing self-hosting for practical reasons - it's more for the fun and pride of setting something up yourself.

Re: Self hosting in 2023

#92

Weird post. If this whole infrastructure is built just to render a static page, I can guarantee that from the point of view of someone reaching it out from Indonesia, then the PageSpeed wouldn't matter. It would be super slow. In fact https://gtmetrix.com/reports/grifel.dev/KDVSwSmr/ shows that render time of your page is 1.8s and TTI is 1.2 sec. Which is 4X times of what PageSpeed shows. I host my blog on CF Pages,…

[deleted]

Re: Self hosting in 2023

#93
post #70
post #16

The blog that you are currently reading has a perfect PageSpeed score 100 / 100. Unfortunately, no it doesn't. The page that has this blog post scored 95 in performance for mobile in one run and 86 in the next. It scored 91 for desktop. They'd get a higher score by adding text compression and by serving static assets (all of them?) with an efficient cache policy.

Wait how do you add text compression?

Generally, you add mod_deflate, or a similar package, to .htaccess and add the mimetypes on a new AddOutputFilterByType line along with the algorithm. This is one page [1] that describes the process for apache or nginx, though there are millions of webpages that give various methods.

[1] https://blog.hubspot.com/website/gzip-compression

Re: Self hosting in 2023

#94
post #5

If you don't need all that cloud operations/deployment infrastructure, self hosting a website from home in 2023 is as easy as it was in 2003. Get a DDNS, do the NAT port forwarding, run some apache/nginx/whatever and push your files with sftp or similar to the server. In contrast to 2003, upstreams got better -- even Germany has average upstream speeds of 20mbit/second nowadays [1]. With 20mbit/sec you can do quite s…

My problem is that I have never been able to purchase residential internet that allowed me to open port 443 or port 80.

Re: Self hosting in 2023

#95
post #34

Earlier quoted context omitted.

Yeah, I would decouple it from any residential ISP, but use a $4 VPS to still self-host. That also removes the need for a DDNS setup. Given some basic Linux skills, all you need is SSH plus nginx+certbot on Debian with unattended-upgrades or similar, that you can point your domain to.

Would recommend Tailscale over SSH. Really easy to setup/use and means you don't have to open up ports like 22 which are constantly being port scanned.

I'm not familiar with Tailscale, but you can easily use a different port than 22 for ssh if you want to; put a different port number in `/etc/ssh/sshd_config` on the server, and then set your `~/.ssh/config` to use that port on your clients. If you're going to be opening it up externally, you also can map a different port to the local one (which is necessary if you want to be able to ssh into two different servers with the same ssh port from the outside anyhow).

Re: Self hosting in 2023

#96
post #77

Not sure why you'd self-host a public site from home when you can get a VM from https://www.hetzner.com/cloud for € 4.81 /mo (1vCPU / 2GB RAM / 20 TB bandwidth) with much better internet access. Residential internet connections are more unreliable, have poor upload speeds and requires running a server 24/7 with ongoing electricity running costs. Or if it's a static rendered website you can publish on GitHub Pages for…

You don't control a VPS, uptime doesn't matter, and even my 5 Mb/s upload is just fine. Electrical costs are marginal. But most importantly there is nothing more convient than $ cp photo.jpg ~/www/ and sending someone the link example.com/photo.jpg. Plus you have tons of space.

That's not to say that a VPS in addition isn't useful or fun. https://indieweb.org/POSSE and all. It just isn't at all required.

Re: Self hosting in 2023

#97
post #5

If you don't need all that cloud operations/deployment infrastructure, self hosting a website from home in 2023 is as easy as it was in 2003. Get a DDNS, do the NAT port forwarding, run some apache/nginx/whatever and push your files with sftp or similar to the server. In contrast to 2003, upstreams got better -- even Germany has average upstream speeds of 20mbit/second nowadays [1]. With 20mbit/sec you can do quite s…

My problem is that I have never been able to purchase residential internet that allowed me to open port 443 or port 80.

Use Cloudflare. Or, rent the cheapest machine you can with a public IP and use something like Rathole. I like Cloudflare because it’s fast and free, but they do MITM you.

Re: Self hosting in 2023

#98

One thing to be mindful of is security. The last you want is for your setup to be compromised, be used to send spam/botnets and then getting perma-banned from your ISP. I would argue it's a lot less risky just to put your static site on S3/Github etc.

Using a web browser with JS execution enabled is a lot more dangerous than running nginx showing .html files in directories.

Re: Self hosting in 2023

#99
post #5

If you don't need all that cloud operations/deployment infrastructure, self hosting a website from home in 2023 is as easy as it was in 2003. Get a DDNS, do the NAT port forwarding, run some apache/nginx/whatever and push your files with sftp or similar to the server. In contrast to 2003, upstreams got better -- even Germany has average upstream speeds of 20mbit/second nowadays [1]. With 20mbit/sec you can do quite s…

True if you ignore certs and the possibility of CG-NAT.

Re: Self hosting in 2023

#100
post #77

Not sure why you'd self-host a public site from home when you can get a VM from https://www.hetzner.com/cloud for € 4.81 /mo (1vCPU / 2GB RAM / 20 TB bandwidth) with much better internet access. Residential internet connections are more unreliable, have poor upload speeds and requires running a server 24/7 with ongoing electricity running costs. Or if it's a static rendered website you can publish on GitHub Pages for…

You don't control a VPS, uptime doesn't matter, and even my 5 Mb/s upload is just fine. Electrical costs are marginal. But most importantly there is nothing more convient than $ cp photo.jpg ~/www/ and sending someone the link example.com/photo.jpg. Plus you have tons of space. That's not to say that a VPS in addition isn't useful or fun. https://indieweb.org/POSSE and all. It just isn't at all required.

I mean is scp any more difficult?
Post reply on HN