My Rust EOS Dev Environment (Naive)

This environment uses EOSIO v1 and installs EOSIO software binaries instead of building from source (see Dockerfile). It sets up eosio-rust for contract development and eoslime (nodejs) for tests. Nodeos and keos are launched in their own containers.

Don't deploy production code using this environment. And don't hold actual tokens in a wallet made from here.

git clone https://github.com/7db9a/rust-eos-dev-env-starter your-eos-project
cd your-eos-project/docker
docker build -t rust-eos-dev:latest .
docker volume create --name=example-nodeos-data-volume
docker volume create --name=example-keosd-data-volume
docker volume create --name=example-cargo-data-volume
docker-compose up

If you change the name from 'example' to 'your-eos-project', for example, the following files need to be updated:

dev.sh
README.md
docker/docker-compose.yml
example.abi.json
example.contracts.md
testing/tests/basic_repo_operations.js

A simple search and replace will suffice. Be sure to rename the file names of example.abi.json and example.contracts.md, too.

Then from the top of your new project's directory:

./dev.sh wallet-create

Add the password to the docker/eos.env. The pub and priv keys in the file are for development.

Restart the services:

docker-compose stop && docker-compose up --force-recreate

Build, set, and test

To build the rust code, deploy it locally, and run tests:

./dev.sh run

The commands broken down individually:

Build code

./dev.sh build

Set code

./dev.sh set

Test code

./dev.sh test

dev.sh is very basic and not generalized. Feel free to modify it or make your own script, or just run the actual underlying commands.

Caveats

The package name of your Cargo.toml will become the prefix fo the wasm binaries. See dev.sh and see the related commmands.