Default Crash Move Folder
(CMF)

Summary

This repo contains the working copy of MapAction's default crash move folder.

WARNING: Selecting "Download.zip" from the Github website will always fail for this repo

Deployments

If you need a fresh copy for a new deployment/response/project please take a fresh copy from the R:\ drive.

See the Crash Move Folder wiki article for more details.

Scripts

To simplify the running of python scripts on different machines with different python configurations etc you can use the .bashrc file to specify your python setup & which script to run.

Prerequisites

• Git Bash (Windows machines only - Linux based machines should have bash pre-installed)
• NodeJs (Optional - for development purposes only)

Getting started

1. Copy the contents of the .bashrc into your local .bashrc file (create one if necessary).

   .bashrc location

   • Windows: C:\Users\USERNAME

   • Linux Based OS: /Users/USERNAME

     
     

   INFO: Remember to update:

   • mapaction_code_directory
   • propy
   • proenv

   values to align with your own machine setup. i.e. change mapaction_code_directory to wherever you store your mapaction files on your local machine & propy & proenv to your ArcPro installation directory.

2. Within the Git Bash terminal run source ~/.bashrc

3. You now have access to all the functions inside the .bashrc file & can call them from inside the Git Bash terminal e.g.

   $ exportAprxTemplateData # Run the script
   $ exportAprxTemplateData development # Run the script every time you save the script (great for development)

Contributing

Anyone with a MapAction Github account can create a pull request with proposed changes to this repo.

Please see Default Crash Move folder wiki page for more details on contributing & automated checks.

Large File Storage

This repo uses Git's Large Files Storage (LFS) therefore you'll need to use a LFS enabled git client, such as Github for Desktop. If you are using a commandline git client you may need to explicitly do the extra step after you clone the repo:

git lfs pull

Notes:

• No harm can be done by making opening or updating a pull request, and only Matt Sims and Andy Smith have permissions to merge a PR on this repo. When we merge a pull request then the changes are automatically sync'd to the R: drive.
• Even without any changes you will see slightly different content between the two copies. This is because when the contents to copied from the Github repo to the R:\ drive, some of git's working files (eg the .git dir and .gitignore file etc) are removed as they are not relevant in an emergency.