splited marketing site from operator app

[rcodyp]

This PR defines the deployment topology for Hyperpush by clearly separating the marketing site (landing) from the operator app (frontend-exp) in terms of routing and runtime responsibilities.

---

Routing

The system is split using hostname-based routing:

• hyperpush.dev → marketing site (landing)
• app.hyperpush.dev → operator app (frontend-exp)

Routing is expected to be handled via a reverse proxy (e.g., Nginx or Traefik) in a Docker-based deployment.

---

Start locally:

1. cd F:\HyperPush\hyperpush\mesher
2. docker compose up -d --build
3. docker compose ps

---

Deployment Topology (Docker-ready)

The system is designed to run as separate containers:

• landing → marketing container
• frontend-exp → operator app container

Example (illustrative):

services:
  landing:
    build: ./landing

  app:
    build: ./frontend-exp