|| at Feb 19, 2013 at 9:26 am
I respectfully disagree :)
I have yet to see a community grow and thrive based on planning ahead.
If this effort is going to be based on voluntary work, I fully expect a lot
of duplication, mistakes and cargo-culting. We have seen that in Ruby and
Rails plugins a few years ago, and we still see that in a lot of PHP
projects (no slight intended).
Best practices are an emerging property; maybe the community will notice
repeating patterns and start reducing duplications; maybe some
highly-motivated, OC guy (no offense intended, I kind of fit the bill) will
take it on himself to do this cleanup.
But that can wait I think; if by that time we have a directory of hundreds
of OSS projects, that will still be a success in my book.
On Tue, Feb 19, 2013 at 6:05 AM, Matt Reider wrote:
Fascinating. Like most things, I would think some planning would make
sense here - so that apps with similar dependencies don't have completely
independent buildpacks, but rather common ancestry across related
On Mon, Feb 18, 2013 at 6:25 AM, Dr Nic Williams wrote:
This is a good idea.
BTW, has anyone tried to patch an OSS project to run on CF and not had
their patch accepted?
On Mon, Feb 18, 2013 at 5:54 AM, Manuel Garcia wrote:
On Feb 18, 2013 8:27 AM, "Andrea Campi" <email@example.com
I'm starting to look at Chef cookbooks to deploy the new DEA, and that
got me thinking.
IIUC the buildback-based staging will support custom buildpacks
specified by passing a URL, right?
If that's the case, then that's our opportunity for world domination!
Ideally, the CF community should be contributing patches to OSS
projects so that they can run on CF out of the box.
However that is time consuming, and there's no guarantee the
maintainers will even merge those changes.
A custom buildpack would allow us to patch software on the flight.
Take something like Redmine, a Ruby on Rails app.
Aside from binding to the DB service (that will probably work
automagically) all that is takes (probably) is to create a
configuration.yml file (similar to the example  in the repo) that uses
If we do this, I imagine we could build a "directory" listing OSS
projects with their custom buildpacks.
That could do wonders for adoption of CF!
Dr Nic Williams
Stark & Wayne LLC - consultancy for Cloud Foundry usershttp://drnicwilliams.comhttp://starkandwayne.com
cell +1 (415) 860-2185