If you’re also new to Vagrant a good way to start is to install either AtoM or Archivematica by themselves using the Vagrant instructions provided here and here. It assumes you are already familiar with Archivematica/AtoM generally and are comfortable using the command line (if you’re not familiar with these things, check out Ashley Blewer’s fantastic intro to the command line deck and the overviews of Archivematica and AtoM). These instructions are current as of the time of writing. If you are thinking of setting up and connecting both applications at your workplace, doing so here should give you a good sense of how to connect the two in production, though of course with the difference of your own appropriate production deployment settings since Vagrant isn’t suitable for production use. The setup instructions that follow are specific to this: they will take you through the process of getting both VMs running at once, and then on how to integrate the two for the Archivematica to AtoM workflow. One thing I’ve been trying to do for a while is get the Archivematica and AtoM Vagrant boxes to integrate around the DIP deposit feature so I can better understand the workflow between the two. ![]() I’ve tried using Docker for Mac with Archivematica but it’s never really worked well for me, probably because it’s in development, I don’t really know Docker, and/or memory/space limitations. Though we also have development instances of Archivematica for this purpose at my workplace, one understandable but roadblock-y thing is that librarians/archivists like myself don’t get admin access (probably for good reason), so when I need to verify something that requires root permissions it’s really useful to have the local option. It’s quick and easy to get an instance of each up and running that is great for testing in a super low-risk situation. I really like the Vagrant option that Artefactual makes available for testing Archivematica and AtoM. If an update doesn’t resolve the problem or something has corrupted your current installation, you can repair the plugin.Hark! An Archivematica-generated DIP in AtoM! vagrant plugin update vagrant-vbguest Repairing a Broken Install To update your plugins after a Vagrant upgrade, you can execute the following command. While great for security and addressing bugs, doing so sometimes break your installed plugins. ![]() Vagrant Guest Additions Plugin Output Plugin Fail after Vagrant Upgradeīeing good administrators of our system we all keep our software up-to-date (right?). You’ll see the following output when it does happen. ![]() If, on the other hand, an update or installation is required, Vagrant will now download all dependent packages and then install Guest Additions from the Virtualbox ISO. If the latest version is installed, you will see the following output. Whenever you launch a Vagrant box you will now notice that the Guest Additions installation is checked. Installing the Guest Addition Plugin for Vagrant It also just happens to be one of the most popular plugins available. Thankfully, there is a plugin that can manage installing and updating the tools automatically. CentOS is guilty of this, and that means you will have to spend time installing the tools every time you launch a new box. Keeping the tools update is problematic enough until you realize not all boxes available from the official repository even have Guest Additions installed, to begin with. ![]() However, ensuring your Vagrant boxes are always running the latest version of Guest Additions can be a time-consuming task, stealing away crucial cycles that could be put to better use. Guest Addition is essentially for being able to unleash Vagrant’s full potential, meaning it is important that it is installed and kept updated.
0 Comments
Leave a Reply. |