<commit_before>.. toctree::
	:titlesonly:
	
=========================================== 
Deployment 
=========================================== 


Client
------

This document provides the basic and detailed setup instructions for new 
Windows environments, specifically for Appleseed development under source control for client projects,
generally deployed on a physical Server or on the Cloud.

Directory Structure
------------------

Below is an overview of the directory structure for deploying a single Anant Application.
Please note for some old clients this is list as C:\Services or C:\Accounts or C:\Sites

- C:\Accounts - Create an accounts directory on the root of the primary drive.  It would be nice if you can store this on a drive other than C:\ as only the OS should reside there. 
- C:\Accounts\ClientName - Create a unique client name for an individual site.
- C:\Accounts\ClientName\prod - The production directory for the site that will be seen in the public  This should be on the client’s environment or AWS.
- C:\Accounts\ClientName\stage - The staging or verification site directory.  This site may or may not be public.  This site is used by the client to review the latest stable development fixes.  This should be on the client’s environment or AWS.
- C:\Accounts\ClientName\[environment]\www - Store the actual site/application/appleseed install in this directory.
- C:\Accounts\ClientName\[environment]\backup - Store site & SQL Data backups in this directory .
- C:\Accounts\ClientName\SiteName - Create a unique site directory for each site and follow the above directory recommendations.


Database 
--------

Appleseed Portal Database Naming 
[client_as_environment]

Production
- clientname_as_prod

Stage



.. include:: /././common.txt<commit_msg>bullet<commit_after>.. toctree::
	:titlesonly:
	
=========================================== 
Deployment 
=========================================== 


Client
------

This document provides the basic and detailed setup instructions for new 
Windows environments, specifically for Appleseed development under source control for client projects,
generally deployed on a physical Server or on the Cloud.

Directory Structure
------------------

Below is an overview of the directory structure for deploying a single Anant Application.
Please note for some old clients this is list as C:\Services or C:\Accounts or C:\Sites

- C:\Accounts - Create an accounts directory on the root of the primary drive.  It would be nice if you can store this on a drive other than C:\ as only the OS should reside there. 
- C:\Accounts\ClientName - Create a unique client name for an individual site.
- C:\Accounts\ClientName\prod - The production directory for the site that will be seen in the public  This should be on the client’s environment or AWS.
- C:\Accounts\ClientName\stage - The staging or verification site directory.  This site may or may not be public.  This site is used by the client to review the latest stable development fixes.  This should be on the client’s environment or AWS.
- C:\Accounts\ClientName\[environment]\www - Store the actual site/application/appleseed install in this directory.
- C:\Accounts\ClientName\[environment]\backup - Store site & SQL Data backups in this directory .
- C:\Accounts\ClientName\SiteName - Create a unique site directory for each site and follow the above directory recommendations.


Database 
--------

Appleseed Portal Database Naming 
[client_as_environment]

Production
- clientname_as_prod

Stage
- 


.. include:: /././common.txt
{'fraction_non_alphanumeric': 0.11984282907662082, 'fraction_numerical': 0.0, 'mean_word_length': 3.8622100954979537, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '97211', 'n_tokens_mistral': 881, 'n_tokens_neox': 844, 'n_words': 435}