Reasoning for NeuroVault AWS branch current configuration.

neurovault_aws.txt

The current version of docker in tha Amazon Linux repositiories is 1.7.1. This version has a limit of 10gb for images unless dm.basesize
is configured on docker startup. In the interest of getting the site back online as quick as possible a number of workarounds of this
limit can be seen in docker-compose.yml and fs_docker/Dockerfile.

The wget and untar in fs_docker/Dockerfile would cause the image to run out of space on being built. To remedy this I pre downloaded the
freesurfer code and had it added to the image directly. To further reduce the space impact of the freesurfer install the following
directories were removed from freesurfer/subjects:
bert  cvs_avg35  cvs_avg35_inMNI152  lh.EC_average  rh.EC_average  V1_average

There was an issue with transformations in pycortex taking up large amounts of space. A copy of the pycortex directory was made and moved
into the base NeuroVault directory and then mounted in the data container. This allowed pycortex to use space on the host directly. 

pycortex, freesurfer, and images are not curently tracked in the repository and should be recreated as necessary to re-deploy.

The database container is not currently being used in the deployment, database settings point at RDS. Leaving db in docker-compose.yml is
innocous.

It looks like the basesize defaults to 100gb in modern versions of docker so the freesurfer and pycortex changes could be reverted.