fix(frontend): move frontend to main repo

Author: kshitijrajsharma

api/app.py

@@ -4,19 +4,16 @@
 
 from litestar import Litestar, get
 from litestar.config.cors import CORSConfig
-from litestar.contrib.jinja import JinjaTemplateEngine
 from litestar.openapi.config import OpenAPIConfig
 from litestar.openapi.plugins import SwaggerRenderPlugin
-from litestar.response import Template
+from litestar.response import Redirect
 from litestar.static_files import create_static_files_router
-from litestar.template.config import TemplateConfig
 
 from .db import close_pool, ensure_schema, open_pool
 from .queries import fetch_state
 from .routers.hashtag import v2_router
 from .schemas import HealthResponse
 
-TEMPLATES = Path(__file__).parent / "templates"
 FRONTEND_DIST = os.getenv("FRONTEND_DIST")
 DEFAULT_CORS_ORIGINS = (
     "http://localhost:5173",
@@ -48,13 +45,14 @@ async def lifespan(app: Litestar):
 
 
 @get("/", include_in_schema=False)
-async def home() -> Template:
-    return Template("home.html")
+async def home() -> Redirect:
+    return Redirect(path="/docs")
 
 
 def _root_handlers() -> list:
-    """Serve the built frontend at / when FRONTEND_DIST is a directory, else the API home page. Explicit API
-    routes (/health, /api/*, /docs) take precedence over the static catch-all; html_mode serves index.html."""
+    """Serve the built frontend at / when FRONTEND_DIST is a directory, else redirect to the API docs.
+    Explicit API routes (/health, /api/*, /docs) take precedence over the static catch-all; html_mode
+    serves index.html."""
     if FRONTEND_DIST and Path(FRONTEND_DIST).is_dir():
         return [create_static_files_router(path="/", directories=[FRONTEND_DIST], html_mode=True)]
     return [home]
@@ -88,5 +86,4 @@ async def health() -> HealthResponse:
         path="/docs",
         render_plugins=[SwaggerRenderPlugin()],
     ),
-    template_config=TemplateConfig(directory=TEMPLATES, engine=JinjaTemplateEngine),  # ty: ignore[invalid-argument-type]
 )

api/templates/home.html

@@ -38,15 +38,20 @@ api.osmsg.<domain>  A   <server-ip>
 
 ## Configure and deploy
 
+The frontend ships in this repo under `frontend/`, and Caddy serves it from `../frontend` relative to
+the compose file. Clone the repo to `/opt/osmsg` so `infra/` and `frontend/` sit side by side.
+
 ```bash
+sudo git clone https://github.com/osgeonepal/osmsg.git /opt/osmsg
+cd /opt/osmsg
 cp infra/.env.example infra/.env && $EDITOR infra/.env   # set the two domains + ACME email
-sudo mkdir -p /opt/osmsg/infra
-sudo cp infra/docker-compose.yml infra/Caddyfile infra/osmsg.service infra/.env /opt/osmsg/infra/
-sudo git clone https://github.com/osgeonepal/osmsg-leaderboard.git /opt/osmsg-leaderboard
-sudo cp /opt/osmsg/infra/osmsg.service /etc/systemd/system/ && sudo systemctl daemon-reload
+sudo cp infra/osmsg.service /etc/systemd/system/ && sudo systemctl daemon-reload
 sudo systemctl enable --now osmsg
 ```
 
+Deploy updates with `git -C /opt/osmsg pull` (refreshes both the frontend and the compose files);
+`infra/.env` and any `infra/docker-compose.override.yml` are gitignored and stay untouched.
+
 `OSMSG_EXTRA_ARGS` runs every tick. Do not put `--last`, `--days`, `--update`, or `--url` there: the
 worker adds `--update` and auto-selects granularity from the gap (day to hour to minute). Pinning
 `--url minute` over a large gap crawls tens of thousands of files and fills the disk.

docs/infra.md

@@ -0,0 +1,36 @@
+# osmsg leaderboard frontend
+
+Static single-page leaderboard for the osmsg API. No build step: plain HTML, CSS, and JavaScript.
+Tailwind, lucide, and flatpickr load from a CDN at runtime.
+
+## Files
+
+- `index.html` , page markup and CDN includes.
+- `app.js` , query flow, state, rendering, CSV export.
+- `charts.js` , the trending-hashtags and editors lists.
+- `style.css` , all styling (light and dark).
+- `sw.js` , service worker (Workbox): network-first for the app shell and API, long-lived CDN cache.
+- `manifest.webmanifest` , PWA manifest.
+- `tailwind.config.js` , Tailwind CDN configuration.
+
+## API origin
+
+`app.js` reads the API base from `window.OSMSG_API_BASE`, falling back to `window.location.origin`.
+In production Caddy serves this site and reverse-proxies `/api/*`, `/health`, `/docs`, and `/schema`
+to the API on the same origin, so no per-deploy edit is needed.
+
+## Local preview
+
+Serve the directory with any static server and point it at a running API:
+
+```sh
+python -m http.server -d frontend 8080
+```
+
+Open <http://localhost:8080>. Set `window.OSMSG_API_BASE` in the console or a small inline script if
+the API runs on a different origin.
+
+## Deployment
+
+The production Caddy service bind-mounts this directory read-only at `/srv/leaderboard`
+(`infra/docker-compose.yml`). See `docs/infra.md` for the full deployment.