awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-10-03 17:26:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'main' of https://github.com/Infisical/infisical

Browse Source
This commit is contained in:
Tuan Dang
2022-11-20 23:44:54 -05:00
parent 4778e1ce6f e188524a93
commit ebe6be201a
3 changed files with 10 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3
View File
@@ -44,6 +44,9 @@
And more. 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? ## What's cool about this?
Infisical is simple, E2EE, and (soon to be) complete. Infisical is simple, E2EE, and (soon to be) complete.
docs/getting-started/introduction.mdx
+1 -1
View File
@@ -3,7 +3,7 @@ title: "Introduction"
--- ---
<iframe <iframe
src="https://www.youtube.com/embed/0q_IroMV1ns" src="https://www.youtube.com/embed/JS3OKYU2078"
width="100%" width="100%"
height="400" height="400"
></iframe> ></iframe>
docs/integrations/docker-compose.mdx
+6 -6
View File
@@ -14,7 +14,7 @@ If you have multiple services and they do not use the same secrets, you will hav
</Info> </Info>
### Step 3: Tell Docker Compose your Infisical Token ### 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. This will ensure that you can set Infisical Tokens for multiple services.
@@ -36,22 +36,22 @@ services:
- INFISICAL_TOKEN: ${INFISICAL_TOEKN_FOR_API} - INFISICAL_TOKEN: ${INFISICAL_TOEKN_FOR_API}
``` ```
### 4: Set shell variables ### 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 donce, it will be used to populate the corresponding `INFISICAL_TOKEN` 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. in your Docker Compose file.
``` bash ``` bash
#Example #Example
# Token refers to the token we generated in step 2 for this service # 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 # 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. Then run your compose file in the same terminal.
```bash ```bash
docker-compose docker-compose ...
``` ```