mirror of
https://github.com/awatertrevi/infisical.git
synced 2026-09-22 13:39:35 +00:00
documentation revamp
This commit is contained in:
@@ -1,11 +1,12 @@
|
||||
---
|
||||
title: "Folders"
|
||||
description: "Organize your secrets with folders"
|
||||
description: "Learn how to organize secrets with folders."
|
||||
---
|
||||
|
||||
Infisical's folder feature lets you store secrets at a specific folder; we also call this **path-based secret storage**.
|
||||
This is great for organizing secrets around hierarchies when multiple services, types of secrets, etc. are involved at great quantities.
|
||||
With folders that can go infinitely deep, you can mirror your application architecture (be it microservices or monorepos)
|
||||
Infisical Folders enable users to organize secrets using custom structures dependent on the intended use case (also known as **path-based secret storage**).
|
||||
|
||||
It is great for organizing secrets around hierarchies with multiple services or types of secrets involved at large quantities.
|
||||
Infisical Folders can be infinitely nested to mirror your application architecture – whether it's microservices, monorepos,
|
||||
or any logical grouping that best suits your needs.
|
||||
|
||||
Consider the following structure for a microservice architecture:
|
||||
@@ -25,9 +26,7 @@ In this example, we store environment variables for each microservice under each
|
||||
We also store user-specific secrets for micro-service 1 under `/service1/users`. With this folder structure in place, your applications only need to specify a path like `/microservice1/envars` to fetch secrets from there.
|
||||
By extending this example, you can see how path-based secret storage provides a versatile approach to manage secrets for any architecture.
|
||||
|
||||
## Folders
|
||||
|
||||
### Managing folders
|
||||
## Managing folders
|
||||
|
||||
To add a folder, press the downward chevron to the right of the **Add Secret** button; then press on the **Add Folder** button.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user