EOS Local provides a really quick way to setup an EOS local network.
EOS local exposes all APIs provided by EOS Costa Rica and other BPs on the TestNet and MainNet.
It allows you to develop your application running the same APIs services you will use in production in your computer.
It has a companion project that serves as a starter boilerplate your dApp. https://github.com/eoscostarica/eos-dapp-boilerplate
EOS Local is a community-driven project led by EOS Costa Rica. We welcome contributions of all sorts. There are many ways to help, from reporting issues, proposing features, improving documentation, contributing code, design/ux proposals, etc.
Table of Contents generated with DocToc
- Architecture
- Technical Specs
- Getting started
- Chain Initialization
- Commands
- Recommended aliases
- Directory Structure
- Services
- Using Cleos on EOS Local
- Frequently Asked Questions
- Contributing
- About EOS Costa Rica
- License
- Contributors
Every service/process runs on a separate container.
You can develop multiple dApps using the same EOS Local Network, sharing testing users and machine resources.
- Virtualized local network with docker.
- Microservices architecture.
- Out-of-box services:
- Nodeos deamon / eosio node.
- HTTP RPC API with history.
- Keosd wallet service.
- GraphQL API for complex data queries.
- Ngnix proxy.
- Services accessible through virtual host names both from host machine and within the docker network.
- Handy scripts for interacting with the local EOS services.
Important Disclaimer: This is a Work in Progress
Basic knowledge about Docker, Docker Compose, EOS and NodeJS is required.
- Video tutorial Docker Containers | Learn Docker Basics in 30 Mins
Global Dependencies
- Docker https://docs.docker.com/install/.
At least 10GB RAM (Docker -> Preferences -> Advanced -> Memory -> 10GB or above)
Execute make setup for:
- Chain initialization.
- Testing Users Creation.
make setuprun chain initialization.make flushstops all services and removes all data.docker-compose startstarts all containers.docker-compose exec [service_name] [bash | sh]open bash or sh in a container.docker-compose stopstops all containers.docker-compose downstops and removes all containers.docker-compose restartrestarts all services.
It is useful to have aliases for the docker ad docker-compose and cleos commands since they are use very often.
alias cleos='docker exec eosio cleos --url http://localhost:8888/'
alias dk='docker'
alias dc='docker-compose'
.
├── docs/ .............................................. documentation files and media
├── contracts/ ......................................... eos smart contracts
├── services/ .......................................... microservices
| ├── graphql/ ....................................... graphql service
| |
| ├── history-api/ ................................... express/swagger history api
| |
| ├── ngnix/ ......................................... nginx service for routing
| |
| ├── mongo/ ......................................... mongodb data
| |
| └── eosio/ ......................................... eos node | nodeos
| ├── utils/ ..................................... service utilities
| ├── config/ .................................... eos node configuration
| ├── scripts/ ................................... chain init scripts
| ├── Dockerfile ................................. service image specification
| └── start.sh ................................... service startup script
|
├── docker-compose.yaml ................................ docker compose for local dev
├── contributing.md .................................... contributing guidelines
├── license ............................................ project license
├── makefile ........................................... make tasks manifest
├── readme.md .......................................... project documentation
└── .editorconfig ...................................... common text editor configs
The eosio node acts as block producer and history api node, this configuration is just for development. It's not recommended to for production. In production it's recommended to devide nodes responsibilities, you may want to configure a dedicate api node that stores you contracts data only or use one of the network block producers node as a service.
The docker image source code can be found at https://github.com/EOSIO/eos/blob/master/Docker/Dockerfile.
Learn more at https://developers.eos.io/eosio-nodeos/docs/
https://developers.eos.io/eosio-nodeos/reference
The eos rpc api is accesible through http://localhost:8888
MongoDB instance for to story hisotry. The eosio::mongo_db_plugin provides archiving of blockchain data into a MongoDB.
https://developers.eos.io/eosio-nodeos/docs/mongo_db_plugin
https://github.com/EOS-BP-Developers/eosio-graphql
https://github.com/CryptoLions/EOS-mongo-history-API
Nginx reverse proxy that allows accesing the services directly on the host machine the wildcard *.esolocal.io that points to 127.0.0.1, therefore as long as you can hit the dns server it will redirect all requests to your machine and nginx-proxy does the internal docker network routing to the right service.
Run ping {whatever}.eoslocal.io to verify.
Optionally you can avoid the round trip and work offline maintaining virtual hosts by manually adding your dns to your hosts file. https://en.wikipedia.org/wiki/Hosts_(file)
See the docker-compose.yml for available virtual hosts for easier access without port shenanigans.
Cleos is a command line tool that interfaces with the API exposed by nodeos. In order to use cleos you will need to have the endpoint (IP address and port number) to a nodeos instance and also configure nodeos to load the 'eosio::chain_api_plugin'. cleos contains documentation for all of its commands.
More at https://developers.eos.io/eosio-nodeos/docs/cleos-overview
EOS Local comes with 2 EOS nodes running in separate docker containers, you can interact with these nodes using cleos in several ways:
You can execute commands on any container from you host machine using the docker-compose exec command.
Eg:
docker exec eosio cleos --url http://localhost:8888/
We recomend using declaring alias on your shell configuration Eg (.bashrc or .zshrc)
alias cleos='docker exec eosio cleos --url http://localhost:8888/'
Notice it uses docker directly thru the container_name insted of docker compose, this allows you to invoke it from any path in your computer, you don't have to be a the root dir of eoslocal.
After you have added those lines to your config you can open a new terminal window and run cleos --help to test.
You can also login into the containers using the following docker-compose command
docker exec eosio bash
That will log you in and you will be able to execute cleos directly within the ubuntu server. Eg.
➜ eos-local git:(master) ✗ docker-compose exec eosio bash
root@b39ffe3c43c0:/opt/eosio/bin# cleos get info
{
"server_version": "f9a3d023",
"chain_id": "cf057bbfb72640471fd910bcb67639c22df9f92470936cddc1ade0e2f2e7dc4f",
"head_block_num": 4900,
"last_irreversible_block_num": 4899,
"last_irreversible_block_id": "000013232f7193f86a4edc59b6aa2b2a8ccd6c2060d24eb0e5c497beb97b76e5",
"head_block_id": "000013249772e5af12592d7d3eeb401276c09f781e3ed76faa75a49f53b481bd",
"head_block_time": "2018-11-05T20:27:45.000",
"head_block_producer": "eosio",
"virtual_block_cpu_limit": 26829884,
"virtual_block_net_limit": 140951435,
"block_cpu_limit": 199900,
"block_net_limit": 1048576,
"server_version_string": "v1.4.1"
}
The primary benefits of containers are efficiency and agility. Containers are orders of magnitude faster to provision, and much lighter-weight to build and define versus methods like omnibus software builds and full Virtual Machine images. Containers in a single OS are also more efficient at resource utilization than running a Hypervisor and guest OSs.
Efficiency and agility are good for everyone, but they become game-changers at scale.
It also gives the ability to run distint versions of the different services like EOSIO on your laptop without conflicts.
Containers offer a logical packaging mechanism in which applications can be abstracted from the environment in which they actually run. This decoupling allows container-based applications to be deployed easily and consistently, regardless of whether the target environment is a private data center, the public cloud, or even a developer’s personal laptop. Containerization provides a clean separation of concerns, as developers focus on their application logic and dependencies, while IT operations teams can focus on deployment and management without bothering with application details such as specific software versions and configurations specific to the app.
For those coming from virtualized environments, containers are often compared with virtual machines (VMs). You might already be familiar with VMs: a guest operating system such as Linux or Windows runs on top of a host operating system with virtualized access to the underlying hardware. Like virtual machines, containers allow you to package your application together with libraries and other dependencies, providing isolated environments for running your software services. As you’ll see below however, the similarities end here as containers offer a far more lightweight unit for developers and IT Ops teams to work with, carrying a myriad of benefits.
Learn more at https://cloud.google.com/containers/
We use a Kanban-style board. That's were we prioritize the work. Go to Project Board.
The main communication channels are github issues and EOS Costa Rica's Discord server. Feel to join and ask as many questions you may have.
Our weekly sync call is every Monday 1:00 AM UTC. meet.eoscostarica.io.
Contributing Guidelines https://developers.eoscostarica.io/docs/open-source-guidelines.
Please report bugs big and small by opening an issue
We challenge ourselves to provide the EOS platform with a strong geographical and political diversity by running the most robust EOS Block Producer possible from Costa Rica; We pledge to leverage our talent, experience, and sustainable internet resources to meet such an important challenge.
EOS Costa Rica supports the EOS.io community by maintaining and contributing to open source initiatives, meetups and workshops.
MIT © EOS Costa Rica
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!