95156b7d1c
## Issue being fixed or feature implemented Install of dash_hash will change once https://github.com/dashpay/dash_hash/pull/17/ is merged ## What was done? - Changed install instructions to match new install in dash_hash README - Updated Dockerfile to install correctly ## How Has This Been Tested? N/A ## Breaking Changes None ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [x] I have made corresponding changes to the documentation |
||
|---|---|---|
| .. | ||
| ci | ||
| deploy | ||
| develop | ||
| README.md | ||
Containers
This directory contains configuration files for containerization utilities.
Currently two Docker containers exist, ci defines how Dash's GitLab CI container is built and the dev builds on top of the ci to provide a containerized development environment that is as close as possible to CI for contributors!
Usage Guide
We utilise edrevo's dockerfile-plus, a syntax extension that leverages Docker BuildKit to reduce the amount of repetitive code.
As BuildKit is opt-in within many currently supported versions of Docker (as of this writing), you need to
set the following environment variables before continuing. While not needed after the initial docker-compose build
(barring updates to the Dockerfile), we recommend placing this in your ~/.bash_profile/~/.zshrc or equivalent
export DOCKER_BUILDKIT=1
export COMPOSE_DOCKER_CLI_BUILD=1
After that, it's simply a matter of building and running your own development container. You can use extensions for your IDE like Visual Studio Code's Remote Containers to run terminal commands from inside the terminal and build Dash Core.
cd contrib/containers/develop
docker-compose build
docker-compose run container