Fix some Docker commands to use a variable instead of hard-coded 'custom' directory (#696)

* remove references to dataclass objects

* Fix a copy-paste error.

* remove extra file

* Fix a copy-paste error.

* Remove unused file

* Fixes the "custom" directory to be a variable

* Add variable formatting

* Minor fixes

Author: kmoscoe

custom_dc/advanced.md

@@ -131,8 +131,8 @@ To run a local instance of the services container, you need to set all of the en
 -e DEBUG=true \
 -e GOOGLE_APPLICATION_CREDENTIALS=/gcp/creds.json \
 -v $HOME/.config/gcloud/application_default_credentials.json:/gcp/creds.json:ro \
--v $PWD/server/templates/custom_dc/custom:/workspace/server/templates/custom_dc/custom \
--v $PWD/static/custom_dc/custom:/workspace/static/custom_dc/custom \
+-v $PWD/server/templates/custom_dc/<var>PROJECT_DIRECTORY</var>:/workspace/server/templates/custom_dc/<var>PROJECT_DIRECTORY</var> \
+-v $PWD/static/custom_dc/<var>PROJECT_DIRECTORY</var>:/workspace/static/custom_dc/<var>PROJECT_DIRECTORY</var> \
 <var>IMAGE_NAME</var>:<var>IMAGE_TAG</var></pre>
     <ul><li>The image name and image tag are the values you set when you <a href="build_image.md#build-package">created the package</a>.</li>
     <li>You don't specify any directories here, as you aren't mounting any local volumes.</li></ul><br/>

custom_dc/build_image.md

@@ -156,14 +156,15 @@ Run the following command to build the repo (and run it locally):
       -e DEBUG=true \
       -v <var>INPUT_DIRECTORY</var>:<var>INPUT_DIRECTORY</var> \
       -v <var>OUTPUT_DIRECTORY</var>:<var>OUTPUT_DIRECTORY</var> \
-      -v $PWD/server/templates/custom_dc/custom:/workspace/server/templates/custom_dc/custom \
-      -v $PWD/static/custom_dc/custom:/workspace/static/custom_dc/custom \
+      -v $PWD/server/templates/custom_dc/<var>PROJECT_DIRECTORY</var>:/workspace/server/templates/custom_dc/<var>PROJECT_DIRECTORY</var> \
+      -v $PWD/static/custom_dc/<var>PROJECT_DIRECTORY</var>:/workspace/static/custom_dc/<var>PROJECT_DIRECTORY</var> \
       <var>IMAGE_NAME</var>:<var>IMAGE_TAG</var>
       </pre>
    </div>
   </div>
 </div>
 
+- The project directory is the directory you have set up for your development environment, as described in [Set up your environment](custom_ui.md#setup) (or `custom` if you are using the default).
 - The image name is a meaningful name, such as `datacommons-services`.
 - The image tag is a meaningful description of the version you are building, such as `latest`.
 

custom_dc/config.md

@@ -60,7 +60,7 @@ Each section contains some required and optional fields, which are described in
 
 ## Enable subdirectories {#subdirs}
 
-If you are using subdirectories, specify the file names using paths relative to the top-level directory (which you specify in the `env.list` file as the input directory), and be sure to set `"includeInputSubdirs": true` (the default is false if the option is not specified.) For example:
+If you are using subdirectories, specify the file names using paths relative to the top-level directory (which you specify in the `env.list` file as `INPUT_DIR`), and be sure to set `"includeInputSubdirs": true` (the default is false if the option is not specified.) For example:
 
 ```
 {
@@ -77,7 +77,7 @@ If you are using subdirectories, specify the file names using paths relative to
 
 ## Input files
 
-The top-level `inputFiles` lists out the CSV input files and options specific to each file. The file expression is the file name (including relative subdirectories, where applicable) or wildcard patterns if the same configuration applies to multiple files.
+The top-level `inputFiles` lists out the CSV input files and options specific to each file. The file expression is the file name (including relative subdirectories, where applicable) or wildcard patterns if the same configuration applies to multiple files. The files and sudirectories are assumed to be relative to the directory which you have specified as `INPUT_DIR` in your `env.list` file.
 
 You can use the `*` wildcard; matches are applied in the order in which they are specified in the config. For example, in the following:
 

custom_dc/custom_data.md

@@ -43,6 +43,8 @@ my_data/
     ├── datafile3.csv
     └── datafile4.csv
 ```
+The top-level directory (e.g. `my_data`) can live anywhere in the file system; you will specify the full path to it when you [configure your input directory](#env). When you set up your files in Google Cloud Storage using the Terraform script, it will automatically create a top-level directory in your bucket called `input`.
+
 The following sections walk you through the process of setting up your data. 
 
 ## Prerequisite steps
@@ -420,6 +422,7 @@ The following procedures show you how to load and serve your custom data locally
 
 To load data in Google Cloud, see instead [Load data in Google Cloud](/custom_dc/deploy_cloud.html) for procedures.
 
+{: #env}
 ### Configure environment variables
 
 Edit the `env.list` file you created [previously](/custom_dc/quickstart.html#env-vars) as follows:

custom_dc/custom_ui.md

@@ -19,6 +19,8 @@ The Custom Data Commons image provides a default site user interface that you wi
 
 This page describes how you can reuse and modify various code and configuration files that are provided for Custom Data Commons in the `website` repo.
 
+> **Note**:  Whenever you make changes you will need to build a custom version of the website. See [Build a local image](build_image.md#build-repo) for details.
+
 {: #setup}
 ## Before you start: Set up your environment
 

custom_dc/deploy_cloud.md

@@ -144,6 +144,7 @@ region  = "us-east1"
 
 ## Manage your data
 
+{: #data}
 ### Upload data files to Google Cloud Storage
 
 > **Note**: Before proceeding, make sure your data is in the correct format required by Data Commons, and you've written an accompanying config file. Please see [Prepare and load your own data](custom_data.md) for complete details.