staging env
Staging environment for creature smart contracts
Staging environmnent is re-started after every commit to devel branch.
The envionment starts with all the developed contracts deployed. It also starts with pre-defined stacks accounts topped up, as specified in Devnet.toml.
Staging environment endpoints
Stacks blockchain node REST API: https://testnet.wannabe.games/api
Stacks explorer app: https://testnet.wannabe.games/stacks
Requirements
Staging environment should be Linux machine with same requirements as for devnet and clarinet.
In addition you need tmux, git and ssh installed.
Deployment automation
Staging machine is expected to be able to poll creature-racer-stacks git repository.
There is a script called staging_deploy.sh, which will check if there are any changes upstream and, if that's the case, will fetch the changes and restart the environment. The script can be run by hand or be executed periodically from cron.
Bootstrapping the environment
Be sure to setup SSH key infrastructure, so that the local working account can poll github repository. For the automation to work, the private key should not be password-protected.
Clone the creature-racer-stacks repository and checkout the branch that you want the staging env to track (i.e. devel).
Launch
ci/staging_deploy.sh. This will bootsrap the environment in a detached tmux session.ci/staging_deploy.shcan be run periodically from cron to update and restart the environment in case of upstream changes.
Manually interacting with environment
To manually interact with the environment you can use tmux ls to identify the staging environment session followed by tmux attach to attach to this session.
The latest version available here
(The content of the page is available for logged-in GitHub users)
Last updated