Skip to content

rhamilto/console

Repository files navigation

bridge

control center for kubernetes clusters

Local non-Docker Build

  1. Build the backend ./build
  2. Build the frontend ./build-web

Backend binaries are generated in /bin
Frontend build assets are generated in /frontend/public/dist

Docker Compiling / Building

Compile all Code using Docker

./build-docker

Compile & Build Docker Image Locally

./build-docker
docker build .

Compile, Build, & Push Docker Image

Must set env vars DOCKER_USER and DOCKER_PASSWORD or have a valid .dockercfg file.

./build-docker-push

Hacking

Develop on CoreOS (useful for fleet & etcd access):

  1. Add your .dockercfg using a quay robot account with access to quay.io/coreosinc repos
    (or set env variables for auth DOCKER_USER and DOCKER_PASSWORD).
  2. For first time setup, run: ./dev-setup
  3. View output of dev servers with sudo journalctl -u devweb -lf and sudo journalctl -u devgrunt -lf

Adding Dependency Libraries

Add Frontend dependencies:

  1. bower install the dependency
  2. from ./frontend run gulp deps
  3. add and commit generated deps.js and deps.min.js files in ./frontend/public/lib/

Add Backend dependencies:

  1. go get ... as usual
  2. run godep save -r ./...

Update existing backend dependencies:

  1. go get -u foo/bar as usual
  2. godep update foo/bar

If changes are made to the schema/v1.json file you must:

  1. Rebuild the bindings by running: schema/generator
  2. Rewrite go dependencies: godep save -r ./...

Dependencies

  • go, nodejs (or just docker)

About

OpenShift Cluster Console UI

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • TypeScript 85.1%
  • Go 4.5%
  • Gherkin 4.3%
  • JavaScript 3.8%
  • SCSS 2.1%
  • Shell 0.2%