From 7ce447efe4b6a47baeebff8c27a67573129f0d81 Mon Sep 17 00:00:00 2001 From: Maidul Islam Date: Sun, 20 Nov 2022 23:00:46 -0500 Subject: [PATCH 1/3] get started to read me --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index e964264d90..ec566b18b1 100644 --- a/README.md +++ b/README.md @@ -44,6 +44,9 @@ And more. +## Get started +To quickly get started, visit our [get started guide](https://infisical.com/docs/getting-started/introduction). + ## What's cool about this? Infisical is simple, E2EE, and (soon to be) complete. From 676f5e121a75b4cb644d0f312446b641ce1ca71d Mon Sep 17 00:00:00 2001 From: Maidul Islam Date: Sun, 20 Nov 2022 23:24:41 -0500 Subject: [PATCH 2/3] update docker compose docs --- docs/integrations/docker-compose.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/integrations/docker-compose.mdx b/docs/integrations/docker-compose.mdx index ec57fd1fae..b6a22f109e 100644 --- a/docs/integrations/docker-compose.mdx +++ b/docs/integrations/docker-compose.mdx @@ -14,7 +14,7 @@ If you have multiple services and they do not use the same secrets, you will hav ### Step 3: Tell Docker Compose your Infisical Token -For each service you want to inject secrets into, set an environment variable called `INFISICAL_TOKEN` equal to a useful shell variable name. +For each service you want to inject secrets into, set an environment variable called `INFISICAL_TOKEN` equal to a helpful identifier variable. This will ensure that you can set Infisical Tokens for multiple services. @@ -36,22 +36,22 @@ services: - INFISICAL_TOKEN: ${INFISICAL_TOEKN_FOR_API} ``` -### 4: Set shell variables -Next, set the shell variables you defined in your compose file. This can be done manually or via your CI/CD environment. Once donce, it will be used to populate the corresponding `INFISICAL_TOKEN` +### 4: Export shell variables +Next, set the shell variables you defined in your compose file. This can be done manually or via your CI/CD environment. Once done, it will be used to populate the corresponding `INFISICAL_TOKEN` in your Docker Compose file. ``` bash #Example # Token refers to the token we generated in step 2 for this service -INFISICAL_TOEKN_FOR_WEB= +export INFISICAL_TOEKN_FOR_WEB= # Token refers to the token we generated in step 2 for this service -INFISICAL_TOEKN_FOR_API= +export INFISICAL_TOEKN_FOR_API= ``` Then run your compose file in the same terminal. ```bash -docker-compose +docker-compose ... ``` From e188524a938e92c96aa85a13c82819d704e9763c Mon Sep 17 00:00:00 2001 From: Maidul Islam Date: Sun, 20 Nov 2022 23:34:13 -0500 Subject: [PATCH 3/3] update to new intro video for docs --- docs/getting-started/introduction.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/introduction.mdx b/docs/getting-started/introduction.mdx index 106d37c14c..7f5a6cb2ab 100644 --- a/docs/getting-started/introduction.mdx +++ b/docs/getting-started/introduction.mdx @@ -3,7 +3,7 @@ title: "Introduction" ---