Document SQLite-to-MySQL migration path in STUDIO.md and publishing to supported hostings - #3984
Merged
Merged
Conversation
Clarify that Studio can export a MySQL-compatible database dump, so sites migrate cleanly to any MySQL host. Prevents the AI assistant from wrongly warning about compatibility issues when users ask about moving to production. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
epeicher
approved these changes
Jun 29, 2026
epeicher
left a comment
epeicher
left a comment
Contributor
There was a problem hiding this comment.
Thanks Antonio for improving this! I have tested a couple of prompts using Claude Code, and the results are much better than the same prompts using trunk. While in trunk they offer no clear path forward to migate the database, these are a couple of results with these changes applied:
| Migrate my site, please | How can I migrate my site |
|---|---|
 |
 |
Changes LGTM!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related issues
How AI was used in this PR
PR created with Claude, and tested manually.
Proposed Changes
STUDIO.mdis the per-site instruction file Studio bundles into every local site and feeds to the built-in AI assistant. Two gaps in its guidance led to bad answers:Migrating to MySQL. The database section only listed SQLite limitations, with nothing about migrating out — so when a user asked how to move their site to a production host running MySQL, the assistant discouraged them with a wrong answer about compatibility issues. This adds a "Migrating to MySQL" subsection: Studio exports a MySQL-compatible database dump (
studio export my-site.sql --mode db) that imports cleanly into any MySQL/MariaDB host with no migration plugin needed. The existing limitations are reframed as applying only to running on SQLite locally, not to the exported dump.Publishing to WordPress.com / Pressable. Push/pull were only present in the MCP tool table, with no CLI guidance. This adds a "Publishing to WordPress.com or Pressable" section (
studio push/studio pull, sync options, overwrite and eligibility caveats), aligned with the rules the Studio Code agent already follows.The result: the next time a user asks about migrating to MySQL or publishing to production, the assistant gives a correct, encouraging answer.
Testing Instructions
skills/STUDIO.md.npm startPre-merge Checklist