Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How I built this website on a Raspberry Pi

mirawelner.com

Post reply on HN
Print view View original

41–50 of 94 posts

Re: How I built this website on a Raspberry Pi

#41

Post by justin66 »

ekianjo wrote: post #29
rednafi wrote: post #25

I like how the author didn’t try to be overly clever with it. They could’ve used Docker to install and isolate dependencies, Caddy or Traefik to serve the site and manage SSL automatically, maybe even k3s to run a mini cluster for HA, Tailscale to avoid manual port forwarding, Terraform for future auto-provisioning without hassle, or Ansible to prepare the machine and all that jazz. Instead, they took the simplest po…

> installing the web server on bare metal, On top of a Linux distro is not what people usually call bare metal

I'm sure 100% of the people who read that comment understood what it meant.

Re: How I built this website on a Raspberry Pi

#42

Post by Dalewyn »

ekianjo wrote: post #29
rednafi wrote: post #25

I like how the author didn’t try to be overly clever with it. They could’ve used Docker to install and isolate dependencies, Caddy or Traefik to serve the site and manage SSL automatically, maybe even k3s to run a mini cluster for HA, Tailscale to avoid manual port forwarding, Terraform for future auto-provisioning without hassle, or Ansible to prepare the machine and all that jazz. Instead, they took the simplest po…

> installing the web server on bare metal, On top of a Linux distro is not what people usually call bare metal

However many layers of abstractions deep you are, please try and get yourself out of there. The air down there ain't good for ya.

Re: How I built this website on a Raspberry Pi

#43

Post by Izmaki »

a1o wrote: post #39

Hey, if one is only using apache and serving static files, is there any security issue one needs to be in the lookout? I was surprised fail2ban was the only thing installed there and it seems reliably working.

If you keep Apache itself up-to-date then typically speaking no. There is always a reason to be on the lookout and , but static files are - well - static. Not much to mess with there.

If you choose to do smart things like caching and such, that opens a whole new can of worms, but basic "this is my HTML page" stuff is typically "not-unsafe" (as opposed to "safe").

Re: How I built this website on a Raspberry Pi

#44

Post by InMice »

Surpised he does not have a step for a assigning a permanent address for the local network. He mentions it but skips it like it's not needed. a lot of routers like those from att do not allow port forwarding to addresses that have finite lease times.

Re: How I built this website on a Raspberry Pi

#47

Post by hoppp »

rednafi wrote: post #25

I like how the author didn’t try to be overly clever with it. They could’ve used Docker to install and isolate dependencies, Caddy or Traefik to serve the site and manage SSL automatically, maybe even k3s to run a mini cluster for HA, Tailscale to avoid manual port forwarding, Terraform for future auto-provisioning without hassle, or Ansible to prepare the machine and all that jazz. Instead, they took the simplest po…

If its for you there is no need to overcomplicate it. Complexity is just for job security :)

Re: How I built this website on a Raspberry Pi

#48

Post by icedrift »

rednafi wrote: post #25

I like how the author didn’t try to be overly clever with it. They could’ve used Docker to install and isolate dependencies, Caddy or Traefik to serve the site and manage SSL automatically, maybe even k3s to run a mini cluster for HA, Tailscale to avoid manual port forwarding, Terraform for future auto-provisioning without hassle, or Ansible to prepare the machine and all that jazz. Instead, they took the simplest po…

I appreciated this as well. Going in I was expecting a long winded technical report detailing npm compatibility issues or bundle size optimizations but no, they're simply setting up an apache webserver and shipping HTML/CSS.

Re: How I built this website on a Raspberry Pi

#49

Post by hoppp »

reassess_blind wrote: post #27

Any DDoS protection? Doesn't really matter with a small personal site, but I run a few solo production apps and they get hit multiple times a month by >100k rps DDoS attacks.

Me too, I need to use cloudflare... I think if he gets hit by a ddos, the pi can go down but since its a simple website and not monetized, the downtime is fine

Re: How I built this website on a Raspberry Pi

#50

Post by rednafi »

ekianjo wrote: post #29
rednafi wrote: post #25

I like how the author didn’t try to be overly clever with it. They could’ve used Docker to install and isolate dependencies, Caddy or Traefik to serve the site and manage SSL automatically, maybe even k3s to run a mini cluster for HA, Tailscale to avoid manual port forwarding, Terraform for future auto-provisioning without hassle, or Ansible to prepare the machine and all that jazz. Instead, they took the simplest po…

> installing the web server on bare metal, On top of a Linux distro is not what people usually call bare metal

Yeah. I used it for a lack of better term. But you get the idea.
Post reply on HN