Hi there,
I’m a computer scientist and I plan to migrate a whole Omeka S site with the database, template, and so on. The first step is to discover Omeka S, and after that, I just want to know if there are best practices to do this migration smoothly.
For instance, I don’t know the SGBD of the initial site but I presume it’s MySQL, and, idealy, I plan to use MariaDB on the new server, but I don’t know if it’s possible.
Is there documentation about Omeka S site migration? I searched in this forum, but I can’t find complete information.
You should be able to use either MySQL or MariaDB, subject to using a supported version. But our requirements are pretty loose there so you’re probably fine.
Making and then restoring a dump is the best move for moving over the database, definitely.
As for the core and the modules/themes/etc., it’s up to you. You can grab everything and bring it over to another server and that will work, just so long as you have valid credentials for the new server in your config/database.ini. Or you can use new copies of the core and the addons if you’d like. Both methods work fine. Note that if you are planning to get fresh copies of the code, you’ll still need to bring over the “files” folder from your old install: that’s where your uploaded files and generated thumbnails are stored.
A further note, just because you mentioned that other thread: there’s no need to install Omeka S on the new server, in the sense of running the installer. Regardless of the method you choose, just having your site’s database, the Omeka S files, and the config/database.ini pointing to that database is enough.
@jflatnes Thanks for your reply.
I need to install Omeka S CMS because we leave a private Omeka S CMS platform and migrate to a public one, which will be managed by me.
Another question I have to prevent error is about the data itself. On the legacy database, all data are linked to an open repository (https://nakala.fr/). Is there any precaution with this kind of configuration?
Regards,
arnome