In order to access the https://[env].foo.redhat.com in your browser, you have to add entries to your /etc/hosts file. This is a one-time setup that has to be done only once (unless you modify hosts) on each machine.
To setup the hosts file run following command:
Add the below to your /etc/hosts file:
127.0.0.1 prod.foo.redhat.com
127.0.0.1 stage.foo.redhat.com
A recommended tool to install is react developer tools, which is installed as a plugin for your favourite browser.
Useful when trying your service config changes before commit to chrome-service-backend repository.
Clone repositories and use Alejandro's branch:
git clone https://github.com/RedHatInsights/chrome-service-backend.git -o upstream
cd chrome-service-backendRun the server in the foreground:
make dev-static port=9999The below will be necessary to deploy on the dev cluster.
- Install nvm by:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash. - Config node 18 by:
nvm install 18; nvm use 18. - Run
cp -vf config/bonfire.example.yaml config/bonfire.yaml. - Update the
config/bonfire.yamlfile by following the TODO placeholders. - Run
mkdir -p secrets/ephemeral && cp -vf scripts/mk/private.example.mk secrets/private.mk. - Update the
secrets/private.mkfile by following the TODO placeholders. - Generate app-secret by:
${PATH_TO_IDMSVC_BACKEND_REPO}/scripts/gen-app-secret.py secrets/ephemeral/app-secret.yaml.
Now you can deploy into dev cluster by make ephemeral-build-deploy.
-
make runto start the server. -
Open the idmsvc app in your browser.
See: Contributing.
- Run unit tests by
make test. - Run linter by
make lint.
Update git submodule and regenerate API with make update-api.
Generate src/Api from the openapi specification by running make generate-api.