Skip to content
This repository has been archived by the owner on Dec 16, 2021. It is now read-only.

docs: add development usage for local docker build #67

Merged
merged 5 commits into from
Jun 10, 2020
Merged
Changes from all commits
Commits
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
8 changes: 8 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,14 @@ Distribution package for Dash Masternode installation

- [Install](#install)
- [Usage](#usage)
- [Configuration presets](#configuration-presets)
- [Command line interface](#cli)
- [Start node](#start-node)
- [Stop node](#stop-node)
- [Register masternode](#register-masternode)
- [Reset data](#reset-data)
- [Development](#development)
- [Docker Compose](#docker-compose)
shumkov marked this conversation as resolved.
Show resolved Hide resolved
- [Contributing](#contributing)
- [License](#license)

Expand Down Expand Up @@ -160,6 +164,10 @@ To reset an Evonet node:
$ mn reset evonet
```

### Development

When developing on a standalone node (the `local` preset), a local path for DAPI or Drive may be specified via the `--drive-image-build-path` and `--dapi-image-build-path` options of the `start` command. A Docker image will be built from the provided path and then used by mn-bootstrap. This allows developers to quickly test changes to DAPI and Drive with minimal overhead.

### Docker Compose

In case if you need to use Docker Compose directly you need to pass a preset configuration.
Expand Down