AI Writing Assistant now supports multiple providers: Workers AI and OpenAI. Cloudflare AI Gateway routes requests for reliability and flexibility.
Tag: infrastructure
15 jots
Umami self-hosted analytics is now in production. Privacy-focused analytics for all sites with custom /e endpoint for better ad-blocker bypass. Real metrics, no cookies.
Migrated the landing page (jottings.me) into the monorepo. Single codebase for dashboard and marketing site. Easier maintenance and consistent styling.
Migrated to a new Cognito User Pool with mutable email schema. This enables email changes and better OAuth integration. Seamless transition for existing users.
Migrated all AWS infrastructure from us-east-1 to us-east-2. Consolidating resources in a single region for better latency and cost management.
Added GitHub Actions workflow for Cloudflare Worker auto-deployment. Changes to the sites-router Worker are automatically deployed on push.
Added Cloudflare Worker for *.jottings.me subdomain routing to R2 storage. Each user's site is now accessible at their-subdomain.jottings.me with proper caching.
Implemented atomic counter updates using DynamoDB transactions. When a site is created, the user's totalSites counter is incremented atomically - no race conditions possible.
Complete dev/prod environment separation with GitHub Actions CI/CD. Push to develop deploys to dev, push to main deploys to production. Automated and reliable.
After a brief pause, back to development. Prepared the dev environment for deployment with compatibility fixes and environment variable management.
Complete DynamoDB integration with AWS Lambda API. Sites, jots, users, and builds are now stored in DynamoDB tables with proper indexes for efficient queries.
Complete frontend migration from Supabase to AWS stack. This is a major architectural shift - moving authentication, database, and APIs to a fully AWS-managed solution.
Added build processor Lambda with 10GB ephemeral storage. This enables generating static sites with all assets, images, and search indexes within Lambda's constraints.
Major architecture decision: migrating from Supabase to AWS. Implemented AWS Lambda infrastructure with Serverless Framework for better scalability and control.
Complete project setup with Supabase for database, SvelteKit for the frontend, and Cloudflare Workers for edge computing. The initial tech stack is in place.