Multi-container development environment for building dapps on test chains
I'm trying to find a suitable solution to the problem of having to run switch between running Ethereum nodes and running dapps. Most of the programs all use the same few ports and don't work together quite so well out of the box.
Docker Compose seems like a reasonable solution - by setting up a virtual network of containers for individual services, and wrapping it behind a web proxy, it should remove a lot of the overhead of process and dependency management.
This project also aims to create a collection of custom wrapper binaries around the supported services, to maintain the interface of local development while everything runs virtualized and separated from localhost.
This repository is currently a WIP attempt to get a sane (to me?) Ethereum dev environment up and running inside docker-compose.
Dev tools include:
Clone this repository somewhere to be your docker-eth-dev home directory ($ETH
)
git clone https://github.com/gnidan/docker-eth-dev.git <dir>
This directory will contain the contents of this repository:
dapps
top-level directory
truffle init
result, reconfigured)Activate shell environment
source <dir>/bin/activate.sh
This aliases all the wrapper binaries so they're available for us in the shell.
Create Docker volume for Ropsten Parity
docker volume create --name=parity-testnet-data
This creates a persistent volume so that the Ropsten account information/ chain data does not get lost when the containers are stopped.
Start Docker containers
docker-compose up -d
This runs nginx, testrpc, and parity-testnet inside containers. Port 80 will be opened on localhost for nginx's proxy.
Add parity-testnet.ethereum
to your /etc/hosts file, pointing locally or
at your docker-machine
This is so that nginx may recognize the resource you are trying to reach.
Visit http://parity-testnet.ethereum/
in your browser.
Run parity-testnet signer new-token
in your active env shell.
In case Parity Wallet needs to authenticate with the running parity-testnet container.
Note: In case anything stops working, I find that restarting docker-compose from scratch seems to help:
docker-compose down
docker-compose up -d
Dapps should live in separate directories in $ETH/dapps
for truffle
to
behave as expected
truffle serve
configuration could use some love and might not work right.
This env works by setting alises - if necessary, you can do \truffle
, etc.
This opens port 80 locally. That's currently hardcoded in. I'm looking for ways around this, or to make it easier to deal with.
I have no idea if configuring Parity behind an nginx proxy is wildly unsafe, hence why it's only set up to do Ropsten right now.
At the very least, though, I will say that Parity tries very hard to prevent you from configuring it this way.