We’ve made some significant changes to the folio-ansible project on GitHub to move us towards automated builds of FOLIO systems for demonstration and for testing. In particular:
Instead of a “backend” and a “demo” system build, we have defined a target for a “testing” system (containing the latest commits for every component) and a target for “stable” system (containing tested and released components known to work together). Both systems contain both front- and back-end components – Okapi, back-end modules, and Stripes.
Going forward, we will no longer release the “folio/folio-backend-auth” and “folio/folio-demo” Vagrant boxes on Atlas. Instead, we will be making regular releases of two new Vagrant boxes, “folio/stable” and “folio/testing”, built from the Ansible playbook in the folio-ansible project.
The goal for the near future is to automate the build and release of these Vagrant boxes nightly (in the case of folio/testing) or on demand (for folio/stable), so that you can always get a demonstration system with the most recent code – even if, in the case of folio/testing, it’s not guaranteed to work flawlessly.
Check out our Vagrant boxes on Atlas at https://atlas.hashicorp.com/folio – to try them out, make a new directory,
cd into it, and then try:
$ vagrant init folio/stable --minimal $ vagrant up
For more information about how these boxes are built, see the folio-ansible project on GitHub.
For more information about Vagrant, see the Vagrant home page.