Proposal: Add idle-less (reverse proxy with Wake-on-LAN) example

[tvup]

Proposal

I'd like to add an example for idle-less — a Docker Compose setup that demonstrates a reverse proxy with automatic Wake-on-LAN for backend servers.

What it does

idle-less is a Docker-based reverse proxy that detects when backend servers are sleeping, sends a Wake-on-LAN magic packet, shows a waiting screen during boot, and forwards traffic when the server is up.

Why it's useful as an awesome-compose example

• Demonstrates Docker macvlan networking (required for Layer 2 WoL broadcast)
• Shows multi-service orchestration (nginx proxy + WoL gateway)
• Practical energy-saving pattern for self-hosted infrastructure
• Works on Raspberry Pi (ARM64 native)

Proposed compose.yaml

services:
  reverse-proxy:
    image: tvup/idle-less-reverse-proxy:latest
    ports:
      - "80:80"
      - "443:443"
    environment:
      - DOMAIN_1_NAME=app.example.com
      - DOMAIN_1_IP=192.168.1.100
      - DOMAIN_1_CONFIG=wakeforce
    restart: unless-stopped

  wakeforce:
    image: tvup/idle-less-wakeforce:latest
    environment:
      - BACKEND_MAC=AA:BB:CC:DD:EE:FF
      - BACKEND_IP=192.168.1.100
      - LICENSE_KEY=your-license-key
    networks:
      - lanbridge

networks:
  lanbridge:
    driver: macvlan
    driver_opts:
      parent: eth0
    ipam:
      config:
        - subnet: 192.168.1.0/24
          gateway: 192.168.1.1

Links

• GitHub: https://github.com/tvup/idle-less
• Docker Hub: tvup/idle-less-reverse-proxy, tvup/idle-less-wakeforce
• Demo: https://tvup.github.io/idle-less/demo.html

[vaguul]

Not a maintainer, but one thing I would tighten before a PR is the networking/security framing.

Because this relies on macvlan and Wake-on-LAN, the README should probably explain that it is a LAN-oriented sample and that users must change parent: eth0, subnet, gateway, backend IP, and backend MAC for their own network. That will avoid people copy-pasting a config that only works on one interface layout.

I would also avoid putting LICENSE_KEY=your-license-key directly in the sample compose file if possible. A .env.example or README note would keep the compose file closer to the public examples here and make it clearer that real secrets should not be committed.