The Giant Swarm web user interface. It lets users:
- View and manage clusters
- Install and manage applications from an app catalog
- Manage their account
- Add / remove organizations
- Add / remove members from organizations
- Learn how to get started with their kubernetes clusters by following a guide
Happa is intended to be deployed to Giant Swarm management clusters and acts as a client to the Giant Swarm API.
Happa is a single page JavaScript application using React+Redux and runs in modern browsers.
To run happa locally, you need:
Install dependencies:
yarn install
Some warnings regarding unmatched dependency versions are expected and can be ignored.
Then, to bring up Happa connected to an installation, you need to have a kubectl context that points to the installation's management cluster. You also need to have get permissions for the happa-configmap ConfigMap, in the giantswarm namespace.
You can log into the installation's management cluster using the kubectl gs plugin. Here's how you would start Happa after using the plugin to log into the gauss installation:
HAPPA_KUBECTL_CONTEXT=gs-gauss yarn start
Execute the test suite using
yarn test
Tagged releases are continuously deployed to all installations, both test and production. For details see Release.md
We are maintaining a Storybook showcasing more and more of our UI components.
Use environment variables or a configuration file to adjust the behaviour of the application in production.
These configuration values affect the config object in index.html (which is
created from index.ejs).
A configuration script (prepare.ts) applies the values from the configuration values
to index.html by templating index.ejs and creating the index.html file. This way Happa remains a fully static website
that can be served by nginx.
In development, these configuration values are applied using the ConfigurationPlugin via webpack, which generates index.html.
╔═════════╗ ╔══════════╗ ╔═══════════╗ ╔═════════════════╗
║ Actions ║──────>║ Reducers ║──────>║ Store ║──────>║ View Components ║
╚═════════╝ ╚══════════╝ ╚═══════════╝ ╚═════════════════╝
^ │
└───────────────────────────────────────────────────────────┘
Components should only emit actions.
Reducers listen for actions and emit a new state.
The view listens for changes to the state and renders.
By following these guidelines we should get some benefits in keeping component logic focused on rendering, and not on doing the actual work of manipulating state.
Happa uses a custom icon pack which we can manage at https://fortawesome.com Login details are in keypass, search for 'fortawesome'. The line
<script src="https://use.fonticons.com/d940f7eb.js"></script>in src/index.ejs is what includes the fonts for us.
More information about our font kit and how to use it can be found here: https://fortawesome.com/kits/d940f7eb/docs
Renovate is configured for this repository to automatically create pull requests (PRs) that update our dependencies and to request reviews from the relevant teams/individuals. Reviewers can be configured in the CODEOWNERS file, and more information regarding Renovate configurations can be found here.
Happa's code style is determined by prettier. There is a pre-commit hook enforcing that
the coding style rules are met. A CI step will also avoid building any code that does not
match expectations, which then surfaces in the pull request checks in Github.
You can run prettier on the whole codebase using yarn prettier.
We use the following config params:
--jsx-single-quote--single-quote--trailing-comma es5
To avoid pushing code that will fail the CI due to codestyle issues, we've added a pre-commit hook using husky.
This runs before every commit, and it will not let commits go through if the tsc, eslint, or prettier checks have not passed.