Hi Alex,
I want to mention upfront that AtoM is designed as production-ready software for archival institutions - meaning, it is intended to be
installed on a server, not a laptop or home computer. This is why the instructions assume a certain basic level of technical proficiency - they assume that the user has a server (or access to a server), and someone who understands how to install software on it, who can maintain the application if you need to upgrade or run into technical issues down the line. AtoM is also not easily installed on Windows servers - it was developed against a Linux distribution (Ubuntu) and generally we recommend that if you are going to install AtoM on a Windows server, the easiest solution is to install it as a
virtual machine - that is, install a Linux Ubuntu virtual appliance on your Windows server, and then install AtoM inside that.
However, if you are just looking for a test instance you can easily set up on a home computer (including Windows), you might want to try out our Vagrant box. The easiest instructions for installing it are found in these slides:
Please understand that this Vagrant box version of AtoM is NOT meant to be a permanent installation where you keep your data or with which run your public site - it is intended for local testing and development only!
You'll have to install
Vagrant and
Virtualbox on your computer first, and if you are a Windows user, you will also have to install
PuTTY. After that, the slides should walk you through the set up and update process.
You will also have to use the command-line a little bit to get set up. If that's totally new to you, you might find the following slides interesting - they will introduce you to command-line basics on Linux/Unix computers. Note that some commands are the same on Windows and some are different (there are a lot of resources out there for Windows console commands too), but these will help you for any part of the instructions inside PuTTY - and maintaining AtoM after you install. See:
There are also some parts in the later parts of the Vagrant slides where, to update the AtoM Vagrant box, you will need to run some of AtoM's command-line tasks. If you would like to learn more about what they do, why we run them, and how to execute them, you can look at these slides: