I build an amazing app in dev, and it works beautifully. Then… when I deploy to production, $#IT hits the fan, and I spend countless hours with the agent trying to troubleshoot why production isn’t working.
I’m looking for tips and tricks to get the deployment to match 100% what is in dev to prod. My logic says, “Deployment” is basically a code copy from one enviroment (spock, for example) to it’s own environment based on the parameters I setup.
But when I “deploy” everything breaks. API endpoints stop working, core functionality is broken, and I spend an enormous amount of time trying to coax the agent to actually fix the problem.
Has anyone found a way to deploy a stable version to production? Is it easier to just sync GIT to your own hosting environment?
Gut tells me you have a secrets issue. Go to publishing tab and click Advanced Settings. See if it appears like any secrets (likely ‘account secrets’) are being omitted during publishing.
As Eric says, it is probably Secrets in the deployed/published app.
Either some are missing, or you’ve got some of your Deployment Secrets still pointing at hardcoded development environment things (API URLs, database, etc). Run through each one and check if it looks like it might be pointing back at something in dev. And also that you aren’t missing any. Also, if it is pointing at the development database, that would be sure to screw things up too.
Let us have a few specifics on what actually happens when you run the published version.
@kevin1096 and @realfunnyeric, this is exactly why I’ve created the AI Dev Kit (ADK). Too many examples where vibe coders are getting things working beautifully in dev, but as soon as it is rolled out to real users, the code unravels and just doesn’t do what it’s supposed to do.
My ADK is very opinionated, not least in its use of Supabase for auth/DB/storage. So I know it isn’t for experienced devs like your good self
But I believe my ADK (and other base scaffold apps) is going to be increasingly sought after by those where they want to take this vibe coding lark further than just beautiful prototypes, and start producing things that actually work. Rather than spend $1,000 and then realise they’ve got a nightmare plate of spaghetti with 5 different auth systems, no handle on database RLS, APIs with no security, etc, etc, etc. A real mess that Agent refuses to understand, so instead it just starts patching the patches and making more of a mess. Oh, and no clean workflow for deploying to prod.
