As the number of modules jumps, we need to have a more lightweight testing-backend VM for developers. They should be able to enable the modules outside the core that they need using Ansible playbooks.
- Reconfigure the folio/testing-backend Vagrant box to run only modules required by the platform-core Stripes platform, plus additional core modules (e.g. mod-codex-ekb, mod-audit)
- Create documentation for developers on how to deploy the additional modules they require and load reference and sample data
- End the nightly build of the full-stack Vagrant boxes folio/testing and folio/snapshot. This will require some coordination with julianladisch, as folio/testing is the basis for folio-demo.gbv.de
- Reconfigure the AWS builds – is there a need for both folio-testing and folio-snapshot, or could folio-snapshot be reconfigured to be two systems with periodic stripes rebuild like folio-testing is today? Regardless, there should be some kind of snapshot reference system that represents the full set of candidate modules for the next release.
As part of this process, we should create a test Vagrant box and work with some front-end developers to refine the configuration and the procedures for adding/updating modules.