Workaround for Bolt.new login
but work around instructions would be great. loom video, audio message, text, whatever works for you.
Bthis is copied from my local computer, at ~/.convex/config.json
BThis is what login normally does, it gets a token and stores it here
Bthe command that's hard to read here should be
GAh ok. Perfect.
GThank you sir. Much appreciated
Gworked perfectly
G@ballingt so I I think im going to be ready to send this to prod. Obviously the bolt to netlify and also convex is a bit interesting.
do I need to deviate from the documentation I see on convex about building and deploying the production enviornment for convex.
do I need to deviate from the documentation I see on convex about building and deploying the production enviornment for convex.
Gbolt typically 2 stages the build. it does a prebuild locally, then ships to netlify for final compiling.
Bhm, and it never gets stored in GitHub yeah, just direct from bolt?
Gyep.
G80% of the bolt userbase is non technical and doesnt understand commit, push, pull, etc.
Bcool, I'll try this flow now
Gultimately bolt and stackblitz maintain extensive back ups
BCan you still enter build commands in Netlify?
Gso bolt lets you modify the netlify.toml so I think so
Bcool
Gthat would be the file, right?
BWhat's your intention, you want two separate deployments, right?
Gi mean ive never gotten a convex build this far.
Byour dev convex deployment that you can keep iterating on, and prod that won't change while you're changing your dev?
G3.7 made it possible.
Guhhh
BThe normal instructions are based around the idea that you have two separate databases
Gah ok
Gso, thats the "right" thing to do of course.
Bone that you iterate on while developing, and another that powers your production site
Gso technically a project COULD run on a production dev
Gsorry
Gflip that
Git could run on a dev deploy
Gvs the production deploy.
Gwhich is kinjda what bolt has people doing now, with the supabase integration
BGot it, ok so if we do push the dev vs prod flow we need to do some user education
Gyes
Bmaybe the thing to make easy is a single environment then
Gi am the 1%
Gthat understands the difference lol
Bin which case yes the instructions will look different, let me try the flow
Ggot it. I wonder if you need to give users an option to make integration easier.
you could call it LLM Builder mode.
You can let people choose to run the deploy/prod dual environment.
OR you can let them run a single environment that uses versioning.
This way convex still retains a "how are we different" edge in that, if you break your database, you can still roll it back to a working version and let them roll backups back like 15 days on the free plan, a year on the paid plan.
You can also make that a slightly reduced cost (not that your plans are unaffordable, im also on the creator/affiliate team for you guys) as an additional advantage.
you could call it LLM Builder mode.
You can let people choose to run the deploy/prod dual environment.
OR you can let them run a single environment that uses versioning.
This way convex still retains a "how are we different" edge in that, if you break your database, you can still roll it back to a working version and let them roll backups back like 15 days on the free plan, a year on the paid plan.
You can also make that a slightly reduced cost (not that your plans are unaffordable, im also on the creator/affiliate team for you guys) as an additional advantage.
Gbecause supabase is the current "pick me" but its heavy as shit with postgres and doing ANYTHING inside of its interface related to back ups or rolling back backups is a NIGHTMARE.
Gso I actually think this is a decent drilling point for you guys.
G(20 year marketing guy, im always looking at everything through that lens)
BOK @Gabe F. the instructions for deploying to Netlify are... just click the button!
Bcatching up on these messages, totally, this makes sense
BSo the way Bolt seems to build is that is that it does a static build (an SPA) and ships that to Netlify. Which is great, because it's during this buyild process that the CONVEX_URL gets backed into the app. So by default, you just get this dev URL baked in.
BFor now I'm just looking and making sure this is easy, but yeah going forward we need to have an upgrade flow or a differentiating flow or something
BBut the way bolt builds these is pretty simple, as you pointed out it just builds and then ships, which is great.
GAnd we keep convex in dev mode?
GOne thing that would be cool to see build in to convex is a terminal shortcut or possibly an overlay component that will run commands in the terminal. For example, when you reload in bolt, it can lose the auth connector because it's a virtualized enviornment.
So a small like, corner pop up that is directly connected to the terminal to run functions would be a MASSIVE plus for adopting on LLM builders.
So a small like, corner pop up that is directly connected to the terminal to run functions would be a MASSIVE plus for adopting on LLM builders.
BYeah with this style you'll be using the same database