Proposal: Add idle-less (reverse proxy with Wake-on-LAN) example
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- docker, docker-compose, nginx
- Domain
- devops, infrastructure
Research direction
Start by reviewing the proposed compose.yaml and the linked idle-less project and image documentation to verify the services, networking, and required configuration. The work is done when the idle-less Docker Compose example is added with its reverse proxy, Wake-on-LAN gateway, macvlan network, and usage details.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- HTML
- Stars
- 46.4k
- Forks
- 8.3k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/awesome-compose
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
docker/awesome-compose#825 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
docker/awesome-compose#767 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
docker/awesome-compose#758 · 1 comment ·
-
Proposal: Add P2PCLAW Research Lab — Decentralized Scientific Network (14 Agents, Docker Compose) Open
Difficulty 1/5 Under an hour Newbie friendliness 72/100
docker/awesome-compose#735 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
docker/awesome-compose#329 · 1 reaction ·
All issues in docker/awesome-compose
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
repo:raw-data
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
hotosm/raw-data-api#316 · 1 comment ·
-
agentic-workflows cascade-suspected
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
willow
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openedx/openedx-authz#460 ·