The origin-web-console repository is the web-based management interface for OpenShift Origin, an open-source container application platform. Written primarily in JavaScript, it provides a graphical user interface for cluster administration, resource management, and application deployment within OpenShift environments. The console serves as the primary dashboard through which users interact with Kubernetes-based infrastructure and manage containerized applications.
The repository is built on AngularJS and the Hawt.io framework, leveraging established web technologies for its user interface layer. The architecture supports custom context roots, allowing the console to be deployed at various URL paths within an OpenShift installation. All console URLs are designed to be relative rather than absolute, enabling flexible deployment scenarios where the console's base path may be injected at runtime into the index.html file.
Development setup requires Node.js, npm, and build tools including grunt-cli and bower. The repository includes comprehensive development documentation and automation scripts for dependency installation and building. Developers can launch a local instance using the grunt serve command, which watches for asset changes and opens the console at localhost:9000. The setup process includes configuration for self-signed certificates and browser-specific certificate handling. The repository provides debug logging capabilities through OpenShift-specific loggers for main functionality and authentication flows, with configurable log levels ranging from OFF to ERROR.
The console is split across three repositories to manage complexity and dependencies. The origin-web-common and origin-web-catalog repositories serve as dependency modules that can be linked during development using bower link functionality. This modular approach allows developers to work on dependent repositories while testing changes within the main console codebase.
Testing infrastructure includes both unit tests and integration tests, with end-to-end tests requiring Firefox. The build process generates distribution files that are eventually compiled into the OpenShift binary through a separate build-go.sh script. Production builds require running hack/install-deps.sh followed by grunt build, with subsequent integration into the origin repository's build system.
The console provides extension points for customization through two primary mechanisms. Navigation extensions can be added to project-level tabs using the hawtio-core-navigation library, with examples of tab registration visible in app/scripts/app.js. Additional content injection is supported through the hawtio-extension-service, though extension hooks are not yet fully implemented in the current codebase.
Code contribution standards are enforced through editor configuration files, requiring soft-tabs with two-space indentation, UTF-8 encoding, and trailing whitespace removal. Pull requests must include updated dist files, passing test suites, and squashed commits. The repository maintains strict consistency checks on built distribution files to prevent Jenkins build failures from uncommitted changes.
GitGenius activity data indicates this repository maintains active contributor overlap with major projects including Microsoft's VSCode, the Rust language project, and Microsoft's TypeScript repository, suggesting involvement from developers working across multiple significant open-source ecosystems. The repository is classified across multiple domains including cloud platform management, Kubernetes integration, cluster administration, and container orchestration, reflecting its comprehensive role in the OpenShift ecosystem.
