Database Vendor | Migration | Server Location and GDPR Compliance
From the FieldSeason 1Episode 1October 21 2022In this episode, John and Pedro answer questions about Directus' own database choice and migration between projects.
Speaker 0: Hey everyone. Welcome to the first episode of From the Field Q and A with P and J. My name is Pedro.
Speaker 1: And I'm John. Let's dive into some questions that we've recently received. Pedro, how about you start off with the first one?
Speaker 0: So our first question, user Ryan Skye, aka Tony on GitHub, asked which DB vendor is used by Directus Cloud itself?
Speaker 1: Great question, Tony. And Ben actually answered this in the thread itself. Ben is our CEO. In the cloud, we use Postgres, unless you're talking about community cloud, which is currently SQLite that may change in the future, in regards to community cloud, but in enterprise and standard, we do use Postgres. Alright.
Great question, Tony. Let's look on to the next one.
Speaker 0: Okay. So onto the next question. Is there a way I can migrate everything from 1 Directus cloud instance into another Directus cloud instance?
Speaker 1: Yeah. There's actually a schema sync utility. We also give you that capability in command line interface, CLI. Those are both enabled on enterprise cloud, so that is something that you can do as well. Also, if you're migrating from one project to another, whether it be community to standard, standard to enterprise, we will also do that migration for you.
Speaker 0: Mhmm. And you can provide for or you can you can find information on the schema sync utility in our direct to stocks online.
Speaker 1: That's actually a great question that ties into our next question, Pedro. How do I migrate a dev environment to a production environment?
Speaker 0: Yeah. So same thing. We have the schema migration tool, which is a CLI integration, and we've got an API wrapper actually coming pretty soon here.
Speaker 1: That's a good point too. We also allow you to have dev environments, nonproduction environments, as well as production environments, and seamlessly move information, schemas in between the 2. That's kind of where that version locking comes into play, where Pedro mentioned last question.
Speaker 0: So for the final question, we have a lot of customers in Europe, who ask to be compliant with GDPR regulations and ask where our servers are actually hosted? Yeah. That's a
Speaker 1: great question. We do have several servers in GDPR compliant areas. For our standard cloud, we have an east US, location. We have Asia location, and we also have servers in Frankfurt, Germany. So for standard cloud, you're covered under GDPR in Frankfurt, Germany.
When you move up to enterprise cloud, we have a a bunch more locations. Some of those include London, Stockholm, Paris, and I believe there's even one in Ireland. All of those which are enabled for GDPR as well. So plenty of locations available for those who are GDPR aware.
Speaker 0: Yeah. And in addition to that, it's all based on Amazon AWS infrastructure, so highly performant and secure as well. Thanks so much for tuning in to from the field q and a with p and j. Make sure to smash that like button and subscribe for notifications on our future videos.
Speaker 1: And feel free to ask questions in the comments. We're definitely gonna take some of those questions for future episodes. We love answering community questions. And don't forget to join the communities on Discord and GitHub as well. That's where we also source questions from.
Thanks again. Everyone have a great day.