Closed ebma closed 10 months ago
@pendulum-chain/product this is the follow-up ticket for #1. The code is ready but we now need to deploy the service on our infrastructure.
@ebma can you provide some dummy settings please for the environment variables. Problem is that I need to test them somehow and I do not want production setting stored in the docker image.
For the Stellar secrets you can use SA2KUMLX3ANG2ZXZBNXZURCT5477K5BAAOVOWMASX2ZFGLO4QWQGYGY7
, for the substrate secret fit gap engage unusual drift energy erupt usage crystal panic speed film
. For the slack token I don't really have a dummy value. You can just use a dummy string like "xxx" as we don't do any regex checking of that token.
We want to deploy our testing service to a server so that it can run 24/7.
The service should be reachable at a user-friendly URL, e.g.
https://spacewalk-testing.pendulumchain.tech
. The service exposes just one route/status
. This route serves GET requests only.How to build and run
Prerequisites
The server needs to have Node.js installed.
Environment variables
We also need to define the following environment variables. They can be put into a local
.env
file, supplied when running the last command (ie.SLACK_WEB_HOOK_TOKEN="xxx" ... node ./dist/server.js
) or sourced into the shell.The first 4 values are shared in 1password.
SLACK_WEB_HOOK_TOKEN
- Slack web hook token for error reporting.STELLAR_ACCOUNT_SECRET_MAINNET
- Stellar account secret for mainnet.STELLAR_ACCOUNT_SECRET_TESTNET
- Stellar account secret for testnet.SUBSTRATE_SECRET_PHRASE
- The substrate account mnemonic phrase.PORT
- Port to run the service on. Defaults to5000
.Optional
RATE_LIMIT_WINDOW_MINUTES
- Rate limit window in minutes. Defaults to1
.RATE_LIMIT_MAX_REQUESTS
- Max requests per rate limit window. Defaults to60
.RATE_LIMIT_NUMBER_OF_PROXIES
- Allowed number of proxies in front of the service. Defaults to1
.Deployment