Go to file
Tom Gallacher 7d60252a05 circleci: overriding inferred commands.
Tests and install were being ran twice
2016-10-27 16:26:41 +01:00
bin ci: no need to re-apply stash 2016-10-27 12:35:37 +01:00
cloudapi-graphql tests: Makefile is now the main truth, away from npm 2016-10-27 16:15:44 +01:00
frontend tests: Makefile is now the main truth, away from npm 2016-10-27 16:15:44 +01:00
spikes css-modules & aphrodite examples 2016-10-19 15:04:20 +01:00
ui lint: Fixing lint errors 2016-10-27 16:26:26 +01:00
.gitignore ignore credentials.json 2016-10-20 14:11:40 +01:00
circle.yml circleci: overriding inferred commands. 2016-10-27 16:26:41 +01:00
CONTRIBUTING.md Introducing a contribution guide 2016-10-14 12:25:04 +01:00
docker-compose.yml docker-compose: only download the needed tags 2016-10-24 17:35:35 +01:00
local-compose.yml backend: Moving backend into frontend 2016-10-24 16:31:05 +01:00
Makefile make: Ignore error when running make 2016-10-27 16:15:44 +01:00
package.json tests: Makefile is now the main truth, away from npm 2016-10-27 16:15:44 +01:00
README.md readme: updating docs 2016-10-25 17:51:20 +01:00
yarn.lock tests: Makefile is now the main truth, away from npm 2016-10-27 16:15:44 +01:00

Joyent Dashboard

Installation

To run the stack locally:

docker-compose -f local-compose.yml up -d

And then navigate to https://localhost:8000.

Development

If you would like to contribute to the project, the recommended way to setup is to insure that you have docker installed, and optionally have a triton account and profile setup using the triton tool.

Currently requires yarn for installing dependencies.

make || make install

Then to run each individual component locally (subject to change).

Project Management

This project is using Github Projects for organisation and development of the Joyent Dashboard.

Repository Layout

Currently we are using this repository as a monolithic catch-all for all project communication, development and designs. We will also include multiple PoC's of various bits of functionality from UI's prototypes to API development.

.
├── frontend
├── ui
├── cloudapi-graphql
└── spikes

cloudapi-graphql

An implementation of the Joyent CloudAPI in GraphQL.

frontend

The client side code with a dev-server, this also includes the production server for the meantime, however we are looking at moving towards a deployment of the build artifacts to manta, and another server to host these assets.

ui

Code for the reusable UI framework.

spikes

Implementation examples from spikes, this directory is experimental and is likely broken.