Documentation: Setting up Arches for production deployment

[mradamcox]

From @dwuthrich on June 2, 2017 22:6

User Story

We should identify the key steps in getting Arches ready for production use. These steps include:

1. Deciding on overall installation approach. Potential items to address may include:
   Unix/Windows OS issues, Application tiers (database/application/ES tiers). This might just require stating that Arches can be deployed in scalable/fault tolerant ways
2. Setting up a production web server with Arches
3. How to update default landing page images/text
4. User/group management tips (perhaps just a link to Django documentation)
5. Suggested backup strategy (e.g.: database, models/business data, concepts/collections, uploaded files)

For each item, directing users to on-line references for more information would be fine.

Copied from original issue: archesproject/arches#2109

[mradamcox]

I think we should close this ticket now, as items have either been addressed, or are now covered in newer tickets.

1. @dwuthrich could you add your thoughts on this to Add Content About Deciding on Overall Installation Approach #229?
2. This exists here: https://arches.readthedocs.io/en/dev-5.1/serving-arches-with-apache/ and 'Uploaded files' section in Read The Docs #125 and Possible mistakes in Arches documentation #119 will handle some necessary updates to that section.
3. @dwuthrich could you add your thoughts on this to How to update default landing page template #230?
4. Document Default Permissions/Group Privileges #98
5. Server issue because of space - add information on basic backup/restore strategy #132