Hosting guides

You only need this if you chose “a hosted website”. Your AI will walk you through it too, but here is the map.

A trip planner shows when you are away from home. A hosted trip site must sit behind a real login, or contain nothing personal at all.

Recommended: Cloudflare Pages + Zero Trust Access

Free for small groups. Each person logs in with a one-time code sent to their email address, and nobody else can see the site.

  1. Create a free Cloudflare account.
  2. Workers & Pages → Create → Pages. Either connect your private git repository, or use Direct Upload and drag in the folder your AI gave you.
  3. Open Zero Trust and choose a team name. The free plan covers up to 50 users.
  4. Access → Applications → Add an application → Self-hosted. Enter your <project>.pages.dev domain.
  5. Add a policy: Allow, include Emails, and type the addresses of everyone travelling. Type them in the Cloudflare dashboard, not in your AI chat.
  6. Login method: One-time PIN. Session duration: 1 month, so you are not logging in every day on holiday.
  7. Add a second application for *.<project>.pages.dev, so preview deployments are locked too.
  8. Open the site in a private window. You should see the Cloudflare login, not your trip.

Cloudflare changes its dashboard from time to time. If a menu has moved, follow the latest Cloudflare Access documentation and the Cloudflare Pages documentation.

Why not GitHub Pages, Netlify or Vercel?

If you still use them, TripForge turns on public-safe mode: no names, no accommodation names, nothing that shows when your home is empty.

Your own server

Put the whole site behind server-side login over HTTPS: HTTP basic auth, or an auth proxy such as oauth2-proxy or Authelia. A JavaScript password on a static page is not security: the content is already in the browser.

Keeping a single file safe