The routing pattern we use in CB2 needs to be finalized. Currently there are a
couple of different routing patterns in use which is going to lead to problems
down the road.
Fact: We need to have two controllers per barclamp/managed object. One for UI
and another for API calls. There was an
The discussion happened quite a while ago with Rob. I was originally hoping we
could have a single controller for both API and UI who's methods would handle
returning both JSON and HTML which is really the rails way of doing it. But
because of the requirement of the API and the need of the Ser
Snap?
-Original Message-
From: crowbar-bounces On Behalf Of Judd Maltin
Sent: Monday, September 16, 2013 10:10 AM
To: Adam Spiers
Cc: crowbar
Subject: Re: [Crowbar] New names for NodeRole > suggesting "Tack"
again, as usual, I'm +1 Spiers.
On Sat, Sep 14, 2013 at 8:20 AM, Adam Spiers wr
+1
-Original Message-
From: crowbar-bounces On Behalf Of Jensen, Scott
Sent: Monday, October 07, 2013 5:28 PM
To: crowbar
Subject: Re: [Crowbar] Split this list into users and dev?
Although the volume is quite low I think that there are users who are 1) Not
comfortable asking basic ques
Is it worthwhile to look at octokit and writing a dev tool replacement in Ruby?
Octokit is the github supported Ruby toolkit for the github API.
https://github.com/octokit/octokit.rb
Thanks,
dp
From: crowbar-bounces On Behalf Of Victor Lowther
Sent: Friday, January 03, 2014 10:49 AM
To: Adam
Dell - Internal Use - Confidential
+1 Sounds great.
-Original Message-
From: crowbar-bounces On Behalf Of Dirk Müller
Sent: Friday, March 28, 2014 5:23 AM
To: crowbar
Subject: [Crowbar] Trove barclamp for Crowbar
Hi,
SUSE, namely Ionut Artarisi, developed a barclamp for deploying Trove
