feat: remove Astro Studio references

[casungo]

This PR removes any Astro Studio reference since the platform is being sunset.
It needs to be evalued if a notice + mini-guide for migration should be included till the very end of the platform (in like 1 year).

Closes #9635

[netlify]

✅ Deploy Preview for astro-docs-2 ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	8935338
🔍 Latest deploy log	https://app.netlify.com/sites/astro-docs-2/deploys/670c4a0434ce0d00087f8000
😎 Deploy Preview	https://deploy-preview-9509--astro-docs-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[astrobot-houston]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale	File	Note
en	guides/astro-db.mdx	Source changed, localizations will be marked as outdated.
en	guides/integrations-guide/db.mdx	Source changed, localizations will be marked as outdated.
en	reference/cli-reference.mdx	Source changed, localizations will be marked as outdated.
it	guides/astro-db.mdx	Localization changed, will be marked as complete.
ja	guides/integrations-guide/db.mdx	Localization changed, will be marked as complete.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[Fryuni]

Awesome start! Left some ideas on how the pages could be changed. Nothing set in stone tho

[sarah11918]

Thank you @casungo for kicking this off, and thanks for jumping in early @Fryuni !

I love where this is going, how you've already realized that the existing structure was a result of the various parts that were added at different times, and want to emphasize that we have TOTAL CONTROL over where this page goes now.

One bit of context from the original page: we really did need to keep "Astro DB" stuff separate from "Studio" stuff, which meant explaining as much of the Astro DB stuff first, and then thinking about "connecting to your database" as something separate and difference. But maybe looking at the process as a whole, that's not the way people think of "using a database" in their project, and we don't have to be beholden to any of the original structure!

In light of that flexibility, some things I knew I would consider:

• Is it more likely that people will be starting/creating new databases from scratch, or might you have existing data that you want to connect with? There may be a world where you start by hooking up a database you already have vs. waiting halfway down this page. e.g. If you have a database, maybe it feels weird to talk about creating mock data to seed so you have access to the "shape" of data for working in dev and testing without acknowledging the data you have, or whether you can seed a copy of production data for working with?

• We received feedback on this initial page that people were working through all the sections like "steps" (rather than treating them as explanations of each step in the process) and would complain about errors when trying to use all the code samples together, as if they should have worked with each other. (Which was never the intention. We did not create a walk-through of an entire process.) As a result, when we wrote the Actions page, we did start with a very basic "Write your first action!" that didn't take too long, and did give people something self-contained to walk through before describing the parts of the process. I had wondered whether using this Actions page as a model in that respect might work well here. Just the smallest overview of something working, and then the examples we'd use in sections throughout the page (like creating references) could assume/refer back to that initial example.

[casungo]

First off thank you for the comment, gave me a new perspective on how to approach this

• Is it more likely that people will be starting/creating new databases from scratch, or might you have existing data that you want to connect with? There may be a world where you start by hooking up a database you already have vs. waiting halfway down this page. e.g. If you have a database, maybe it feels weird to talk about creating mock data to seed so you have access to the "shape" of data for working in dev and testing without acknowledging the data you have, or whether you can seed a copy of production data for working with?

• We received feedback on this initial page that people were working through all the sections like "steps" (rather than treating them as explanations of each step in the process) and would complain about errors when trying to use all the code samples together, as if they should have worked with each other. (Which was never the intention. We did not create a walk-through of an entire process.) As a result, when we wrote the Actions page, we did start with a very basic "Write your first action!" that didn't take too long, and did give people something self-contained to walk through before describing the parts of the process. I had wondered whether using this Actions page as a model in that respect might work well here. Just the smallest overview of something working, and then the examples we'd use in sections throughout the page (like creating references) could assume/refer back to that initial example.

I think that we should "guide" the user, at least trough the initial setup to have them in the mindset that once you set 2 env variables you are good and the rest of the things to do are either to seeds your database from zero or to copy how your database is already structured. The actions doc is a great writeup and I think by borrowing a few aspect of it the db page will feel like a page for a completly new feature (not that db is old, or maybe it is old by astro standards where if you blink you miss 3 major releases of everything)

Based on this, I think that the page should have a structure like this:

Overview
Installation
Basics
 Get started with a fresh database
 Use an already existing database
libSQL connection configuration options
Defining your database
 [keep it as it is]
Seeding your database
 [keep it as it is]
Querying your database
 [keep it as it is]
Basic commands
 Pushing data
 Pushing table schemas
 [etc...]
Building Astro DB integrations
 Type safe operations in integrations
Self-hosted production deployment

[sarah11918]

I love that idea for a structure! Would you be up for taking a shot at reorganizing it yourself?

[casungo]

Currently I'm on vacation till next Monday so I doubt I can draft something up these days, but after this week I'll tackle this for sure (or if someone precedes me i can review the changes) :)

[sarah11918]

Oh, no worries! Enjoy your vacation! Let's see what we've come up with by the time you're back!

[sarah11918]

Alright! I took a shot at this, trying to think of a reasonable process re: how you might think of this. Completely open to thoughts and suggestions!

Note, since we're going to merge this soon, to the main branch, we should keep the "Migrate from Studio" up for a while longer, just in case it's helpful to people who are still migrating. I would have to check on the exact date, but I think people will still have access for a while yet (maybe can't make new DBs etc, but at least to get their data)

[ArmandPhilippot]

Looks good to me as someone who's never used Astro Studio nor Astro DB! Just a tiny typo.

I still have an interrogation. From what I understand, in development mode, there is nothing to configure: Astro takes care of generating a database from two files (db/config.ts and db/seed.ts)... but generate where? Is a .db file generated in the db directory or in .astro/? Do I have access to it? Can I see how the data is generated?

My question may be stupid, as I said I am not used to Astro DB, but from where I stand I tell myself that it could be important information if someone needs to debug code related to their database. Maybe this scenario never happens... and I'm just curious to better understand how it works locally. 😄 So would it make sense to specify this information in the documentation?

[Fryuni]

@ArmandPhilippot

From what I understand, in development mode, there is nothing to configure: Astro takes care of generating a database from two files (db/config.ts and db/seed.ts)... but generate where? Is a .db file generated in the db directory or in .astro/?

That's correct. It is a normal SQLite DB file placed in your .astro folder.

Do I have access to it?

Since it is a normal SQLite DB file you can access it however you prefer. We can add that to the docs and maybe even link to the most common tools to inspect and work with it (or link to Turso's blog post about it: https://turso.tech/blog/5-best-free-sqlite-gui)

Can I see how the data is generated?

I'm not sure what do you expect from this. You can see the data, but what do you mean by "how the data is generated"?

[sarah11918]

This looks amazing everyone! 🥳

I went through and made some small edits myself. You can check the last commit to see exactly what I did, and make sure it all looks ok.

@casungo please let me know when you're happy with the end result, and it will be ready to merge! 💪

@Fryuni we'll want your final review, too, and to remove your block when it meets your approval! 🫡

[JusticeMatthew]

Left a small optional change comment but other than that LGTM

[casungo]

@sarah11918 your commit is perfect, really happy of how this PR turned out!

[Fryuni]

We did it!!!
This looks awesome.

I left a comment about one sentence that irks me.

[sarah11918]

Message to everyone:

I have removed [i18nIgnore] because even though we did correct links (to pass the checks) in two translation, there are more changes to those files that need to happen. So, we do want status to update as "needs updating" on those files, in addition to the other ones changed here.

[yanthomasdev]

We'll need a tracker directive here, blocking the PR so we don't forget that!

@lunaria-track:src/content/docs/en/guides/astro-db.mdx;src/content/docs/en/guides/integrations-guide/db.mdx;src/content/docs/en/reference/cli-reference.mdx

[sarah11918]

!coauthor

[github-actions]

Co-authored-by: Houston (Bot) <108291165+astrobot-houston@users.noreply.github.com>
Co-authored-by: Sarah Rainsberger <sarah@rainsberger.ca>
Co-authored-by: Luiz Ferraz <luiz@lferraz.com>
Co-authored-by: Armand Philippot <59021693+ArmandPhilippot@users.noreply.github.com>
Co-authored-by: Jonathan Dallas <1310725+jwdallas@users.noreply.github.com>
Co-authored-by: Yan <61414485+yanthomasdev@users.noreply.github.com>
Co-authored-by: Matthew Justice <72817096+JusticeMatthew@users.noreply.github.com>

We are using the tracking code!