octolanding

octolanding is a deliberately minimal, static-only Docker image designed to serve as a default landing page for infrastructure entry points.

It answers a simple question safely and intentionally:

"What should someone see when they land on this?"

Instead of exposing an application, redirecting to a random service, or leaking infrastructure details, octolanding serves a single static HTML landing page — nothing more.

What it is

• A tiny BusyBox-based HTTP container
• Static HTML & CSS only
• No PHP, no CGI, no server-side scripting
• No configuration required
• Mountable document root for easy overrides

What it's for

• Default IP landing pages
• HAProxy / OPNsense fallback backends
• Gateways and DMZ entry points
• Infrastructure courtesy pages
• Intentional "nothing lives here" endpoints

What it is not

• A web application
• A CMS
• A framework
• A general-purpose web server

octolanding is meant to be boring, predictable, and safe - built once, reused everywhere, and forgotten about until it's needed.

Minimal usage (default landing page)

services:
  octolanding:
    image: octoleo/octolanding:latest
    container_name: octolanding
    ports:
      - "80:80"
    restart: unless-stopped

This serves the built-in default landing page.

Override with your own HTML

services:
  octolanding:
    image: octoleo/octolanding:latest
    container_name: octolanding
    ports:
      - "80:80"
    volumes:
      - ./www:/www:ro
    restart: unless-stopped

Folder structure:

www/
 ├── index.html
 ├── maintenance.html
 └── info.html

• Any number of static HTML files supported
• No configuration changes required
• Volume fully overrides the built-in page
• If no volume is mounted, octolanding serves the built-in default page.
• Mounting /www replaces the default content entirely.
• The container serves static files only and cannot execute code.

License

Copyright (C) 2021–2026
Llewellyn van der Merwe

Licensed under the GNU General Public License v2 (GPLv2)
See LICENSE for details.