# Learnitive public ingress

The normal Learnitive installer deliberately does **not** install, enable, disable, reload or restart Apache/Nginx. This protects the existing Interactive Shell production listener.

Learnitive listens privately on `127.0.0.1:4210` (application) and `127.0.0.1:4211` (collaboration). Route `https://www.learnitive.com` to those endpoints using an ingress boundary that is operationally independent of the web server serving Interactive Shell, for example:

- a separate VM/server;
- a dedicated public IP with an independent listener;
- an external reverse proxy/load balancer; or
- an independently managed tunnel service.

Do not add the Learnitive vhost to a shared Apache instance if doing so requires reloading or restarting the Interactive Shell production web server.


## Staging first, then production

The approved staging origin is `https://edu.learnitive.com`, backed by `/var/www/edu.learnitive.com/public_html` and the `staging` deployment profile. The supplied `edu.learnitive.com-http.conf` / `edu.learnitive.com-https.conf` templates mirror the production routes but add a mandatory `X-Robots-Tag: noindex, nofollow, noarchive` response policy. The application also disallows all crawlers when `LEARNITIVE_ENV=staging`.

After staging acceptance, install the production profile at `/var/www/learnitive.com/public_html` and route `https://www.learnitive.com` through the independent ingress. Only after www acceptance may `edu.learnitive.com` be retired or redirected to www. See `EDU_STAGING.md` and `WWW_CUTOVER.md`.