Earlier quoted context omitted.
> 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.
It is the correct term
How I built this website on a Raspberry Pi
51–60 of 94 posts
Re: How I built this website on a Raspberry Pi
#52I did something similar in 2016 https://www.e-tinkers.com/2016/11/hosting-wordpress-on-raspb.... Instead of having Apache, I use Nginx. Instead of serving webpage from SD card, I setup a 512MB hard disk except booting still done via the SD card. The site is still running on a Raspberry Pi 3 till this day from my living room.
Re: How I built this website on a Raspberry Pi
#53Nice work, thanks for sharing! Do you plan to implement an RSS feed?
Re: How I built this website on a Raspberry Pi
#54Earlier quoted context omitted.
> 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.
You shouldn't back off a correct statement just because some rando on the internet challenges you. Bare metal is absolutely the correct terminology here.
Re: How I built this website on a Raspberry Pi
#55Earlier quoted context omitted.
Yeah. I used it for a lack of better term. But you get the idea.
You shouldn't back off a correct statement just because some rando on the internet challenges you. Bare metal is absolutely the correct terminology here.
Hehe. Not big on picking fights over minutiae. Also, English isn't my first language, so there's always a chance of making legit mistakes when picking terms. But in my 7 years of working in the industry, I've heard it used in this context by many.
Re: How I built this website on a Raspberry Pi
#56I 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 really appreciated the blog post because it taught me something I’ve always wanted to learn but avoided because PaaS made me complacent.
Three years ago, I tried to publish a website on a VPS in the morning to present it to a client at lunch. This was before ChatGPT. I spent hours trying but got nowhere. At the meeting, having failed to publish it, I had to run it locally and share my screen. I was frustrated.
Later, I discovered Heroku, which solved all my problems. Eventually, I migrated to VPS + CapRover, and now I use VPS + Coolify.
I’m happy with my setup—it works—but I’ve always felt guilty for not knowing how to publish a simple website without Docker.
Re: How I built this website on a Raspberry Pi
#57Very cool, very accessibly written. Thanks for sharing.
Curious how you handle your router’s public IP changing as (I believe?) this is pretty common depending on the ISP, no?
Re: How I built this website on a Raspberry Pi
#58To the OP:
Make sure you have updated firmware to latest, plus added active protection against the following known vulnerabilities.
https://nvd.nist.gov/vuln/search/results?form_type=Basic&res...
Re: How I built this website on a Raspberry Pi
#59I 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 really appreciated the blog post because it taught me something I’ve always wanted to learn but avoided because PaaS made me complacent. Three years ago, I tried to publish a website on a VPS in the morning to present it to a client at lunch. This was before ChatGPT. I spent hours trying but got nowhere. At the meeting, having failed to publish it, I had to run it locally and share my screen. I was frustrated. Late…
It took me much longer than I'd like to admit to publish my first bare-metal website on a VM. The main issue was SSL—I could never configure Nginx for multiple sites on the same server with TLS. Setting up DNS and pointing your domain to your server also requires some fiddling. It’s not intuitive, and there aren’t many people doing this, so resources with full end-to-end examples are limited.
However, with tools like Caddy and Let’s Encrypt, the process has become easier. That said, it still involves quite a bit of fiddling if you want to automate everything and make it reproducible without a lot of hassle. Now, I do it all the time for fun. But that said, if it's a static site, then I don't see much point in self-hosting when Cloudflare Page and GitHub Page are so much more convenient.
Re: How I built this website on a Raspberry Pi
#60[deleted]