I have a number of S sites that were originally installed via the zip file, and I’d like to switch to using github releases for updates. With the backups as usual, would it work to just empty the directory, do a git pull of the Omeka S source, and replace with the right config files and uploaded files?
And if so, I’m guess similar for modules and themes?
Thanks
Yes, you can switch between a zip-based installation to a Git checkout in basically the same way as you’d upgrade or move an install, you just need your install-specific things in place (config files, the “files” folder, modules, themes).
Note that you need to install external dependencies if you’re using a Git checkout: you can do this with composer install or using the scripting included with a checkout.
Modules can similarly be replaced by checkouts just the same as a regular module upgrade: delete the old module and replace with the new one. A small number of modules also have Composer dependencies, and need similar handling to the core’s dependencies.
I migrated a test installation from the release .zip file to git by myself and I can confirm that it works just fine.
Having all the modules and the core in git makes it so much easier to update, and I can manage the customizations I did to the theme in my own branch.
This topic was automatically closed 360 days after the last reply. New replies are no longer allowed.