Small WebApp (with purebasic stand-alone server)

This is a lightweight aviation weather web application based on official data from the German Weather Service (DWD). The project deliberately avoids bloated frameworks and complex stacks, focusing instead on a clean, minimal design with very few dependencies.

The bash-backend runs as cronjob on server or within oci-container and is seperated from the WebApp Frontend.

A small stand-alone webserver written in PureBasic, including a built-in reverse proxy for OpenStreetMap tiles let the WebApp run on every Windows or Linux w/o external runtimes and executable smaller than 2 MB each.

it’s kiosk-mode is ideal for Clubhouses, Pilot preparation Areas ans wall-mounted Information Displays.

20251216-dwd

4 Likes

At FL100 I had today ice warning at fl100 :slight_smile: Didn’t know you’re also a pilot

yep, you wanna something to read (in german) :slight_smile:

2 Likes

Very nice work — this is genuinely impressive. :rocket:

What really stands out is the stand-alone design: a single PureBasic executable handling HTTP requests directly, with no external runtime, web framework, or reverse proxy involved. That’s not trivial, and it appears to have been done very cleanly here.

I went down a similar path choosing PureBasic for a SCORM packager we use with a Learning Management System, largely for the same reasons — native compilation, small binaries, and zero runtime dependencies. Projects like this are a good reminder of how well PB fits that niche when you need something reliable and self-contained.

Thanks for sharing this — really enjoyable to look through.

1 Like

thank you, spread the word :wink:
you may then find this one useful aswell

Why bash-backend? Why not write everything in PureBasic?

because of jq, awk and wgrib2. These are well established and bullet-proof toolkits. You won’t try to re-develop and re-invent them in Purebasic. And bash gives every admin the flexibility to modify and transperency to see, what’s running on your server or oci-container.

It’s interesing that you all are focused on the webserver :wink:

All my brain-cells were thrown on the Javascript in the Frontend.
Purebasic was just available, quick and handy and w/o bloated frameworks like NodeJS or Python.

just optimized the purebasic stand-alone webserver with reverse-proxy to OSM. It has now a cache for every OSM tile. Once a tile is forwared and cached, it will never be loaded from OSM. This helps to reduce download times and traffic allows the stand-alone webserver be operated fully offline once all tiles downloaded.

1 Like