SquiggleConf

Website for SquiggleConf: a conference for excellent web dev tooling

Usage

pnpm i
pnpm dev

Environment Variables

To get the newsletter API running, copy .env.template to an .env file and fill in the Brevo API key value from our password manager. This is not necessary unless you want to work on the newsletter API.

Cloudflare Deployment

This project deploys to Cloudflare Workers and does not use GitHub Actions. Day-to-day development stays the same: pnpm dev.

One-Time Setup

1. Connect this GitHub repository to a Cloudflare Worker in the Cloudflare dashboard.
2. Use the main branch as production.
3. Let Cloudflare create the preview deployment flow for other branches.
4. Set BREVO_API_KEY as a secret in the Cloudflare dashboard.

Immediate Manual Deploy

If you need to cut over production immediately, deploy directly from this repo:

pnpm build
npx wrangler deploy -c dist/server/wrangler.json

The build writes a complete worker config to dist/server/wrangler.json from the settings in wrangler.toml.

CI Behavior

• Pushes to main deploy the production worker.
• Pushes to other branches create preview deployments in Cloudflare.

Why No Local Deploy Command

The old Vercel flow centered on pushing to the repo and letting the platform handle deployment. This setup keeps the same feel: you develop locally with Astro, then push to GitHub and let Cloudflare handle deployment.

Contributors

Alexander Lichter 💻	Ceci 🚧	Corina Murg 🐛	Dimitri Mitropoulos 💻	Josh Goldberg ✨ 💻 🖋 📖 🤔 🚇 🚧 📆 🔧 🐛	Kevin 💻	Nicolò Ribaudo 💻
Ryan Waskiewicz 💻	Varun Shukla 💻	Yona Alexander Voss-Andreae 💻	Yufa 💻

💙 This package was templated with create-typescript-app.