Hi all,
I am working on developing a framework for automating Omeka S site setup and management. I am following a similar path that I have already followed to do similar things with WordPress sites. For WordPress sites I use the provided command line tools to do things like perform the setup of the initial admin user, install/remove themes and plugins, update themes and plugins, and changing of the site URL when migrating.
I have not been able to find any mention of a CLI for omeka in the Omeka S User Manual . Am I missing something or does one not exist?
I have found one on github: GitHub - Libnamic/omeka-s-cli: Omeka S CLI tool developed by a third party, but hasn’t been updated in 2 years. Though not having found anything else, I have started to try it out and while it mostly seems to work it is fairly lacking. I am at the point now where I am considering doing some improvements myself on that repo to make it more automation friendly as some tasks require interactive confirmation which is not suitable for automation.
I would love to know if I am missing an official CLI that already exists.
1 Like
Hi,
There is no official tool for that, but some tools exists on github.
Nevertheless, i thing that the best tool for most common tasks is composer, and that’s why i think that composer should be used anywhere, and not gulp or any python tool.
There is an issue to use composer to manage, install, update, any modules and themes with in github/omeka/omeka-s#2272. With such a solution, the main point to check is the way to manage old modules and themes or to force upgrade.
For other tasks, a tool based on the symfony cli would be fine, but it can be a standalone.
The thing I am currently using is a PHP based CLI, but is very rough around the edges. I have started to do a little hacking on it to smooth the edges out just enough for my needs. However, I do have concerns about future maintenance/compatibility and would love there to be something more official.
I am not particularly familiar with composer, and understand it to be something that manages PHP packages. Would that allow one to have a CLI tool for managing Omeka sites? I suppose Omeka, modules, and themes are just php packages at some level, but would composer be “Omeka aware”? Or are you proposing a CLI tool that is built on top of composer to do the package management under the hood?
Interesting thoughts about a future tool and would love to know where it goes, I suppose for now I will keep doing what I am doing with the hope that something better comes along.