`<Main>` doesn't really belong in App.js given the html it renders, but there's some additional thing happening with this component that requires it to be here to support tests. This update addresses the extra padding that it creates by being used at this level. Closes #17 |
||
|---|---|---|
| .github/workflows | ||
| .travis | ||
| config | ||
| profiles | ||
| src | ||
| tools | ||
| .babelrc | ||
| .eslintrc.yml | ||
| .gitignore | ||
| .stylelintrc.json | ||
| .travis.yml | ||
| LICENSE | ||
| package.json | ||
| README.md | ||
image-builder-frontend
Development
- Clone the following repositories:
Optional: https://github.com/osbuild/osbuild-composer
-
Setting up the proxy
Choose a runner (podman or docker), and point the SPANDX_CONFIG variable to profile/local-frontend-and-api-with-identity.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-and-api-with-identity.js sudo -E insights-proxy/scripts/run.sh -
Starting up osbuild-composer-cloud
Make sure osbuild-composer is installed and osbuild-composer-cloud is enabled:
sudo systemctl enable --now osbuild-composer-cloud.socketStart a remote worker like so:
sudo systemctl enable --now osbuild-remote-worker@localhost:8704 -
Starting up image-builder In the image-builder checkout directory
make build OSBUILD_SERVICE="http://127.0.0.1:8703/" ./image-builder -
Starting up image-builder-frontend
In the image-builder-frontend checkout direcotry
npm install npm start
The UI should be running on https://prod.foo.redhat.com:1337/apps/image-builder/landing, the api (image-builder) on https://prod.foo.redhat.com:1337/api/image-builder/v1/openapi.json