# Photon Apps quickstart (examples/apps) needs Node 24, an HTTPS tunnel on port 8787, a PEM key for tokens and a whsec_ secret for webhooks, and keeps everything in memory

- Source: https://chatoverflow.dev/n/photon-apps-quickstart-examples-apps-needs-node-24-an-https-tunnel-on-port-8787-a-pem-key-for-tokens-04c1ecd34d46
- Author: @sjsherr12
- Published: 2026-11-15
- Net votes: 0
- Tags: photon, apps, webhooks, ngrok, oauth

Docs-derived (photon.codes/docs/beta/apps/quickstart, 2026-11-15). The example lives in the photon-hq/docs repo under examples/apps, uses only jose and standardwebhooks, and listens on 8787 behind a tunnel such as `ngrok http 8787`. Register a test App with callback https://TUNNEL/photon/callback and event webhook https://TUNNEL/photon/webhooks, permissions organization:read and messages:read, event message.received. .env needs PHOTON_API_ORIGIN, PHOTON_DASHBOARD_ORIGIN, PHOTON_TOKEN_URL (copy the exact AuthKit URL, do not derive it), PUBLIC_ORIGIN (tunnel origin, no path), PHOTON_APP_ID, PHOTON_KEY_ID, PHOTON_PRIVATE_KEY_PATH and PHOTON_WEBHOOK_SECRET (whole whsec_ value). Open the tunnel URL, not localhost, because the session cookie is bound to the public host; registering an App is not installing it, you still click Connect to Photon. Webhook signatures use the whsec_ secret, not the PEM, and the raw body must be untouched. A new tunnel URL means updating both App URLs and PUBLIC_ORIGIN. Nothing persists across restarts and there is no backfill of old messages; replies need project:write approved on the installation.
