Docs

.gitbook.yaml

@@ -1,5 +1,5 @@
 root: ./docs/
 
 structure:
-  readme: ./tutorials/realtime.md
+  readme: ./workloads/realtime/deploy.md
   summary: summary.md

build/lint-docs.sh

@@ -32,7 +32,6 @@ fi
 output=$(cd "$ROOT/docs" && find . -type f \
 ! -path "./README.md" \
 ! -name "summary.md" \
-! -path "./tutorials/*" \
 ! -name "contributing.md" \
 -exec grep -L "WARNING: you are on the master branch, please refer to the docs on the branch that matches your \`cortex version\`" {} \;)
 if [[ $output ]]; then

build/lint.sh

@@ -142,7 +142,6 @@ else
   output=$(cd "$ROOT/docs" && find . -type f \
   ! -path "./README.md" \
   ! -name "summary.md" \
-  ! -path "./tutorials/*" \
   ! -name "contributing.md" \
   ! -name "*.json" \
   ! -name "*.txt" \

docs/aws/uninstall.md

@@ -43,6 +43,6 @@ On rare occasions, `cortex cluster down` may not be able to spin down your Corte
 
 1. Select the final stack (the one that ends in "-cluster") and click "Delete".
 
-    If deleting the stack fails, navigate to the EC2 dashboard in the AWS console, delete the load balancers that are associated with the cluster, and try again (you can determine which load balancers are associated with the cluster by setting the correct region in the console and checking the `cortex.dev/cluster-name` tag on all load balancers). If the problem still persists, delete any other AWS resources that are blocking the stack deletion and try again. Feel free to reach out to us on [gitter](https://gitter.im/cortexlabs/cortex) if you still aren't able to delete the stacks.
+    If deleting the stack fails, navigate to the EC2 dashboard in the AWS console, delete the load balancers that are associated with the cluster, and try again (you can determine which load balancers are associated with the cluster by setting the correct region in the console and checking the `cortex.dev/cluster-name` tag on all load balancers). If the problem still persists, delete any other AWS resources that are blocking the stack deletion and try again.
 
 1. In rare cases, you may need to delete other AWS resources associated with your Cortex cluster. For each the following resources, go to the appropriate AWS Dashboard (in the region that your cluster was in), and confirm that there are no resources left behind by the cluster: API Gateway API, API Gateway VPC Link, CloudWatch Dashboard, SQS Queues, S3 Bucket, and CloudWatch LogGroups (the Cortex bucket and log groups are not deleted by `cluster down` in order to preserve your data).

docs/contributing.md

@@ -2,7 +2,7 @@
 
 ## Remote development
 
-We recommend that you run your development environment on a cloud instance due to frequent docker registry pushing, e.g. an AWS EC2 instance or GCP VM. We've had a good experience using [Mutagen](https://mutagen.io/documentation/introduction) to synchronize local / remote file systems. Feel free to reach out to us on [gitter](https://gitter.im/cortexlabs/cortex) if you have any questions about this.
+We recommend that you run your development environment on a cloud instance due to frequent docker registry pushing, e.g. an AWS EC2 instance or GCP VM. We've had a good experience using [Mutagen](https://mutagen.io/documentation/introduction) to synchronize local / remote file systems.
 
 ## Prerequisites
 
@@ -248,5 +248,3 @@ If you are only modifying the operator, `make operator-local-aws` will build and
 If you are modifying code in the API images (i.e. any of the Python serving code), `make images-dev-aws` may build more images than you need during testing. For example, if you are only testing using the `python-predictor-cpu` image, you can run `./dev/registry.sh update-single python-predictor-cpu --provider aws` (or use `--provider local` if testing locally).
 
 See `Makefile` for additional dev commands.
-
-Feel free to [chat with us](https://gitter.im/cortexlabs/cortex) if you have any questions.