creative-commoners / dashboard Goto Github PK

The purr cron has always been running on my laptop. Let's move it into the Pi.

Purr config: https://silverstripe.atlassian.net/wiki/spaces/CC/pages/343801972/CC+s+purr+configuration

Needs a GitHub access token.

Add to config.yml:

• firesphere/silverstripe-boostrapmfa
• silverstripe/silvertripe-login-fomrs
• silverstripe/silverstripe-u2f-authenticator
• elliot-sawyer/totp-authenticator
• silverstripe/silverstripe-ckan-registry
• silverstripe/silverstripe-mfa

Note this will probably require some CSS to have all repos presented on one screen without scrolling

I broke something when I removed the travis.rb library, in progress/yellow builds are now showing as red.

• Get Ops to create a hostname e.g. product-dashboard for local network access
• Stop smashing on a cron at e.g. 6pm
• Sleep screen at e.g. 6pm
• Unsleep screen e.g. 8.30am
• Start smashing on a cron at e.g. 8.30am
• Remove mouse pointer from display
• Cron to run git pull in dashboard repo at e.g. 8.25am
• Change port from 3030 to 80

It'd be cool to show somehow what the code coverage level is like for each repository, example (arbitrary):

I think codecov.io will provide its definition of what constitutes good coverage levels etc, since that is configurable in its system, and powers its own readme badge colours.

I think the primary focus of the colours should still be indicate the build status, but maybe something like a variable border colour could be used to add some extra context.

cc @sachajudd for thoughts

Example: github.com/silverstripe/silverstripe-security-extensions

It was built once a while back on .org, now lives on .com - the dashboard is showing broken master branch only, which is from the .org repo.

Our code pings the .org API which internally resolves to .com when it should, so it must be using .org with priority for this module. We may be able to change to .com endpoint assuming it works the other way too, but I haven't tried it to find out.

The current logic says "if not green then must have failed" - this is wrong. We maybe need to add a new state for "in progress" instead.