We are running a local installation of Omeka classic on a RHEL 7 LAMP stack. Like we do with most open source projects, we have chosen to create a development server for Omeka, where all plugins and themes exist for content creators, but that is never exposed to the public. When the site/content has been played with, tested, and finally created, we then move the site to a production server but only with the plugins and themes that the site needs. So in the end, the production server has only what is needed for the sites it’s serving, not the whole package of Omeka’s themes and plugins.
We are wondering if the readership of this forum believes our strategy is overkill or commonplace with Omeka installations - or somewhere in between. We are not interested in creating a lot of administrative/security overhead when it’s not needed. But I’d be interested in knowing if anyone else has taken this approach, how it’s worked, and honestly, if you think we’re just way off base and taking an overkill approach. Thanks in advance for any feedback.