Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Can we get rid of Ansible after moving the digital collections to Heroku? What’s standing in our way?

Things we have to keep

  • S3 bucket management (see issue #1023). We may want to use Terraform for this instead.

    • Notably, we need to keep create_kithe_s3.yml.

  • Building ArchivesSpace (details).

Things we can eliminate

Playbooks

  • create_kithe.yml

  • restore_kithe.yml

  • sync_kithe.yml

  • update_kithe.yml

  • We can also remove those parts of create_manage.yml that deal exclusively with updating the digital collections servers.

Roles

These roles are only used by the playbooks (or parts of playbooks) mentioned above, so they can be eliminated once we move to Heroku.

  • capistrano_setup

  • ffmpeg

  • kithe

  • passenger

  • redis

  • resque

  • management_scripts

  • No labels