Skip to main content

Self-hosting

logdrop is designed to be deployed by anyone who wants the same "reporters upload freely, only you can read it, it expires on its own" flow for their own project. It runs on Vercel, with no database.

What you need​

  • A Vercel account (the Hobby plan is enough to start).
  • A Resend account, to send magic-link emails, with a verified sender domain.
  • A Cloudflare account, for the Turnstile widget.
  • A (sub)domain you control, e.g. logdrop.your-domain.example.
  • A fork or clone of Marvellous-Codeworks/logdrop.

Deploy step by step​

1. Create the Vercel project​

Import the repository as a new Vercel project (or vercel link an existing one). Don't deploy yet: the app needs storage and environment variables first, or the first real upload will fail.

2. Create and connect a Vercel Blob store​

Project → Storage → Create Database → Blob.

  • Choose Public access. logdrop writes blobs with access: "public" and reads them with a plain fetch(); a Private store won't work. Blobs still aren't reachable in practice, because every blob name carries a random suffix that can't be derived from the slug.
  • Use Connect Project to attach it to this project (creating the store alone doesn't connect it: check the store's Connected Projects).
  • This provisions BLOB_READ_WRITE_TOKEN automatically.

3. Create and connect an Edge Config store​

Same Storage tab → Create Database → Edge Config (shown as Global Config in newer dashboards, same product). Create it and Connect Project. This provisions EDGE_CONFIG. It powers the optional upload kill-switch.

4. Create a Cloudflare Turnstile widget​

Cloudflare dashboard → Turnstile → Add widget:

  1. Domain: the subdomain you'll deploy to (add localhost too if you want to test locally).
  2. Widget mode: Managed.
  3. Copy the Site Key (→ VITE_TURNSTILE_SITE_KEY, public) and the Secret Key (→ TURNSTILE_SECRET_KEY, private).

5. Generate the app secrets​

TOKEN_SECRET, CRON_SECRET and, if you want the Agent API, AGENT_API_TOKEN are random strings you generate yourself, one per variable:

openssl rand -base64 32

6. Set the environment variables​

Project → Settings → Environment Variables, see the full list below.

7. Point your domain at the deployment​

Add a CNAME for your subdomain pointing to Vercel, and add the same domain under Settings → Domains. It must match SITE_URL exactly.

8. Deploy​

Trigger a deploy, or a redeploy if one already ran before steps 2-6 were done: environment variables and storage bindings only apply to deployments created after they're set. Then open the site and upload something to test it.

Upload fails right after deploying?

A generic "Upload failed" almost always means a missing environment variable or storage connection. Check the Vercel function logs first.

Environment variables​

VariableRequiredDescription
TOKEN_SECRETYesSigning secret for magic-link and session tokens (step 5). Changing it signs everyone out.
ADMIN_EMAILSYesComma-separated list of admin emails, case-insensitive. Removing an address revokes its access immediately.
RESEND_API_KEYYesResend API key for magic-link emails.
MAIL_FROMYesSender, e.g. logdrop <noreply@your-domain.example>, on a domain verified in Resend.
SITE_URLYesPublic base URL, no trailing slash, e.g. https://logdrop.your-domain.example. Used to build share links and magic links.
RETENTION_DAYSNoDays before an upload is deleted. Default 7.
MAX_UPLOAD_BYTESNoMax upload size in bytes. Default 4194304 (4 MB). Keep it below Vercel's ~4.5 MB request limit, larger bodies are rejected by the platform before logdrop sees them.
VITE_TURNSTILE_SITE_KEYYesTurnstile site key (public, shipped to the browser).
TURNSTILE_SECRET_KEYYesTurnstile secret key (server-side only).
CRON_SECRETYesSecret Vercel sends to the daily cleanup job.
AGENT_API_TOKENNoEnables the Agent API and the AI agent access enabled. line on the dashboard.
BLOB_READ_WRITE_TOKENAutoProvisioned by connecting the Blob store (step 2).
EDGE_CONFIGAutoProvisioned by connecting the Edge Config store (step 3).
Enable variables for each Vercel environment

Vercel scopes every variable to Production, Preview and/or Development. A variable enabled only for Production doesn't exist on Preview deployments: for example, AGENT_API_TOKEN set only for Production means Preview deployments don't show the agent line and answer the Agent API with 500. Tick every environment you need, then redeploy.

Upload kill-switch​

To stop new uploads without redeploying (e.g. during abuse), add a boolean key uploadsDisabled to the connected Edge Config store and set it to true. Uploaders then get "Uploads are temporarily disabled"; admins can still read, triage and delete existing uploads. Set it back to false (or delete the key) to reopen uploads.

If Edge Config can't be reached, uploads stay enabled: the switch is a safety valve, not a dependency.

Cleanup job​

vercel.json schedules /api/cron/cleanup every day at 03:00 UTC. It deletes every upload whose expiry time has passed, authenticated by CRON_SECRET. Between an upload's expiry and the next run, it may still appear in the admin dashboard, but the Agent API already treats it as gone.

Local development​

bun install
cp .env.example .env.local   # fill in the values above
bun run dev
bun test

Add localhost to the Turnstile widget's domains to test uploads locally.

Updating​

Pull the latest changes from upstream into your fork and let Vercel redeploy. Stored uploads don't need migrations: metadata fields added by newer versions are filled with defaults when older uploads are read. Check the release notes for new optional variables.