Make sure that node and yarn are installed on your system. The minimum versions for each are listed in package.json.
Run the following commands (in the deck directory) to get all dependencies installed in deck and to start the server:
yarnyarn modulesyarn start
The app will start up on localhost:9000.
When editing core or any other cloud provider package, please run the following in that folder
yarn dev
If your local dev setup ends up in a corrupt state with missing npm modules, please run yarn fixup from deck and that
should reset your state.
Environment variables can be used to configure application behavior. The following lists those variables and their possible values:
AUTHenable/disable authentication (default is disabled, enable by settingAUTH=enabled).TIMEZONEset the default timezone (default is 'America/Los_Angeles' - see http://momentjs.com/timezone/docs/#/data-utilities/ for options)DECK_CERTenable SSL (set to the fully qualified path to cert file, andDECK_KEYmust be set to the fully qualified path to the key file)
The following external resources can be specified with environment variables:
API_HOSToverrides the default Spinnaker API host.AUTH_ENABLEDdetermines whether Deck will attempt to authenticate users via Gate.
For example, API_HOST=http://spinnaker.prod.netflix.net yarn start will run Deck with http://spinnaker.prod.netflix.net as the API host.
To run the tests within the application, run yarn test.
Developing things locally? You may want to run gate locally (which runs on port 8084) as well. Gate is the service that hosts the spinnaker REST API. Then run deck like this:
API_HOST=http://localhost:8084 yarn start
To build the application, run yarn modules && yarn build.
The built application lives in build/.
the core package is using graphql queries and mutation to interact with the backend (currently, only the managed components).
To generate the TS types and the Apollo hooks, run yarn graphql:generate from core.
It's a work in progress, but please try to follow the conventions here.
It's certainly doable - we're in the middle of some significant changes to our build process, which should make it easier. For now, you can look at the all modules to get an idea how we are customizing Deck internally. Expect a lot of this to change, though, as we figure out better, cleaner hooks and integration points. And we're happy to provide new integration points (or accept pull requests) following those existing conventions if you need an integration point that doesn't already exist.
Interested in sharing feedback on Spinnaker's UI or contributing to Deck? Please join us at the Spinnaker UI SIG!