...
One important function of Ansible that we currently still need is the provisioning of the ArchivesSpace server.
Current function
For the purposes of this discussion, the ArchivesSpace server has three pieces of software on it:
A ) The ArchivesSpace software proper.
B ) The code and files that export ArchivesSpace EADs and HTML finding aids (in a GitHub repository).
At the moment, this code is badly in need of repair and updates.
C ) An Apache server that serves the EADs and the HTML finding aids .output by B )
Options
To entirely eliminate the ArchivesSpace server (and thus our dependency on the ArchivesSpace code in Ansible), we could can take one or more of the following steps:
A ) Move the ArchivesSpace software proper to a hosted provider.
As part of this, we may wish to (or have to) also update the version of ArchivesSpace we use.
We may also decide, as part of this work, to turn on the public user interface.
If we turn on the PUI, the HTML finding aids export code can and should be eliminated.
B ) Run the export scripts from a hosted environment. It may be possible to run them from a serverless environment, such as AWS lambda.
C ) Serve the EADs, and, if we still need them, the HTML finding aids, from an S3 bucket. This allows us to remove Apache from our setup altogether.
...