Skip to content

Commit

Permalink
Fixing deprecated env vars
Browse files Browse the repository at this point in the history
  • Loading branch information
joedborg committed Mar 12, 2019
1 parent b2aaaef commit 9187fa5
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions src/en/developer-layers-interfaces.md
Original file line number Diff line number Diff line change
Expand Up @@ -129,10 +129,10 @@ interface-layers you may wish to write, and the

```bash
export JUJU_REPOSITORY=$HOME/charms
export LAYER_PATH=$JUJU_REPOSITORY/layers
export INTERFACE_PATH=$JUJU_REPOSITORY/interfaces
export CHARM_LAYER_DIRS=$JUJU_REPOSITORY/layers
export CHARM_INTERFACE_DIRS=$JUJU_REPOSITORY/interfaces

mkdir -p $LAYER_PATH $INTERFACE_PATH
mkdir -p $CHARM_LAYER_DIRS $CHARM_INTERFACE_DIRS
```

!!! Note:
Expand All @@ -141,7 +141,7 @@ mkdir -p $LAYER_PATH $INTERFACE_PATH
add the same export statements to a resource file that are evaluated when you
create a new console such as `~/.bashrc` depending on your shell.

The export of `INTERFACE_PATH` is an environment variable which tells the
The export of `CHARM_INTERFACE_DIRS` is an environment variable which tells the
`charm build` process where to scan for local interfaces not found in the
[layer registry](https://github.com/juju/layer-index/).

Expand All @@ -150,7 +150,7 @@ With our interface repository created, we can now create our new interface.
Next, create the directory to warehouse your interface.

```Bash
mkdir -p $INTERFACE_PATH/http
mkdir -p $CHARM_INTERFACE_DIRS/http
```

And declare the interface's metadata in `interface.yaml`.
Expand Down

0 comments on commit 9187fa5

Please sign in to comment.