Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
  • Loading branch information
Tuan Dang committed Nov 21, 2022
2 parents 4778e1c + e188524 commit ebe6be2
Show file tree
Hide file tree
Showing 3 changed files with 10 additions and 7 deletions.
3 changes: 3 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion docs/getting-started/introduction.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: "Introduction"
---

<iframe
src="https://www.youtube.com/embed/0q_IroMV1ns"
src="https://www.youtube.com/embed/JS3OKYU2078"
width="100%"
height="400"
></iframe>
Expand Down
12 changes: 6 additions & 6 deletions docs/integrations/docker-compose.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ If you have multiple services and they do not use the same secrets, you will hav
</Info>

### 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.


Expand All @@ -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=<token>
export INFISICAL_TOEKN_FOR_WEB=<token>

# Token refers to the token we generated in step 2 for this service
INFISICAL_TOEKN_FOR_API=<token>
export INFISICAL_TOEKN_FOR_API=<token>
```

Then run your compose file in the same terminal.

```bash
docker-compose
docker-compose ...
```

0 comments on commit ebe6be2

Please sign in to comment.