- Make sure you have Node.js version >= 16 installed
- Run script to patch your
/etc/hosts
- Make sure you are using Red Hat proxy
- Install dependencies with
npm install
- Run development server with
npm run start:proxy:beta
- Local version of the app will be available at https://stage.foo.redhat.com:1337/beta/insights/advisor/
In case you want to use the stable environment instead of beta you can run the app with npm run start:proxy
and access it from https://stage.foo.redhat.com:1337/insights/advisor/. Usually there is no difference between these two environments unless there is a large feature in progress which is hidden behind isBeta
flag.
Travis is used to test the build for this code.
npm run test
will run tests.npm run lint
will run all linters.
Any push to the following branches will trigger a build in insights-advisor-frontend-build repository which will deploy to corresponding environment. Travis is used to deploy the application.
Push to branch in this repo | Updated branch in build repo | Environment | Available at |
---|---|---|---|
master | stage-beta | stage beta | https://console.stage.redhat.com/beta |
master-stable | stage-stable | stage stable | https://console.stage.redhat.com |
prod-beta | prod-beta | production beta | https://console.redhat.com/beta |
prod-stable | prod-stable | production stable | https://console.redhat.com |
Translation keys are saved in messages.js
.
Each time you add a new translation keys you need to run npm run translations
, which will automatically generate JSON files for every language into locales/
folder based on the entries in the messages.js
.
There are two ways to use translated strings:
- With
intl.formatMessage(messages.messageId)
- With
<FormattedMessage {...messages.messageId}/>
This project uses Patternfly React.
This app imports components from Insights Front-end Components library. ESI tags are used to import Insights Chrome which takes care of the header, sidebar, and footer.