✳ kaalkosha
Deployment guide · Cloudflare Pages

Your homepage is live.
Connect the archive engine.

Cloudflare Pages can serve the dashboard, but it cannot execute KaalKosha's Python Instagram worker. You must deploy that backend on a separate always-on HTTPS container server. Do not upload its Python source as your Pages frontend.

1. Deploy the Python backend

Use the original KaalKosha Cloud v7 project on a Linux Docker host with persistent database/session storage and a private Cloudflare R2 bucket. Set the required secrets on the host, NOT in the public Pages upload.

2. Connect it to Cloudflare Pages

  1. Open your Cloudflare dashboard → Workers & Pages → select this site.
  2. Open Settings → Variables and Secrets (or Environment variables).
  3. Add a variable named BACKEND_ORIGIN with the HTTPS origin of the running Python backend, such as https://archive.example.com, without a trailing path.
  4. Save and redeploy this Pages site so the Worker receives the environment variable.
  5. Open the main site; the server status will change once /api/health succeeds. Sign in to your private gallery.

3. Verify real archiving

  1. Sign in, connect your own Instagram session via the documented secure method and add one profile you can access.
  2. Run a first sync and verify actual files arrive in your R2 bucket and gallery.
  3. Test DP versions, a profile/year ZIP download, recovery alerts, and backups before relying on the automated process.

Nothing is auto-downloaded while the backend is disconnected. Public HTML alone cannot perform cloud media archiving.

← Open dashboard