a3a882a001
Replace every hardcoded atlascorporation.nl URL with YOUR_DOMAIN placeholder. Remove private client site names (replaced with example.com markers). Remove specific Tailscale tailnet address. Remove mosque name — now configurable. Add sed one-liner at top of README for instant domain swap. Deploy section is now the canonical getting-started path for anyone cloning.
1.4 KiB
Islamic Layer
A first-class part of Atlas OS — woven into the OS and the device fleet, not bolted on.
Components
| Layer | What it does |
|---|---|
| Family-safe DNS | AdGuard Family + a hosts blocklist across the network |
| Content filtering | HaramBlur on browsers |
| Quran at logon | Recitation plays when the workstation logs in |
| Adhan + lock | At configured mosque salah times, the Adhan plays and the screen locks |
| Sunnah reminders | Recurring reminders surfaced across the device fleet |
Salah timing
Prayer times are configured for your local mosque. At each salah time the fleet plays the Adhan and locks the active screen — a deliberate, enforced pause rather than a passive notification.
To configure your mosque: edit atlas-os/islamic/config.json with your mosque name and location (or GPS coordinates). The timing engine uses the MuslimSalat API.
Where it lives
All assets and scripts live under the Atlas artifacts tree:
Sync/atlas-artifacts/atlas-os/islamic/
This keeps the layer versioned and reproducible alongside the rest of the Atlas OS configuration, and syncs across devices through the same Syncthing topology as the other artifacts.
Principle
The Islamic layer is treated as core infrastructure: it ships with the OS, runs on the fleet by default, and is documented and version-controlled like every other service.