Hi Hedge, thank you for sharing cuken with us.
I personally never bought the Cucumber approach, so I don't have much
interest in such a project, while I can appreciate your effort and I
guess others will share your feelings about this idea. Besides that, now
I intend to start working on the migration from Rails 2 to Rails 3.1 in
Gitorious, so this is what I intend to spend most of my free time on
lately...
Best regards,
Rodrigo.
Em 07-05-2011 04:15, Hedge Hog escreveu:
On Sat, May 7, 2011 at 6:43 AM, Rodrigo Rosenfeld Rosas
<[email protected]> wrote:
Hi, I finished a first version of the Gitorious cookbook for Opscode Chef.
Could some one please test it on a virtual machine with last stable Debian
installed?
It took less than 15 minutes for me... Instructions are here:
https://github.com/rosenfeld/gitorious-cookbooks
I got two messages like below in production.log:
** ultrasphinx: spelling support not available (raspell configuration raised
"uninitialized constant Ultrasphinx::Spell::Aspell")
Probably this is not a big deal since it doesn't happen to repeat anymore...
I still couldn't figure out how to setup Exim4 for usage as a smart host for
GMail. It would be great if someone could add support for GMail to this
recipe.
If anyone is interested in contributing to this cookbook, just do a fork in
Github and issue a pull request.
I'm not hosting this in Gitorious because the lack of some basic issues
management tool. We should work on this, right? It would be great if we
could integrate Redmine or ChiliProject to Gitorious. It would be much
superior than Github's.
Please give me some feedback,
Hi,
Apologies if this is a _little_ off topic:
This looks very interesting, and this chef use case is what I had in
mind with the cuken[0] and [1]project: Documentation, which is
executable, of non-trivial setups.
To illustrate I made an example that starts a chef server, using a
Vagrant VM, and then installs a Zenoss server onto another VM, using
the just created Chef server to install zenoss.
You can see the example here[2].
Now cuken is still quite raw, and it might not (yet) have all the
steps that you need to set up Gitorious, but it would be interesting
to see how far you can get.
If you do try to create an executable-description of a Gitorious
setup, I would be interested in what pain points you experienced. And
what steps you thought were still needed.
One caveat is that cuken assumes cookbooks are 'first class citizens',
i.e. each exists in their own repository, and you access your
cookbooks accordingly using git rather than knife. Although cuken
does use knife extensively for other tasks.
Finally I am looking for collaborators to joins the github cookbooks
account and take ownership of cookbooks they have expertise in.
Exactly what that involves trying to achieve hasn't yet been fully
worked, and is wide open. github message me if you are interested in
helping at that level, alterbnativly if you want your changes
contributed to a cookbook, just rebase on the QA branch and issue a
pull request (master is reserved for upstreams changes) .
Again, please bear in mind that cuken is still quite raw, and step
definitions may change rapidly so you could have to rework to keep up.
Anyway, HTH?
[0]: https://github.com/hedgehog/cuken
[1]: http://relishapp.com/hedgehog/cuken
[2]: http://relishapp.com/hedgehog/cuken/dir/zenoss-example/01-chef-server-vm
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
