Can we explain or give an example of what someone needs to do to make sure these are set at the correct time? It's one thing to say they "have to be set during..", but it's helpful to show what they will need to do to make that happen. If simply setting the variables were enough, then this sentence wouldn't be necessary, right? So what else do they have to make sure they do?

ooops, this ended up as a plain comment, not review comment! I'm doing a review now, and the rest will come in one review batch!

Setting the environment variables is enough, but they have to do it in all places being used. So, for example, when deploying to Vercel you need the environment variable set locally when you run astro db push --remote to apply the schemas and on Vercel to connect to the DB.

Using Studio, the token only needs to be set on Vercel since the local run of astro db push --remote will use the user token.

So, would this be added to the command as a flag when run? Or just added in the appropriate places (one and done, like in a .env file or in a dashboard somewhere? I think this is what I'm getting at.

"Set when you run" could mean "pre-set, and available somewhere" or something you need to provide each time.

I made the examples show the .env file so people put it there. There is multiple ways to do it along with security considerations, but that will depend on how their project and their connection to LibSQL is structured. I don't think there is much point going into details on Astro Docs vs following the docs of the hosting they are using

My earlier comment holds here too. "using the connection URL" is not as helpful as spelling out specifically "as query parameters".

Can we have one actually, complete full example here showing the broader context to set people up for the following sections all being understood as additional query parameters? Pick the most common situation you can think of. There's been a lot of "you can set" below without seeing what that looks like.

We're moving away from calling it "Hrana", so not using it here would be a huge help 🫶

As a reader, this also makes it a lot easier to understand what it is in this context.

The name everywhere I see is LibSQL with capital L, is that changing too?

I looked again, and there seems to be a mix. I'll normalize our references to be libSQL but as a heads up @notrab , on Turso docs and the repos the links and titles are mostly using "LibSQL" while the content on the pages are using "libSQL".

Good spot! I’ll make sure our docs are updated to reflect our new messaging, and additional pages on our site/GitHub repos.