u/babyflocologne

I’m building a project with a purely static frontend that hits a serverless SQL database via edge functions. It works great for scaling, but I’m hitting a wall when it comes to CI/CD workflows and database schema migrations.

Since the frontend deploys are atomic and instant, a breaking database change can easily tear down live sessions if a user is on an older version of the static UI that expects the old schema. Are you guys writing backward-compatible migrations for every single change or is there a tool that syncs database schema updates perfectly with the edge deployment lifecycle?

I’m trying to prep for AI agents that shop and plan for users, but I don't see how it fits a static-first setup. If the future is sites that adapt in real-time, is pre-rendered HTML dead? I want to keep the speed of a static host, but I’m not sure how to support agents that need to take actions. Is there a way to layer this on top, or are we stuck going back to heavy SSR?

My static site is creeping up on 10,000 pages, and my current search setup is starting to feel like a massive bottleneck. Right now, I’m building a huge JSON index that the browser has to download just to run a search, but the file size is getting so big that it’s killing my load times and eating up memory on mobile.

I'm trying to figure out if I should move to a paid search API or try something self-hosted like Meilisearch or Typesense. For anyone else managing a huge catalog or doc site, at what point did a local JSON file just stop working for you? I’m also curious how you're handling partial updates so the whole index doesn't have to be re-downloaded every time I change one page. Is there a way to do this with serverless functions that keeps things fast but doesn't cost a fortune every month?

I’m trying to find a way to stop my pipeline from rebuilding the whole site every time I touch a README or a test script. Right now, every tiny commit triggers a 5-minute build that minifies all my images and purges the CSS, which feels like a total waste of time.

I’ve tried using basic shell scripts with git diff to skip steps, but it feels like a hack and doesn't always work right across different branches. As my repo gets bigger, it's really killing my deployment speed. How are you guys handling this? Is there a better way to ignore non-visual changes without breaking the build?