Add docs for Apollo config

packages/apollo-cli/README.md

@@ -5,16 +5,19 @@
 Apollo CLI brings together your GraphQL clients and servers with tools for validating your schema, linting your operations for compatibility with your server, and generating static types for improved client-side type safety.
 
 <!-- toc -->
-* [Apollo CLI](#apollo-cli)
-* [Usage](#usage)
-* [Commands](#commands)
-* [Code Generation](#code-generation)
-* [Contributing](#contributing)
-<!-- tocstop -->
+
+- [Apollo CLI](#apollo-cli)
+- [Usage](#usage)
+- [Commands](#commands)
+- [Configuration](#configuration)
+- [Code Generation](#code-generation)
+- [Contributing](#contributing)
+  <!-- tocstop -->
 
 # Usage
 
 <!-- usage -->
+
 ```sh-session
 $ npm install -g apollo
 $ apollo COMMAND
@@ -26,17 +29,19 @@ USAGE
   $ apollo COMMAND
 ...
 ```
+
 <!-- usagestop -->
 
 # Commands
 
 <!-- commands -->
-* [`apollo codegen:generate [OUTPUT]`](#apollo-codegengenerate-output)
-* [`apollo help [COMMAND]`](#apollo-help-command)
-* [`apollo queries:check`](#apollo-queriescheck)
-* [`apollo schema:check`](#apollo-schemacheck)
-* [`apollo schema:download OUTPUT`](#apollo-schemadownload-output)
-* [`apollo schema:publish`](#apollo-schemapublish)
+
+- [`apollo codegen:generate [OUTPUT]`](#apollo-codegengenerate-output)
+- [`apollo help [COMMAND]`](#apollo-help-command)
+- [`apollo queries:check`](#apollo-queriescheck)
+- [`apollo schema:check`](#apollo-schemacheck)
+- [`apollo schema:download OUTPUT`](#apollo-schemadownload-output)
+- [`apollo schema:publish`](#apollo-schemapublish)
 
 ## `apollo codegen:generate [OUTPUT]`
 
@@ -50,11 +55,11 @@ ARGUMENTS
   OUTPUT
       Directory to which generated files will be written.
       - For TypeScript/Flow generators, this specifies a directory relative to each source file by default.
-      - For TypeScript/Flow generators with the "outputFlat" flag is set, and for the Swift generator, this specifies a 
+      - For TypeScript/Flow generators with the "outputFlat" flag is set, and for the Swift generator, this specifies a
       file or directory (absolute or relative to the current working directory) to which:
          - a file will be written for each query (if "output" is a directory)
          - all generated types will be written
-      - For all other types, this defines a file (absolute or relative to the current working directory) to which all 
+      - For all other types, this defines a file (absolute or relative to the current working directory) to which all
       generated types are written.
 
 OPTIONS
@@ -204,8 +209,93 @@ OPTIONS
 ```
 
 _See code: [src/commands/schema/publish.ts](https://github.com/apollographql/apollo-cli/blob/v1.5.0/src/commands/schema/publish.ts)_
+
 <!-- commandsstop -->
 
+# Configuration
+
+The Apollo CLI and VS Code extension can be configured with an Apollo Config file. Apollo configuration is stored as a plain object and can be either specified under the `apollo` key in your `package.json` or as a separate `apollo.config.js` which exports the config data.
+
+The core of any configuration is specifying schemas and queries. Schemas specify information about your backend such as where to get the schema, what endpoint to make requests against, and the Apollo Engine API key to get schema updates and stats from. Queries define which documents Apollo tooling should analyze and tie them to the schema they are targeting.
+
+Let's take a look at a basic configuration file (`package.json` style):
+
+```js
+{
+  ...
+  "apollo": {
+    "schemas": {
+      "myPrimaryBackend": {
+        "schema": "downloadedSchema.json", // if not defined the an introspection query will be run
+        "endpoint": "http://example.com/graphql", // if not defined the schema will be downloaded from Apollo Engine
+        "engineKey": "my-engine-key" // use this key when connecting to Apollo Engine
+      }
+    },
+    "queries": [
+      {
+        "schema": "myPrimaryBackend", // reference the previously defined schema
+        "includes": [ "**/*.tsx" ], // load queries from .tsx files
+        "excludes": [ "node_modules/**" ] // don't include any matching files from node_modules
+      }
+    ]
+  }
+}
+```
+
+Or in `apollo.config.js` style:
+
+```js
+...
+
+module.exports = {
+  schemas: {
+    myPrimaryBackend: {
+      schema: "downloadedSchema.json", // if not defined the an introspection query will be run
+      endpoint: "http://example.com/graphql", // if not defined the schema will be downloaded from Apollo Engine
+      engineKey: "my-engine-key" // use this key when connecting to Apollo Engine
+    }
+  },
+  queries: [
+    {
+      schema: "myPrimaryBackend", // reference the previously defined schema
+      includes: [ "**/*.tsx" ], // load queries from .tsx files
+      excludes: [ "node_modules/**" ] // don't include any matching files from node_modules
+    }
+  ]
+}
+```
+
+## Endpoint Configuration
+
+When configuring a schema's endpoint, you can either pass in a string or an object, which allows for specifying advanced options like headers and subscription endpoints.
+
+```js
+endpoint: {
+  url: "http://example.com/graphql",
+  subscriptions: "ws://example.com/graphql",
+  headers: {
+    cookie: "myCookie=myCookieValue"
+  }
+}
+```
+
+## Schema Dependencies
+
+Schemas can also declare dependencies on eachother, which can be useful in situations like having a client-side schema for `apollo-link-state`. To declare a dependency, use the `extends` key. When working with a client-side schema, make sure to also specify the `clientSide` key to enable code-generation support.
+
+```js
+schemas: {
+  myServerSideSchema: {
+    ...
+  },
+  myClientSideSchema: {
+    extends: "myServerSideSchema",
+    clientSide: true
+    ...
+  }
+}
+```
+
 # Code Generation
 
 ## Accompanying Libraries