Open-source status page, incident response and uptime monitoring
TypeScript alertingincident-managementmcpmcp-servermonitoringmonitoring-as-codeobservabilityon-callopen-sourcesrestatus-pagestatuspagesynthetic-monitoringterraformtinybirdtursouptimeuptime-checkeruptime-monitor
feat: blog raspberry pi (#1461)
Maximilian Kaske29ed807ea826
diff --git a/apps/web/public/assets/posts/deploy-private-locations-raspberry-pi/dashboard-create-private-location.png b/apps/web/public/assets/posts/deploy-private-locations-raspberry-pi/dashboard-create-private-location.pngnew file mode 100644index 000000000..71dce178dBinary files /dev/null and b/apps/web/public/assets/posts/deploy-private-locations-raspberry-pi/dashboard-create-private-location.png differdiff --git a/apps/web/public/assets/posts/deploy-private-locations-raspberry-pi/dashboard-response-logs.png b/apps/web/public/assets/posts/deploy-private-locations-raspberry-pi/dashboard-response-logs.pngnew file mode 100644index 000000000..f5ac44e4cBinary files /dev/null and b/apps/web/public/assets/posts/deploy-private-locations-raspberry-pi/dashboard-response-logs.png differdiff --git a/apps/web/public/assets/posts/deploy-private-locations-raspberry-pi/raspberry-htop.png b/apps/web/public/assets/posts/deploy-private-locations-raspberry-pi/raspberry-htop.pngnew file mode 100644index 000000000..cb03dc0a4Binary files /dev/null and b/apps/web/public/assets/posts/deploy-private-locations-raspberry-pi/raspberry-htop.png differdiff --git a/apps/web/public/assets/posts/deploy-private-locations-raspberry-pi/raspberry-pi-receiver.jpg b/apps/web/public/assets/posts/deploy-private-locations-raspberry-pi/raspberry-pi-receiver.jpgnew file mode 100644index 000000000..f9392d93aBinary files /dev/null and b/apps/web/public/assets/posts/deploy-private-locations-raspberry-pi/raspberry-pi-receiver.jpg differdiff --git a/apps/web/public/assets/posts/deploy-private-locations-raspberry-pi/raspberry-pi.png b/apps/web/public/assets/posts/deploy-private-locations-raspberry-pi/raspberry-pi.pngnew file mode 100644index 000000000..42983ade7Binary files /dev/null and b/apps/web/public/assets/posts/deploy-private-locations-raspberry-pi/raspberry-pi.png differdiff --git a/apps/web/src/app/(pages)/(content)/layout.tsx b/apps/web/src/app/(pages)/(content)/layout.tsxindex a696fca33..0091be68b 100644--- a/apps/web/src/app/(pages)/(content)/layout.tsx+++ b/apps/web/src/app/(pages)/(content)/layout.tsx@@ -17,10 +17,10 @@ export default function ContentLayout({ children }: { children: ReactNode }) {function Banner() {return (<div className="border-b bg-muted/50 px-2 py-3 backdrop-blur-3xl">- <Link href="/blog/new-dashboard-we-are-so-back">+ <Link href="/blog/deploy-private-locations-raspberry-pi"><div className="group mx-auto flex w-full max-w-4xl flex-row items-center justify-between"><p className="font-medium">- We Are So Back - New Dashboard. More Monitors.+ Monitor from anywhere. Literally anywhere.</p><div className="text-nowrap"><span className="mr-1">Read more</span>diff --git a/apps/web/src/content/posts/deploy-private-locations-raspberry-pi.mdx b/apps/web/src/content/posts/deploy-private-locations-raspberry-pi.mdxnew file mode 100644index 000000000..9a3e9f931--- /dev/null+++ b/apps/web/src/content/posts/deploy-private-locations-raspberry-pi.mdx@@ -0,0 +1,227 @@+---+title: Deploy private locations on a Raspberry Pi+description: An 8.5MB Docker image running uptime checks from home.+author:+ name: Maximilian Kaske+ url: https://x.com/mxkaske+ avatar: /assets/authors/max.png+publishedAt: 2025-10-17+image: /assets/posts/deploy-private-locations-raspberry-pi/raspberry-pi.png+tag: engineering+---++We just pushed the first version of **Private Locations** at openstatus - and I had to test it on my old **Raspberry Pi 3**.++Since **2016**, I've been using the Pi for **AirPlay** to connect to my receiver but other than that, it's been sitting around without any other use case.++Time to revive it!++<ImageWithCaption+ src="/assets/posts/deploy-private-locations-raspberry-pi/raspberry-pi-receiver.jpg"+ alt="bare metal raspberrypi on a receiver"+ caption="My bare metal Raspberry Pi on top of the receiver I use for AirPlay"+/>++---++## Deployment Guide++Obviously connecting to the Raspberry Pi via `ssh` - and if you're like me, the default password is secure enough:++```shell+$ ssh [email protected]+> password: raspberry+```++### Hardware Specs++I didn’t know exactly which Debian version it was running, but it was _very_ old - so I took the opportunity to clean everything up and upgrade to the latest available version.++Model:++```shell+$ cat /proc/device-tree/model+> Raspberry Pi 3 Model B Rev 1.2+```++Linux Kernel:++```shell+$ uname -a+> Linux raspberrypi 6.12.47+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1 (2025-09-16) aarch64 GNU/Linux+```++Operating System:++```shell+$ cat /etc/os-release+> PRETTY_NAME="Debian GNU/Linux 13 (trixie)"+> NAME="Debian GNU/Linux"+> VERSION_ID="13"+> VERSION="13 (trixie)"+> VERSION_CODENAME=trixie+> DEBIAN_VERSION_FULL=13.1+> ID=debian+> HOME_URL="https://www.debian.org/"+> SUPPORT_URL="https://www.debian.org/support"+> BUG_REPORT_URL="https://bugs.debian.org/"+```++I'm running the OS on a **16GB micro SD** card. The Pi has **1GB of RAM**, which is perfectly enough for this use case.++<ImageWithCaption+ src="/assets/posts/deploy-private-locations-raspberry-pi/raspberry-htop.png"+ alt="htop stats"+ caption="Statistics from htop command"+/>+++### Install Docker Image++Let's freshly install **Docker** using the official Debian repository instructions:++https://docs.docker.com/engine/install/debian/#install-using-the-repository++Once installed, Docker should already be running.++You can verify it with:++```shell+$ sudo systemctl status docker+```++### Pull and Run the OpenStatus Container++Let's grab the image:++```shell+$ sudo docker pull ghcr.io/openstatushq/private-location:latest+```++If you have access to Private Locations in the **Dashboard**, create one - it'll will provide you a `token` to use as an environment variables:++<ImageWithCaption+ src="/assets/posts/deploy-private-locations-raspberry-pi/dashboard-create-private-location.png"+ alt="dashboard create private location form"+ caption="Create a private location"+/>+++Add the `token` to your shell profile:++```bash+$ echo 'export OPENSTATUS_KEY=<token>’ >> ~/.bashrc+```++Reload the shell profile:++```bash+$ source ~/.bashrc+```++If you are using `oh-my-zsh` you might be using the `~/.zshrc` file instead.++Check that it worked:++```bash+# print the env var+$ echo $OPENSTATUS_KEY+```++### Run the Container++Now let's launch it:++```shell+$ sudo docker run -d \+ --name openstatus-private-location \+ --restart=always \+ -e OPENSTATUS_KEY=$OPENSTATUS_KEY \+ ghcr.io/openstatushq/private-location:latest+```++What these flags do:+- `-d`: run in background (detached mode)+- `--restart`: auto-start on reboot+- `--name`: give it a nice readable name+- `-e`: pass your env var into the container++> Don't sleep on `--restart=always`! How often I had to quickly switch position of and need to reboot the Raspberry, this is a game changer.++To see live logs:++```shell+$ sudo docker logs -f openstatus-private-location+```++++---++### What Happens Next++Once the container is up, openstatus automatically fetches the endpoints you've chosen for this private location and starts monitoring them.++Every few minutes (`last_seen_at`), the agent refreshes its internal database to stay up-to-date with any changes - like added monitors or updated headers.++The responses of the pings are sent to our ingest endpoint for storage and aggregation.+++<ImageWithCaption+ src="/assets/posts/deploy-private-locations-raspberry-pi/dashboard-response-logs.png"+ alt="response logs in the openstatus dashboard"+ caption="Access your logs within the openstatus Dashboard."+/>+++### Light on Resources++Our Docker image is just **8.5 MB** in size. Compare that to 1GB+ for some competitors (yes, they pack more features, but still 🤯).++It's wild that a tiny 1 GB-RAM device from 2016 can now handle this so easily.++### Why Private Locations?++Running a private probe means your checks happen **from within your own network** - not just from public cloud servers.++It’s useful for:+- Monitoring internal applications or databases+- Testing network latency from real-world locations (like your office or home)+- Running low-cost monitoring nodes on tiny devices (e.g. in agriculture or industrial setups)++---++## Closing Thoughts++And that’s it - my **Raspberry Pi (2016)** is officially back in action. Running quietly next to my receiver, it’s now part of the openstatus network, checking endpoints from my home.++Not bad for a 9-year-old piece of hardware.++If you'd like to try this out yourself, contact us ([discord](https://openstatus.dev/discord), [email](mailto:[email protected])) and head over to:++https://github.com/openstatusHQ/openstatus/pkgs/container/private-location++Private locations are currently in **beta** and we're gathering feedback from early users. If you've got an old Raspberry Pi lying around - this is your excuse to bring it back to life.++---++**A few more useful Commands**++```shell+# stop running+$ docker stop openstatus-private-location+# remove the container, not the image or data:+$ docker rm openstatus-private-location+# remove unused images (docker keeps old images even after pulling updates)+$ docker image prune -f+# check docker image statistics+$ docker stats+# check the CPU / RAM usage (each work)+$ htop+$ top+# update docker image+$ docker stop openstatus-private-location+$ docker rm openstatus-private-location+$ docker pull ghcr.io/openstatushq/private-location:latest+$ docker run ... # same command as before+```\ No newline at end of file