Automation Analytics provides data analytics for Ansible Tower that provides visualization and insight into how automation is used in your organization.
npm ci
- install dependencies from the lockfile- get the backend running: automation analytics backend
npm start
- starts standalone: webpack serves the files alongside with insights, rbac and keycloak.- Go to
http://localhost:1337/beta/ansible/automation-analytics
and use the admin/admin credentials to login.
When you have M1 Mac:
npm ci
- install dependencies from the lockfile- get the backend running: automation analytics backend
- build keycloak locally
VERSION=16.1.1
git clone [email protected]:keycloak/keycloak-containers.git
cd keycloak-containers/server
git checkout $VERSION
docker build -t "jboss/keycloak:MAGIC" .
- run keycloak locally
docker run -p 4001:8080 -e KEYCLOAK_USER=admin -e KEYCLOAK_PASSWORD=admin -e DB_VENDOR=h2 -v `pwd`/node_modules/@redhat-cloud-services/frontend-components-config-utilities/standalone/services/default/keycloak/realm_export.json:/tmp/realm_export.json jboss/keycloak:MAGIC -Dkeycloak.migration.action=import -Dkeycloak.migration.provider=singleFile -Dkeycloak.migration.file=/tmp/realm_export.json -Dkeycloak.migration.strategy=OVERWRITE_EXISTING
- in
node_modules/@redhat-cloud-services/frontend-components-config-utilities/standalone/services/rbac.js
changeredis:5.0.4
toredis:latest
- in
node_modules/@redhat-cloud-services/frontend-components-config-utilities/standalone/services/default/chrome.js
change wholeargs
for keycloak tonode
(must be a container that will build and run without errors and not consume port 4001) npm run start
- Go to
http://localhost:1337/beta/ansible/automation-analytics
and use the admin/admin credentials to login.
Note that after running npm install
or npm ci
changes in node_modules
will be lost. You can use this script to do it
sed -i.bak -e 's/redis:5.0.4/redis:latest/' node_modules/@redhat-cloud-services/frontend-components-config-utilities/standalone/services/rbac.js
sed -i.bak -e '/-p.*keycloakPort.*8080/d' -e '/"-[eD]/d' -e '/-v /d' -e 's/jboss\/keycloak/node/' node_modules/@redhat-cloud-services/frontend-components-config-utilities/standalone/services/default/chrome.js
npm ci
- install dependencies from the lockfilenpm start --env=stage
- starts local frontend while proxying all the request to the stage environment.- Follow the link the proxy outputs to the terminal - this is different from env to env. You need valid credentials for the environment you are running against to be able to log in
npm ci
- install dependencies from the lockfilenpm start --env=eph --eph_id=YOUR_EPH_ID
- starts local frontend while proxying all the request to the eph environment.- Follow the link the proxy outputs to the terminal - this is different from env to env. You need valid credentials for the environment you are running against to be able to log in
npm run lint
- runs eslintnpm run test
- runs jestnpm run test:watch
- runs jest in watch modenpm run verify
- will run linters and tests
- The Platform team is using Travis to deploy the application
- The Platform team will help you set up the Travis instance if this is the route you are wanting to take
- any push to the
devel
branch will deploy tostage
,stage/beta
,prod/beta
- any push to the
prod-stable
branch will deploy toprod
- If a PR is accepted and merged,
devel
will be rebuilt and will deploy tostage
,stage/beta
,prod/beta