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

Jump to bottom

documentation formatting changes #207

Merged
merged 1 commit into from
Nov 20, 2022
Merged

documentation formatting changes #207

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/docs/build.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ brave build -r $REMOTE

Where `$REMOTE` is the name of a trusted Bravetools remote.

## Using Local image store
## Using a Local Image Store
Every image built by Bravetools can be used as a base for any subsequent image configurations. For example, you might have pre-built images containing the full python3 development environment, which can be re-used as bases for python3-dependent applications.

To use images in the local store, set the `location` field of the Bravefile to `local`.
Expand All @@ -94,7 +94,7 @@ base:
location: public
```

Upon build completion, the image will be pushed to a remote called `qemu` for later use and a local copy will be stored in on the host's file system
Upon build completion, the image will be pushed to a remote called `qemu` for later use and a local copy will be stored on the host's file system

To use an image stored on your remote, reference it in your `Bravefile` as:

Expand Down