Add links and refrences to secrets

Author: Lagoja

docs/app/docs/configuration.md

@@ -180,6 +180,34 @@ For example, you could set variable `$FOO` to `bar` by adding the following to y
 Currently, you can only set values using string literals, `$PWD`, and `$PATH`. Any other values with environment variables will not be expanded when starting your shell.
 
 
+### Env From
+
+Env from takes a string or list of strings for loading environment variables into your shells and scripts. Currently it supports loading from two sources: .env files, and Jetify Secrsts.
+
+#### .env Files
+
+You can load environment variables from a `.env` file by adding the path to the file in the `env_from` field. This is useful for loading secrets or other sensitive information that you don't want to store in your `devbox.json`.
+
+```json
+{
+    "env_from": "path/to/.env"
+}
+```
+
+This will load the environment variables from the `.env` file into your shell when you run `devbox shell` or `devbox run`. Note that environment variables set in the `.env` file will be overridden if the same variable is set directly in your `devbox.json`
+
+#### Jetify Secrets
+
+You can securely load secrets from Jetify Secrets by running `devbox secrets init` and creating a project in Jetify Cloud. This will add the `jetpack-cloud` field to `env_from` in your project.
+
+```json
+{
+    "env_from": "jetpack-cloud"
+}
+```
+
+Note that setting secrets securetly with Jetify Secrets requires a Jetify Cloud account. For more information, see the [Jetify Secrets](/cloud/docs/secrets/) guide.
+
 ### Shell
 
 The Shell object defines init hooks and scripts that can be run with your shell. Right now two fields are supported: `init_hook`, which run a set of commands every time you start a devbox shell, and `scripts`, which are commands that can be run using `devbox run`

docs/app/docs/guides/secrets.md

@@ -0,0 +1,43 @@
+---
+title: Managing Secrets and Environment Variables
+---
+
+Devbox provides a few different methods for including environment variables and secrets in your Devbox shell. This guide will walk you through the different methods and help you choose the best one for your use case.
+
+## Setting Environment Variables in your Devbox Config
+
+Environment variables that do not need to be stored securely can be set directly in your `devbox.json` under the `env` object. This is useful for non-secret variables that you want to have set in your Devbox shells:
+
+```json
+{
+  "env": {
+    "MY_VAR": "my_value"
+  },
+  "packages": {},
+  "shell": {}
+}
+```
+
+Currently, you can only set values using string literals, `$PWD`, and `$PATH`. Any other values with environment variables will not be expanded when starting your shell. For more details, see (/devbox/docs/configuration.md).
+
+## Setting Environment Variables with Env Files
+
+For environment variables that you want to keep out of your `devbox.json` file, you can use an env file. Env files are text files that contain key-value pairs, one per line. You can reference an env file in your `devbox.json` like this:
+
+```json
+{
+  "packages": {},
+  "shell": {},
+  "env_from": [
+    "path/to/.env"
+  ]
+}
+```
+
+## Securely Managing Secrets with Jetify Secrets
+
+For secrets that need to be stored securely, you can use Jetify Secrets. Jetify Secrets is a secure secrets management service that allows you to store and manage your secrets with Jetify. You can then access your secrets whenever you start your Devbox shell, and manage them from the CLI using [`devbox secrets`](/devbox/docs/cli_reference/devbox_secrets).
+
+To get started with Jetify Secrets, you will need to first create an account on Jetify Cloud and login with `devbox auth login`. Once your account is created, you can create a new project and start adding secrets to your project using `devbox secrets init`.
+
+For more details on how to manage your secrets from the CLI, see our guide on [**Jetify Secrets**](/cloud/docs/secrets/secrets_cli).