Go to file
sevenzing cc9c155391
Running Nginx with the ava client in the same docker container
2020-07-19 14:17:48 +03:00
.ci removing set x 2020-06-21 17:09:12 -03:00
.github ansible: Add service_playbook.yml & supporting roles 2020-05-09 23:01:23 +01:00
api fix typo causing infinite loop 2020-06-30 17:13:06 -04:00
cache add minimumCacheSize 2020-06-16 16:11:21 -04:00
chains grab context of chain before calling isBootstrapped() to avoid race condition 2020-06-29 18:07:48 -04:00
database only downsize underlying arrays if they're much too large 2020-06-23 16:44:02 -04:00
genesis reverted breaking changes 2020-06-18 01:45:58 -04:00
ids Merge branch 'denali' into limit-outstanding-requests 2020-06-23 19:19:19 -04:00
main added error reporting to nat.Map 2020-06-24 11:41:22 -04:00
nat Merge pull request #123 from ava-labs/nat-errors 2020-06-24 12:39:37 -04:00
network only log to info based on the beacons 2020-06-23 20:58:35 -04:00
node address PR comments 2020-07-03 13:45:54 -04:00
scripts Merge branch 'master' into ansible-service 2020-07-13 14:05:55 -05:00
snow nit cleanup 2020-07-03 17:07:39 -04:00
staking make staking cert/key read-only 2020-06-22 10:53:10 -04:00
utils move codec to utils 2020-06-15 13:20:30 -04:00
version version constants 2020-05-25 23:09:31 -04:00
vms Merge branch 'denali' into c-chain-next 2020-06-23 20:12:17 -04:00
xputtest move codec to utils 2020-06-15 13:20:30 -04:00
.codecov.yml init repo 2020-03-10 15:20:34 -04:00
.dockerignore Running Nginx with the ava client in the same docker container 2020-07-19 14:17:48 +03:00
.editorconfig Standardise newline and trailing whitespace conventions 2020-05-11 20:31:59 +01:00
.env.example Running Nginx with the ava client in the same docker container 2020-07-19 14:17:48 +03:00
.gitignore Running Nginx with the ava client in the same docker container 2020-07-19 14:17:48 +03:00
.travis.yml re-enabling osx 2020-06-21 16:13:59 -03:00
Dockerfile Running Nginx with the ava client in the same docker container 2020-07-19 14:17:48 +03:00
LICENSE init repo 2020-03-10 15:20:34 -04:00
README.md updated readme 2020-05-25 23:14:37 -04:00
docker-compose.yml Running Nginx with the ava client in the same docker container 2020-07-19 14:17:48 +03:00
entrypoint.sh Running Nginx with the ava client in the same docker container 2020-07-19 14:17:48 +03:00
go.mod merged 2020-06-23 20:20:57 -04:00
go.sum merged 2020-06-23 20:20:57 -04:00
nginx.template Running Nginx with the ava client in the same docker container 2020-07-19 14:17:48 +03:00

README.md

Gecko

Installation

AVA is an incredibly lightweight protocol, so the minimum computer requirements are quite modest.

  • Hardware: 2 GHz or faster CPU, 3 GB RAM, 250 MB hard disk.
  • OS: Ubuntu >= 18.04 or Mac OS X >= Catalina.
  • Software: Go version >= 1.13.X and set up $GOPATH.
  • Network: IPv4 or IPv6 network connection, with an open public port.

Native Install

Clone the Gecko repository:

go get -v -d github.com/ava-labs/gecko/...
cd $GOPATH/src/github.com/ava-labs/gecko

Building the Gecko Executable

Build Gecko using the build script:

./scripts/build.sh

The Gecko binary, named ava, is in the build directory.

Docker Install

  • Make sure you have docker installed on your machine (so commands like docker run etc. are available).
  • Build the docker image of latest gecko branch by scripts/build_image.sh.
  • Check the built image by docker image ls, you should see some image tagged gecko-xxxxxxxx, where xxxxxxxx is the commit id of the Gecko source it was built from.
  • Test Gecko by docker run -ti -p 9650:9650 -p 9651:9651 gecko-xxxxxxxx /gecko/build/ava --public-ip=127.0.0.1 --snow-sample-size=1 --snow-quorum-size=1 --staking-tls-enabled=false. (For a production deployment, you may want to extend the docker image with required credentials for staking and TLS.)

Running Gecko and Creating a Local Test Network

To create your own local test network, run:

./build/ava --public-ip=127.0.0.1 --snow-sample-size=1 --snow-quorum-size=1 --staking-tls-enabled=false

This launches an AVA network with one node.

You should see some pretty ASCII art and log messages. You may see a few warnings. These are OK.

You can use Ctrl + C to kill the node.

If you want to specify your log level. You should set --log-level to one of the following values, in decreasing order of logging.

  • --log-level=verbo
  • --log-level=debug
  • --log-level=info
  • --log-level=warn
  • --log-level=error
  • --log-level=fatal
  • --log-level=off