<offtopic> you don't have to move to RoR. chef is just an "emerging standard" in deployment recipes (you may also intend it as "buzzword-project gone right"). See it as fabric snippets on steroids. Puppet, ansible, salt, etc, are also on the same "family". http://redmonk.com/sogrady/2013/12/06/configuration-management-2013/ Instead of doing 'bash setup-*.sh' you do 'chef therecipe.rb' The fact that it needs ruby (not RoR) it's just due to the fact that creating DSL is much easier in ruby than python. </offtopic>
On Sunday, March 23, 2014 6:38:55 PM UTC+1, Michele Comitini wrote: > > 2014-03-23 18:31 GMT+01:00 Niphlod <nip...@gmail.com <javascript:>>: > > having a chef opcode does not count as "ruby is needed". Given chef's > > spread, it's exactly as if we shipped all scripts/setup* scripts in > ruby. > I hope not! I started using web2py to avoid moving to ruby RoR! ;-) > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
