pendulum-chain / spacewalk-testing-service

GNU General Public License v3.0
0 stars 0 forks source link

Deploy spacewalk-testing-service on our infrastructure #3

Closed ebma closed 10 months ago

ebma commented 11 months ago

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.

Optional

Deployment

# Clone the repository (main branch)
git clone https://github.com/pendulum-chain/spacewalk-testing-service.git

# Change directories
cd spacewalk-testing-service

# Install the dependencies
npm install

# Build the files
npm run build

# Run the service
node ./dist/server.js
ebma commented 11 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.

zoveress commented 10 months ago

@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.

ebma commented 10 months ago

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.