Add how to manage JSON/INI file Store using Configu recipe

content/Concepts/config-store.mdx

@@ -50,7 +50,7 @@ You can choose the appropriate `ConfigStore` based on your specific use case, an
   category="file"
   name="Ini File"
   type="ini-file"
-  interfaces={['Node.js']}
+  interfaces={['CLI', 'Node.js']}
   docs="https://configu.com/docs/"
   configs="https://configu.com/docs/"
 />

content/Recipes/files-w-configu.mdx

@@ -0,0 +1,203 @@
+---
+id: files-w-configu
+slug: files-w-configu
+title: Managing configuration files using Configu Orchestrator (open-source)
+---
+
+Today's dev teams are tasked with managing Config Ops on the _platform_ as well,
+Configu lets you only worry about your application [schemas](/config-schema), with Configu providing the rest of what's needed, including managing the diffrent storage platforms
+and validating your new config values. Check out the tutorial below that shows how to use [Configu Orchestrator (open-source)](https://github.com/configu/configu) to manage
+[JSON files](https://json.org) and [INI files](https://en.wikipedia.org/wiki/INI_file).
+
+![image](./img/files-diagram.png)
+
+To complete the tutorial, you'll need:
+
+- A [JSON file](https://json.org) or an [INI file](https://en.wikipedia.org/wiki/INI_file)
+- [Configu's CLI](/cli-setup)
+- [hackathon-starter application](https://github.com/sahat/hackathon-starter)
+
+<Admonition type="info">
+- Make sure that the files are already created when using the Configu CLI.
+- When using a JSON file, make sure it is a root-level array as such:
+```json
+[]
+```
+
+</Admonition>
+
+As most applications already have configuration files, In this example, we will use the `.env.example` file from the hackathon-starter repo:
+
+`.env.example`
+
+```bash
+BASE_URL=http://localhost:8080
+MONGODB_URI=mongodb://localhost:27017/test
+SITE_CONTACT_EMAIL=youremail@yourdomain.com
+
+...
+
+```
+
+## Step 1 - Create schema declaration
+
+Instead of maintaining a `.env` file for each environment or duplicating the keys,
+create a `.cfgu` schema declaration for this service, so that each change will only have to be made once (only the key in the schema) and then the values will be initialized by the same interface.
+We will use the `init` command to generate it and for this example, we can also use the `--import` flag to auto-generate it from the existing `.env` file:
+
+```bash
+configu init --import .env.example --defaults --types --name app
+```
+
+<Admonition type="info">
+  `--types` will automatically generate the types for you, based on the supported types. If you use
+  this flag, always check and verify that the generated types are accurate
+</Admonition>
+
+`app.cfgu.json`
+
+```json
+{
+  "BASE_URL": {
+    "type": "URL",
+    "default": "http://localhost:8080"
+  },
+  "MONGODB_URI": {
+    "type": "String",
+    "default": "mongodb://localhost:27017/test"
+  },
+  "SITE_CONTACT_EMAIL": {
+    "type": "Email",
+    "default": "youremail@yourdomain.com"
+  },
+
+  ...
+}
+```
+
+<Admonition type="info">
+  Although saving configurations in the source control is considered to be bad practice, the Cfgu
+  format is designed to be part of the code as it doesn't include any sensitive values. Doing that
+  increases developers' velocity and helps them avoid leaving the terminal/IDE.
+</Admonition>
+
+## Step 2 - Use defaults for local development
+
+<Admonition type="info">
+  For the full instructions please follow the `hackathon-starter` [getting started
+  guide](https://github.com/sahat/hackathon-starter/blob/master/README.md#getting-started)
+</Admonition>
+
+Running a local environment was never easier, run Configu seamlessly with your app.
+
+```bash
+configu eval --schema "./app.cfgu.json" | configu export --run "node app.js"
+```
+
+## Step 3 - Manage configs in JSON/INI files using Configu Orchestrator
+
+Using a single set of commands we can control any store from local files to secret managers.
+In the following example, we will manage our configs over our JSON/INI files.
+
+### Using JSON/INI files
+
+Configu's CLI needs to be directed to your desired file by providing a file path via the [.configu file](../cli-config).
+
+example:
+
+<CodeTabs labels={["JSON File", "INI File"]}>
+
+```json
+{
+  "stores": {
+    "file-store": {
+      "type": "json-file",
+      "configuration": {
+        "path": "path/to/file.json"
+      }
+    }
+  }
+}
+```
+
+```json
+{
+  "stores": {
+    "file-store": {
+      "type": "ini-file",
+      "configuration": {
+        "path": "path/to/file.ini"
+      }
+    }
+  }
+}
+```
+
+</CodeTabs>
+
+### Upsert values
+
+```bash
+configu upsert --store "file-store" --set "prod" --schema "./app.cfgu.json" \
+    -c "BASE_URL=http://app.yourdomain.com" \
+    -c "SITE_CONTACT_EMAIL=info@yourdomain.com"
+```
+
+We can also easily add configs to additional environments like `test`
+
+```bash
+configu upsert --store "file-store" --set "test" --schema "./app.cfgu.json" \
+    -c "BASE_URL=http://app.test.yourdomain.com" -c "SITE_CONTACT_EMAIL=test@yourdomain.com"
+```
+
+Upsert result:
+
+<CodeTabs labels={["JSON File", "INI File"]}>
+
+```json
+[
+  {
+    "key": "BASE_URL",
+    "set": "test",
+    "value": "http://app.test.yourdomain.com"
+  },
+  {
+    "key": "SITE_CONTACT_EMAIL",
+    "set": "test",
+    "value": "test@yourdomain.com"
+  },
+  {
+    "key": "BASE_URL",
+    "set": "prod",
+    "value": "http://app.yourdomain.co.il"
+  },
+  {
+    "key": "SITE_CONTACT_EMAIL",
+    "set": "prod",
+    "value": "info@yourdomain.com"
+  }
+]
+```
+
+```ini
+[test]
+BASE_URL=http://app.test.yourdomain.com
+SITE_CONTACT_EMAIL=test@yourdomain.com
+
+[prod]
+BASE_URL=http://app.yourdomain.com
+SITE_CONTACT_EMAIL=info@yourdomain.com
+```
+
+</CodeTabs>
+
+### Export values
+
+Similar to the way we previously used the Cfgu defaults we can evaluate and export from any store we need.
+
+```bash
+configu eval --store "file-store" --set "prod" --schema "./app.cfgu.json" \
+ | configu export --run "node app.js"
+```
+
+You're done! This was a simple operation, but that's the best way to show someone the power and the simplicity of Configu Orchestrator and how you can use it to manage your configuration automatically and safely using all your current stores.

content/Recipes/hc-vault-w-configu.mdx

@@ -86,18 +86,18 @@ Running a local environment was never easier, choose your preferred way to injec
 - Run Configu seamlessly with your app
 
   ```bash
-  configu eval --schema "./my-app.cfgu.json" --defaults | configu export --run "py my-app.py"
+  configu eval --schema "./my-app.cfgu.json" | configu export --run "py my-app.py"
   ```
 
 - Inject the variables into your shell
 
   ```bash
-  configu eval --schema "./my-app.cfgu.json" --defaults | configu export --source
+  configu eval --schema "./my-app.cfgu.json" | configu export --source
   ```
 
 - Download and use `.env` file or any other format you want
   ```bash
-  configu eval --schema "./my-app.cfgu.json" --defaults | configu export --format "Dotenv" > .env.development
+  configu eval --schema "./my-app.cfgu.json" | configu export --format "Dotenv" > .env.development
   ```
 
 ## Step 3 - Manage configs in HashiCorp Vault using Configu Orchestrator
@@ -114,7 +114,7 @@ If not please configure your environment with the required variables (See variab
 
 ```bash
 configu upsert --store "hashicorp-vault" --schema "./my-app.cfgu.json" --set "prod" \
-    --config "DB_USER=user" --config "DB_PASSWORD=123" --config "DB_HOST=localhots" \
+    --config "DB_USER=user" --config "DB_PASSWORD=123" --config "DB_HOST=localhost" \
     --config "DB_PORT=5433" --config "DB_NAME=database"
 ```
 

content/sidebar.json

@@ -192,6 +192,10 @@
         {
           "title": "Managing HashiCorp Vault using Configu",
           "slug": "hc-vault-w-configu"
+        },
+        {
+          "title": "Managing configuration files using Configu",
+          "slug": "files-w-configu"
         }
       ]
     }