phase2/outrigger-dashboard

Dashboard for Outrigger

outrigger-dashboard's Issues

Add grouping for "Outrigger" containers

While most containers are grouped by docker-compose project, we can create a secondary group based on the label assignment com.dnsdock.image == 'outrigger'.

This would help communicate that the outrigger containers are a bit special, instead of being grouped with the isolated containers which are often less significant.

Improve grouping of sync containers

Sync containers currently appear in the unclassified section of the dashboard. This is a bit misleading, as these containers are usually critical pieces of the plumbing of specific projects.

But what can we do to improve this? Two options occur to me.

1. In our most common usage, the sync container is generally "universal" to every locally running instance of the project. Therefore show the sync container in each grouping of containers. (Currently there could be multiple groupings for a single project, by virtue of different docker-compose project label.)
2. Create a category of sync containers. They have some pretty special characteristics anyway and are more likely to be subject to similar oversight and management.

In either case, we may want to modify rig to add a sync container label.

Machine keeps restarting in the loop

I'm trying to setup phase2 outrigger on linux. I made it trough the installation of dnsdock. Compiled rig and I can use it. When I use rig start i get

[INFO] Linux users should use Docker natively for best performance.
[INFO] Please ensure your local Docker setup is compatible with Outrigger.
[INFO] See http://docs.outrigger.sh/getting-started/linux-installation/
[INFO] Launching Dashboard...
b3e88e692bfb5e0bb5c634ecc825b0399a9b4adbc11a333290214783f044141b
[INFO] Outrigger Dashboard is now available at http://dashboard.outrigger.vm
[INFO] Outrigger is ready to use

But I cannot access it on that url

also if i go docker ps in status for dashboard i get Restarting in the loop

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b3e88e692bfb outrigger/dashboard:latest "docker-entrypoint..." 6 seconds ago Restarting (1) Less than a second ago outrigger-dashboard

is that a normal behaviour? What am I missing here?

in logs i get

2017-09-24T08:22:05.208401400Z 2017/09/24 08:22:05 Registering Docker Event Listener....
2017-09-24T08:22:05.208454603Z 2017/09/24 08:22:05 Starting HTTP server listening on port :80
2017-09-24T08:22:05.209048144Z 2017/09/24 08:22:05 Error response from daemon: {"message":"page not found"}

➜ rigtest docker version
Client:
Version: 17.06.2-ce
API version: 1.30
Go version: go1.8.3
Git commit: cec0b72
Built: Tue Sep 5 20:00:17 2017
OS/Arch: linux/amd64

Server:
Version: 17.06.2-ce
API version: 1.30 (minimum version 1.12)
Go version: go1.8.3
Git commit: cec0b72
Built: Tue Sep 5 19:59:11 2017
OS/Arch: linux/amd64
Experimental: false

rig version 1.3.1

Add operations context menu with easily copied commands.

The Dashboard represents an opportunity to help developers bridge from the UI to the command-line by facilitating CLI command construction.

Similar to how Github offers easy buttons to copy clone operations or commit hashes to the clipboard, we could offer easy push-button copy of text to facilitate:

Project Category

• Space delimited list of container names suitable for pasting into a docker stop command.
• docker stop/rm command with all containers in the category.

Individual Container

• Container name suitable for pasting in a docker stop command.
• docker stop command
• docker exec command to "SSH" to the container. Not all container support Bash, so this might be tricky.

Future Directions

Similar to how http://label-schema.org/rc1/ includes some docker commands as label metadata, we could have outrigger container self-declare various operations for running, execing, and so on.

Add cache busting of dashboard's custom script

The build.js file referenced by the main HTML markup of the dashboard contains all the content and custom styling for the dashboard as a Vue.js app. For lack of cache busting, when there are updates to the dashboard it requires extra cache clearing on the part of viewers.

Add some element of cache busting (querystring or otherwise) so new releases more smoothly deliver changes to users.

Since this is only a single file we'd prefer to minimize tooling additions to make this happen. (We do have webpack)