What’s the best way to transfer a Directus instance from one environment to another?

[MrCasquette]

For example, from local to production, or just for making simple copies.

I remember there used to be a snapshot command, or maybe even a more recent extension that made data transfers easier, including both schema and data.

This one

It seems like this info has disappeared from the docs — or at least I can’t find it anymore. I think this kind of guidance would be helpful for more than just me

Here’s the error I got with the extension

Thanks, bunnies!

[bryantgillespie]

This is definitely a tough question to answer because there are different pieces you might want to migrate from one environment to another.

You could be looking to migrate:

• Just your data model/schema
• Configuration settings
• Content and assets
• The entire instance

Migration Options

Here are a few approaches depending on what you need:

Schema & Configuration Only

• Check out our Promoting Changes Between Environments guide

Full Instance Migration

• Use the Migration extension from Directus Labs - great starting point
• Several community extensions available that handle more comprehensive migrations
  • GitHub - tractr/directus-sync: A CLI tool for synchronizing the schema and configuration of Directus across various environments.
  • GitHub - bcc-code/directus-schema-sync: The better way to sync your Directus schema and data between environments
• Database dump/restore for complete data transfer

The migration extension is probably your best bet to get started, then you can layer on additional tools based on your specific needs.

[MrCasquette]

I recently discover this new tools for those who are looking for a bootstrap tool.

GitHub - directus-labs/directus-template-cli: Apply "templates" to a new, empty Directus...

It’s look really cool. Can’t wait to make my own.

Hope I’ll can use it with a docker compose file