Working with multiple environments

Writing Contracts Building Clients Github

Search…

Motivation
In a standard workflow, the first steps of development will be facing a locally running Gamma server. This server runs multiple nodes in-memory on your local machine.
In later stages of the development process, the contract should also be tested on a test net. Since the test net is external, the HTTP endpoints used will have to change.
To make this process easier, Gamma CLI supports multiple environments with an optional config file.
Gamma config JSON
To configure multiple environments create a file named orbs-gamma-config.json in the local directory, with the following format
orbs-gamma-config.json
1
{
2
  "Environments": {
3
    "local": {
4
      "VirtualChain": 42,
5
      "Endpoints": ["localhost"]
6
    },
7
    "testnet1": {
8
      "VirtualChain": 90043,
9
      "Endpoints": ["http://192.168.1.1", "http://192.168.2.2:8080"]
10
    },
11
    "testnet2": {
12
      "VirtualChain": 3007,
13
      "Endpoints": ["http://10.1.1.122", "https://node-example.com", "http://another.io:8081"]
14
    }
15
  }
16
}
Copied!
If a config file does not exist, the default environment is "local" with virtual chain 42 and the endpoint "localhost"
Choosing environment in Gamma CLI
You can choose the active environment by passing the -env command line argument to every command. 
For example, to work with environment testnet2
1
gamma-cli send-tx transfer.json -signer user1 -env testnet2
Copied!

Gamma in Depth - Previous

Reading Logs from Contracts

Next - Gamma in Depth

Upgrading to latest versions

Last modified 2yr ago

Copy link

Contents

Motivation

Gamma config JSON

Choosing environment in Gamma CLI