Update the README with cloud storage information

README.md

@@ -62,11 +62,7 @@ resources including tutorials and documentation.
   
 ![Gif of Label Studio annotating different types of data](https://raw.githubusercontent.com/heartexlabs/label-studio/master/images/annotation_examples.gif)
 
-Have a custom dataset? You can customize Label Studio to fit your needs. Read
-an [introductory blog post](https://towardsdatascience.com/introducing-label-studio-a-swiss-army-knife-of-data-labeling-140c1be92881)
-to learn more. 
-
-### Configuring Label Studio Spaces for Secure Use
+### Making your Label Studio Hugging Face Space production-ready
 
 By default this space allows for the unrestricted creation of new accounts
 will full access to all projects and data. This is great for trying out
@@ -98,13 +94,13 @@ Postgres. We strongly recommend setting these as secrets to prevent leaking
 information about your database service to the public in your spaces
 definition.
 
-    ENV DJANGO_DB=default
-    ENV POSTGRE_NAME=<postgres_name>
-    ENV POSTGRE_PORT=<db_port>
-    ENV POSTGRE_USER=<postgres_user>
-    ENV POSTGRE_PASSWORD=<password>
-    ENV POSTGRE_PORT=<db_port>
-    ENV POSTGRE_HOST=<db_host>
+    DJANGO_DB=default
+    POSTGRE_NAME=<postgres_name>
+    POSTGRE_PORT=<db_port>
+    POSTGRE_USER=<postgres_user>
+    POSTGRE_PASSWORD=<password>
+    POSTGRE_PORT=<db_port>
+    POSTGRE_HOST=<db_host>
 
 Add the following environment variable to remove the warning about ephemeral
 storage.
@@ -114,8 +110,39 @@ storage.
 Note that you will need to connect cloud storage to host data items that you
 want to annotate, as local storage will not be preserved across a space reset.
 
+By default the only data storage enabled for this space is local. In the case
+of a space reset, all data will be lost. To enable permanent storage, you
+must enable a cloud storage connector. We also strongly recommend enabling
+configuration persistence to preserve project data, annotations, and user
+settings. Choose the appropriate cloud connector and configure the secrets
+for it.
+
+#### Amazon S3
+    STORAGE_TYPE=s3
+    STORAGE_AWS_ACCESS_KEY_ID="<YOUR_ACCESS_KEY_ID>"
+    STORAGE_AWS_SECRET_ACCESS_KEY="<YOUR_SECRET_ACCESS_KEY>"
+    STORAGE_AWS_BUCKET_NAME="<YOUR_BUCKET_NAME>"
+    STORAGE_AWS_REGION_NAME="<YOUR_BUCKET_REGION>"
+    STORAGE_AWS_FOLDER=""
+
+#### Google Cloud Storage
+
+    STORAGE_TYPE=gcs
+    STORAGE_GCS_BUCKET_NAME="<YOUR_BUCKET_NAME>"
+    STORAGE_GCS_PROJECT_ID="<YOUR_PROJECT_ID>"
+    STORAGE_GCS_FOLDER=""
+    GOOGLE_APPLICATION_CREDENTIALS="/opt/heartex/secrets/key.json"
+
+Azure Blob Storage
+==================
+
+    STORAGE_TYPE=azure
+    STORAGE_AZURE_ACCOUNT_NAME="<YOUR_STORAGE_ACCOUNT>"
+    STORAGE_AZURE_ACCOUNT_KEY="<YOUR_STORAGE_KEY>"
+    STORAGE_AZURE_CONTAINER_NAME="<YOUR_CONTAINER_NAME>"
+    STORAGE_AZURE_FOLDER=""
+
+
 ## Questions? Concerns? Want to get involved? 
 
 Email the community team at [[email protected]](mailto:[email protected])
-
-</body>