API URLs

Now there are several endpoints as below:

GET /api/services.json
GET /api/services/${id}.json
GET /api/roles.json
GET /api/roles/${id}.json
GET /api/hosts.json
GET /api/hosts/${id}.json
GET /api/services/${service}/(roles|hosts).json
GET /api/services/${service}/roles/${role}/hosts.json

I'm thinking of only URLs for retrieval so far. Create/Update/Delete APIs are also needed?

Authentication

See #29.

I decided to adopt API token-based strategy.

(service/role/host).descriptionをmarkdownで書いて、表示する。

Now datetime is shown as UTC. How can I show it along with visitor's time zone?

Avoid methodful models and extract methods to roles.

There's already https://github.com/mylesmegyesi/hyperion-ruby

Needs bootstrap-nized formbuilder.

When #26 is closed, then API client library will be needed. It should have just sufficient functions for Triglav's API. Once API's spec is fixed, it'll be uploaded onto rubygems.org.

• Each users have their own API token.
• Access under /api must be authenticated by the token
  • It should authenticate also by cookie for convenience
• API token should be able to be updated by user.

eg) http://triglav-kentaro.sqale.jp/api.json

#41

@KitaitiMakoto
It works fine on your environment?

サービスに属するホスト一覧のページに Munin のグラフが表示されますが、 daily だけではなく weekly/monthly のグラフを一覧で眺めたいことがあるので、切り替えボタンが欲しいです。

I think Cells is a symmetrical thing against DCI's Context. While we inject Roles into models along with some Contexts when we create/update/delete resources, we avoid methodful models and extract the methods to appropriate place when we retrieve and render resources. That is Cells.

Munin's URLs (example):

• index page: http://munin.ping.uio.no/ping.uio.no/aquarius.ping.uio.no/index.html
• graph image: http://munin.ping.uio.no/ping.uio.no/aquarius.ping.uio.no/load-day.png

Whose rule seems to be:

• index page: http://munin-host/#{service}/#{host}/index.html
• graph image: http://munin-host/#{service}/#{host}/#{type}-{day,week,month,year}.png

If Hyperion just support to set munin's URL, it can include monitoring graphs along with the URL rules.

It's clunky Services is translated into サービスs...

When Settings.github.organization is not set, we regard the setting as "free member mode", that is, we don't need login users to be some specific organization member. Only if the users have github account, anybody can log in to the site.