Local development environment and workflow

I’m curious what people are doing for local development and workflow, specifically for a team that manages an Omeka site with multiple custom themes and modules. We’re still on Omeka Classic at the moment, and will be looking to upgrade soon. We’ve tried a couple different tools over the years. At the moment we use lando for our environment, phing for deployment, and composer for managing our custom modules and themes (composer grabs our contributed and custom themes and modules from github). This setup has felt a little fragile and finicky at times. I’m curious what others have had luck with. Are you using any deployment tools? Are you using Docker (if so, are you mounting the modules folder so you can work on the files?)? Are you pulling down your database from your production environment somehow? If you work on a team maintaining a module or theme, what’s the development workflow? Does everyone just manually clone the repo to their own Omeka S environment? Anything you can share would be helpful. Thanks!

1 Like