How a single index.php serves every business site, root directory, Cloud, and NearByMeNow page in the network by detecting the host and routing the request.
Doozer is a single-file multi-tenant application. There is one entry point, index.php, and the whole network runs through it. What renders is decided by the request's host, not by separate codebases or a CMS per site.
index.php reads $_SERVER['HTTP_HOST'] and classifies the request:doozer.work) — the platform landing page + admin console. Never abusiness page.
?e=... / ?ajax=...) — routed to includes/api-endpoints.php (the?e= read+write API) or the inline ?ajax= action switch.
elks.club, vsso.net, westmilford.biz,nearbymenow.com) — the root/Cloud directory listing many businesses.
oakridgeflorist.westmilford.biz) — a singlegenerated business site, rendered by includes/business-site.php.
livemusictonight.com) —see Clouds and Live Music Tonight.
domains row for the host resolves the businesses row (the real data).business-site.php composes the page: muse CSS/type, the AIai_generated_content, photos, sections, contact + lead form, the network footer.
Deployment is a file copy over FTP (no build step, no per-site config). A new wildcard domain becomes a live business generator the moment DNS points at the server. "Monolith with internal structure": the logic lives in includes/*.php helpers, not scattered apps. The tradeoff is discipline. A regression in index.php or business-site.php touches the whole fleet, so we verify by looking at live pixels and deploy with backup + rollback.
A Doozer site is generated from data + a Muse, not hand-built. The inputs (Google Places data, scraped enrichment, reviews) persist in the DB; the output is recomputed by today's pipeline. "Converting" or "upgrading" a site = re-running the current generation pipeline over the same inputs. The site never goes dark, and it gets better as the pipeline improves. This is the premise behind the flywheel and the whole data-enrichment direction.