This is the home of the web user-interface for Galasa.
- Clone the repository
- Run the
setup-locally.shscript
- Run the
build-locally.shscript
- Run the
run-locally.shscript
If you would like to run the web UI locally and have it connect to an existing Galasa service's backend, perform the following steps:
- Make sure that you have access to an existing Galasa service and are able to log in to its web UI - if you do not have access, contact your Galasa service administrator
- Navigate to the remote Galasa service's webui and create a new personal access token. The personal access token value will be in the form
<string>:<string>- note this token value down - Set the
GALASA_DEV_TOKENenvironment variable, either in the terminal that you will use to start the webui or inside a new.env.development.localfile, to be the personal access token that was just created- For example, if your access token was
my:token, you could create a new.env.development.localfile next to the existing.envfile and then set the environment variable in the file likeGALASA_DEV_TOKEN="my:token"
- For example, if your access token was
- Set the
GALASA_API_SERVER_URLenvironment variable, either in the same terminal that you will use to start the webui or inside the.env.development.localfile that you may have created in step 3, to be the URL of the remote Galasa service's API server- For example, if the Galasa service's webui URL was
https://my-galasa-service.dev, then the API server URL would behttps://my-galasa-service.dev/api(added/apito the end of the URL)
- For example, if the Galasa service's webui URL was
- Start the webui locally
See the contributions.md file for terms and instructions.