886bd768dc
This integrates all the Image Builder components needed by the cloud.redhat.com frontend and allows them to be developed and run locally using `docker compose`. This should make it simple to make patches across the different components and develop them in tandem. Thanks to Achilleas Koutsou for the initial idea and implementation in osbuild-composer. Signed-off-by: Tom Gundersen <teg@jklm.no>
38 lines
1.1 KiB
Markdown
38 lines
1.1 KiB
Markdown
# image-builder-frontend
|
|
|
|
## Frontend Development
|
|
|
|
To develop the frontend you can use a proxy to run image-builder-frontend locally
|
|
against the chrome and backend at cloud.redhat.com.
|
|
|
|
1. Clone the insights proxy: https://github.com/RedHatInsights/insights-proxy
|
|
|
|
2. Setting up the proxy
|
|
|
|
Choose a runner (podman or docker), and point the SPANDX_CONFIG variable to
|
|
`profile/local-frontend.js` included in image-builder-frontend.
|
|
|
|
```
|
|
sudo insights-proxy/scripts/patch-etc-hosts.sh
|
|
export RUNNER="podman"
|
|
export SPANDX_CONFIG=$PATH_TO/image-builder-frontend/profiles/local-frontend.js
|
|
sudo -E insights-proxy/scripts/run.sh
|
|
```
|
|
|
|
3. Starting up image-builder-frontend
|
|
|
|
In the image-builder-frontend checkout directory
|
|
|
|
```
|
|
npm install
|
|
npm start
|
|
```
|
|
|
|
The UI should be running on
|
|
https://prod.foo.redhat.com:1337/apps/image-builder/landing.
|
|
|
|
## Backend Development
|
|
|
|
To develop both the frontend and the backend you can again use the proxy to run both the
|
|
frontend and backend locally against the chrome at cloud.redhat.com. For instructions
|
|
see [devel/README.md](devel/README.md).
|