OrchardCore 2.0.2 and higher: how to migrate Orchard Core projects and database configurations to a new server

[MarGraz]

Hi,

We need to migrate several OC projects (2.0.2 and higher). Our solutions connect to PostgreSQL databases, and we've developed APIs, Content Types, etc.

Now, we need to migrate these solution to a new server with new PostgreSQL database. How can we migrate all the configurations stored in the databases to the new environment?

We would like to understand if it's possible to do this with and without the created Content Items (the data). Of course, we need to save all the Content Types, modules, and other configurations present in the database.

Thank you

[MarGraz]

@Piedone sorry for the direct mention, what do you think about this question? Maybe is better to proceed with a DB dump?

Thank you

[Piedone]

The simplest is to just backup the DB and restore it. I don't know how this works with Postgres, but I presume there are suitable tools for this.

Such a DB snapshot will include all content and configuration (unless you used the File Content Definition Store). If you don't want to migrate the content items, then a better approach is to build a Deployment Plan that exports everything but content items, and then import it (or use it as a setup recipe) on the other server.

[MarGraz]

@Piedone thank you for your answer.

If we have a dev environment and a production environment already in operation, I believe that performing a database backup and restore is not an option in this case, correct? In such a scenario, do we need to use the Deployment Plan, or is there another way to migrate the modifications made in dev to production?

One more things, I found these videos about the Deployment Plan in the documentation. Are they applicable for use with Orchard Core 2.x?

Thank you

[Piedone]

Unless you want to keep the dev environment as-is, and not overwrite it with a fresh prod DB, then yes, backup-restore is not an option and using recipes is a better idea.

Yes, the videos are largely applicable.