Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs for env push #22

Merged
merged 2 commits into from
Sep 19, 2023
Merged

Docs for env push #22

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b363568
Docs for env push
djmb Aug 31, 2023
f9f7214
Update _docs/commands.md
dhh Sep 14, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions _docs/commands.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,19 @@ order: 3

# Commands

## Pushing environment files to the servers

Before you can deploy, you'll need to push env files to the servers. The will then be
dhh marked this conversation as resolved.
Show resolved Hide resolved
included in the docker run commands.

You can do this by running:

```bash
$ kamal env push
```

If you create the files with `kamal envify`, they will automatically be pushed for you.

## Running commands on servers

#### Run command on all servers
Expand Down
4 changes: 3 additions & 1 deletion _docs/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,6 +169,8 @@ env:
REDIS_URL: redis://redis1:6379/1
```

**Note:** Before you can start the containers you need to push the env variables up to the servers.

## Using secret env variables

If you have env variables that are secret, you can divide the `env` block into `clear` and `secret`:
Expand Down Expand Up @@ -208,7 +210,7 @@ volumes:

Directories act in a similar way to volumes except it will create a corresponding directory on the host before mounting the volume:

e.g.
e.g.

```yaml
service: kamal-demo
Expand Down