- delete internal infra docs: system-of-record.md, sitemap.html status board
(exposed live attack surface: subdomains, up/down status, client names)
- parameterize OS desktop: derive DOMAIN from location.hostname, u() helper
builds service URLs so a friend deploying at their domain just works
- scrub all live service links to service.{DOMAIN} placeholders
- remove client domains (bicos, hkintercare, etc.) everywhere
- collapse brand/client site tiles to one generic Website tile
- single public CTA -> atlascorporation.nl (Get a workspace)
- relative SSO sign-out; sanitized server scripts to example.com
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1.7 KiB
Atlas Academy
The education arm of Atlas Corporation, running on the same box: atlasacademy.nl. Coaching, courses, and a curriculum spanning ESF-funded tracks, BiSL, startup, and AI.
Hosting
Served as static HTML + a PHP product feed via nginx (TransIP subsite), fronted by the same brand and analytics as the rest of the stack.
Key pages: index, coaching, cursussen, pricing, leerpad, shop, esf, bisl, plus per-course pages (cursussen/bisl, cursussen/startup, cursussen/ai).
Lead capture → Odoo CRM
Academy leads flow straight into the operator's Odoo CRM as crm.lead records — no manual re-entry.
Academy page (form)
│ POST { name, email, interest, source }
▼
atlas-academy-relay (systemd on atlas-01, port 7793)
│
├─► Odoo → creates crm.lead, returns { ok: true, lead_id: N }
└─► email fallback → info@atlascorporation.nl
The relay is exposed via Caddy at /academy-lead (proxied to 127.0.0.1:<relay-port>). It caches the Odoo UID so it doesn't re-authenticate on every lead.
Product feed
Courses and hardware bundles are pulled from WooCommerce via a JSON feed, so the Academy shop stays in sync with the live store without duplicating product data.
GET https://www.<your-store>/academy-feed.php
→ { ts, count, products[] } # each: { id, title, price, type, img, url, cats }
Product types: laptop, desktop, monitor, accessory, bundle, pos.
Principle
Academy content follows the same hard rule as the rest of Atlas OS: no fabricated data. No invented student counts, testimonials, ratings, or review quotes — sections are left as placeholders or omitted until real data exists.