From b254c83f7167afd0c71d7224262ad055419173f7 Mon Sep 17 00:00:00 2001 From: Artur Wdowiarski Date: Thu, 8 Sep 2022 21:34:15 +0200 Subject: [PATCH] Adapted an env var used in docs to reflect the change in latest ceramic release (#29) * Changed the docs to reflect the change of an env var used to run a ceramic node with indexing * Fixed the env var name and added a note about composedb not working on mainnet --- website/docs/first-composite.mdx | 6 ++++++ website/versioned_docs/version-0.2.x/first-composite.mdx | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/website/docs/first-composite.mdx b/website/docs/first-composite.mdx index 422b12238..f65cba496 100644 --- a/website/docs/first-composite.mdx +++ b/website/docs/first-composite.mdx @@ -9,6 +9,12 @@ This page presents how to create your first composite and deploy it to your loca ## Running a local Ceramic node +:::caution + +Because ComposeDB is still an experimental feature set built on top of Ceramic, if you want to use it with a Ceramic node, you need to set the `CERAMIC_ENABLE_EXPERIMENTAL_COMPOSE_DB` environment variable to `true`, before running a node. Note that ComposeDB is not yet supported on Ceramic mainnet. + +::: + The following steps require a local Ceramic node to be running. If you do not already have it running, you can use the following command: