from:"Ben"

Yep. The term for that in ruby is a block, which is a closure passed to a
method call. A closure is an anonymous function that runs in the scope of
where it was defined, not where it was called.

(Javascript functions are closures, but ruby methods aren't.)

In this case, what it means is that Enumerable#all? or Array#map can invoke
that block of mine by calling 'yield(item)' for each item of the list.
Because it's a closure, it runs in the binding it was defined, which is why
it can see #run_requirement.

A closure is a way of passing a context around -- it says to 'all?' or
'map', "here's some custom logic, if you pass control to me at the right
moment then I'll run it in my house and return the resulting value".

- Ben



On 7 May 2013 15:35, Sam Howie  wrote:

> @Simon
>
> Haha, yes the example was for structure. And, as you caught, I haven't
> quite kicked the habit of typing in all those parentheses! Thanks for
> confirming that implicit return values are still the established convention
> here.
>
> @Ben
>
> Thank you for sharing your code. I love how succinct it is and can see
> what you are getting at. It's not all readable to me yet, showing that I
> have a bit further to go in learning Ruby's syntax. This is off topic, but
> I have particular trouble with:
>
> {|r| run_requirement(r, and_meet) }
>
> Is that defining an annonymous function where |r| is the parameter,
> similar to the javascript:
>
> function(r){run_requirement(r, and_meet)}
>
>
>
>
>
> On Tue, May 7, 2013 at 3:24 PM, Simon Russell wrote:
>
>> Obviously you'd write your thing as:
>>
>> def is_grater_than_five(a)
>>   a > 5
>> end
>>
>> But I assume you mean the structure; yes, that's normal, and it
>> becomes readable.  As long as you don't have returns making things
>> complex in the middle.  (Also, no parentheses around the if
>> condition.)
>>
>> On Tue, May 7, 2013 at 3:15 PM, Sam Howie  wrote:
>> > *EDIT
>> >
>> > def is_grater_than_five(a)
>> >   if (a > 5)
>> > true
>> >   else
>> > false
>> >   end
>> > end
>> >
>> >
>> > On Tue, May 7, 2013 at 3:14 PM, Sam Howie  wrote:
>> >>
>> >> Thanks everyone. It seems pretty decisive that implicit returns are the
>> >> established convention, where explicit returns are acceptable when
>> exiting
>> >> the function early.
>> >>
>> >> But how about in conditional logic?
>> >>
>> >> def is_grater_than_five(a)
>> >>   if (a > 5)
>> >> true
>> >>   else
>> >> false
>> >> end
>> >>
>> >> This seems pretty readable with a simple function like the above, but I
>> >> could see those implicit returns becoming lost in messier code (which
>> of
>> >> course no one ever writes ;P)
>> >>
>> >>
>> >>
>> >> On Tue, May 7, 2013 at 2:59 PM, Steve H  wrote:
>> >>>
>> >>> I agree with Craig - I only use explicit returns for early exits. That
>> >>> seems to be the general convention.
>> >>>
>> >>> The GitHub style guide is generally close to what people consider
>> >>> idiomatic Ruby to be: https://github.com/styleguide/ruby
>> >>>
>> >>> --
>> >>> You received this message because you are subscribed to the Google
>> Groups
>> >>> "Ruby or Rails Oceania" group.
>> >>> To unsubscribe from this group and stop receiving emails from it,
>> send an
>> >>> email to rails-oceania+unsubscr...@googlegroups.com.
>> >>> To post to this group, send email to rails-oceania@googlegroups.com.
>> >>> Visit this group at
>> http://groups.google.com/group/rails-oceania?hl=en.
>> >>> For more options, visit https://groups.google.com/groups/opt_out.
>> >>>
>> >>>
>> >>
>> >>
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups
>> > "Ruby or Rails Oceania" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an
>> > email to rails-oceania+unsubscr...@googlegroups.com.
>> > To post to this group, send email to rails-oceania@googlegroups.com.
>> > Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
>> >

Re: [rails-oceania] [BEGINNER] Implicit vs Explicit return values

Yep. To me this means "use lambda, not proc" as well as "don't use return".
(Procs are also absent from my idealised ruby) :)

Sam, you're right, the value that's being implicitly returned can be hard
to see in a complex method. I actually view this as a point in favour of
implicit returns, because when costs are visible, the fix (refactoring the
method) is clear.

- Ben



On 7 May 2013 15:48, Paul Annesley  wrote:

> Maybe a better example:
>
> # unsurprising:
> lambda { proc { 1 }.call + 1 }.call  # => 2
> lambda { lambda { return 1 }.call + 1 }.call  # => 2
>
> # surprising?
> lambda { proc { return 1 }.call + 1 }.call  # => 1
>
> — Paul
>
>
> On 07/05/2013, at 3:42 PM, Paul Annesley  wrote:
>
> > Returning in a lambda returns from the lambda back to its caller.
> > This is normally what you want.
> >
> > pry(main)> lambda { return }.call
> > => nil
> >
> > Returning in a proc returns from the caller, up to its caller… usually
> unexpected.
> >
> > pry(main)> proc { return }.call
> > LocalJumpError: unexpected return
> > from (pry):5:in `block in __pry__'
> >
> > Stabby-syntax is the nice lambda behaviour:
> >
> > [7] pry(main)> ->{ return }.call
> > => nil
> >
> > So running a non-lambda proc is kind of like eval'ing its code in your
> current context, rather than adding to the call stack.
> >
> > — Paul
> >
> >
> >
> > On 07/05/2013, at 3:38 PM, Michael Gall  wrote:
> >
> >> I seem to recall some weirdness with explicit returns in relation to
> lamdas, procs or blocks. Something like:
> >>
> >> %w(a b c).map do |i|
> >>  puts i
> >>  return i
> >> end
> >>
> >>
> >> This is invalid code, throws an unexpected return error, meaning that
> moving style between that sort of calls with explicit returns is crappy.
> >>
> >> There's another instance where returning from a proc or a lambda
> changes the behaviour. Anyone care to jog my memory?
> >>
> >>
> >>
> >>
> >> On Tue, May 7, 2013 at 3:24 PM, Simon Russell 
> wrote:
> >> Obviously you'd write your thing as:
> >>
> >> def is_grater_than_five(a)
> >>  a > 5
> >> end
> >>
> >> But I assume you mean the structure; yes, that's normal, and it
> >> becomes readable.  As long as you don't have returns making things
> >> complex in the middle.  (Also, no parentheses around the if
> >> condition.)
> >>
> >> On Tue, May 7, 2013 at 3:15 PM, Sam Howie  wrote:
> >>> *EDIT
> >>>
> >>> def is_grater_than_five(a)
> >>>  if (a > 5)
> >>>true
> >>>  else
> >>>false
> >>>  end
> >>> end
> >>>
> >>>
> >>> On Tue, May 7, 2013 at 3:14 PM, Sam Howie  wrote:
> >>>>
> >>>> Thanks everyone. It seems pretty decisive that implicit returns are
> the
> >>>> established convention, where explicit returns are acceptable when
> exiting
> >>>> the function early.
> >>>>
> >>>> But how about in conditional logic?
> >>>>
> >>>> def is_grater_than_five(a)
> >>>>  if (a > 5)
> >>>>true
> >>>>  else
> >>>>false
> >>>> end
> >>>>
> >>>> This seems pretty readable with a simple function like the above, but
> I
> >>>> could see those implicit returns becoming lost in messier code (which
> of
> >>>> course no one ever writes ;P)
> >>>>
> >>>>
> >>>>
> >>>> On Tue, May 7, 2013 at 2:59 PM, Steve H  wrote:
> >>>>>
> >>>>> I agree with Craig - I only use explicit returns for early exits.
> That
> >>>>> seems to be the general convention.
> >>>>>
> >>>>> The GitHub style guide is generally close to what people consider
> >>>>> idiomatic Ruby to be: https://github.com/styleguide/ruby
> >>>>>
> >>>>> --
> >>>>> You received this message because you are subscribed to the Google
> Groups
> >>>>> "Ruby or Rails Oceania" group.
> >>>>> To unsubscribe from this group and stop receiving emails from it,
> send an
> >>>>> email to rails-oceania+uns

Re: [rails-oceania] Re: Running rack apps

In that case, how does it spawn a new version of itself?


On 7 May 2013 15:00, Chris Berkhout  wrote:

> I don't have unicorn daemonize, so upstart keeps the pid of the bourne
> shell it started (which runs bash, which runs unicorn).
>
> # service restful_geof status
> restful_geof start/running, process 2777
> # ps -F -p 2777
> UIDPID  PPID  CSZ   RSS PSR STIME TTY  TIME CMD
> root  2777 1  0  1099   612   0 May06 ?00:00:00 /bin/sh -e
> /proc/self/fd/9
>
> upstart doesn't know anything about the child unicorns. I'm not sure
> whether that could lead to zombies. I think it won't necessarily if unicorn
> manages the child processes properly.
>
>
>
> On Tue, May 7, 2013 at 2:27 PM, Paul Annesley  wrote:
>
>>
>> On 07/05/2013, at 2:15 PM, Samuel Richardson 
>> wrote:
>>
>> > Interesting. I've tried switching over to Upstart a couple of times but
>> ran into trouble with it monitoring Sidekiq (I think, I can't remember
>> exactly what process it was but it had forking behaviour).
>>
>> Probably not Sidekiq, I don't believe it forks.
>> It's threaded and uses https://github.com/celluloid/celluloid
>>
>> ~/github/sidekiq ⸩ ack --ruby '^[^#]*fork'
>> # $? == 1
>>
>> Unicorn certain forks, though. Also, Resque I believe.
>>
>> — Paul
>>
>>
>> >
>> > Because of that, I'd stuck with monit as I could just point it at a PID
>> file and be done with it.
>> >
>> > Runit with the REST interface looks very nice though.
>> >
>> > Samuel Richardson
>> > www.richardson.co.nz | 0405 472 748
>> >
>> >
>> > On Tue, May 7, 2013 at 2:12 PM, Michael Pearson 
>> wrote:
>> > This was a long time ago, so it's fuzzy, but: its configuration
>> language was confusing, it had confusing semantics for stopping/starting
>> jobs, and it didn't log output at all, so you had no idea _why_ a
>> particular process wasn't starting or stopping properly.
>> >
>> > I then switched to runit, which was pretty simple (and good).
>> >
>> > When I upgraded our systems to Ubuntu 12.04 I checked out upstart, and
>> they'd made many improvements since what shipped with 10.04 (including
>> output logs), and I haven't looked back.
>> >
>> >
>> > On Tue, May 7, 2013 at 2:09 PM, Samuel Richardson 
>> wrote:
>> > While I'm enjoying this tangent on unicorn behaviour, I'm also an avid
>> Monit user. What were your problems with it?
>> >
>> > Samuel Richardson
>> > www.richardson.co.nz | 0405 472 748
>> >
>> >
>> > On Tue, May 7, 2013 at 2:08 PM, Michael Pearson 
>> wrote:
>> > Oh, one time?
>> >
>> > My start/stop script got out of whack (protip: monit is terrible, use
>> runit or upstart instead) and so I had to say "that's not working because
>> the system is overrun with rogue unicorns"
>> >
>> > Okay I'm done.
>> >
>> >
>> > On Tue, May 7, 2013 at 12:35 PM, Michael Pearson 
>> wrote:
>> > Unicorn is excellent because you can say things like:
>> >
>> > "are there any unicorns still alive?"
>> > "Oh, crap, we have zombie unicorns"
>> >
>> > and
>> >
>> > "The master unicorn has spawned a new child. Once the new child has
>> spawned all of its new unicorns, and they have grown up, it will kill the
>> older master unicorn, and all of its children will die"
>> >
>> > This is otherwise known as sending it the USR2 signal.
>> >
>> > On Wed, May 1, 2013 at 10:20 AM, Ben Hoskings  wrote:
>> > We run two production rack/sinatra apps at TC. I recommend nginx +
>> unicorn.
>> >
>> > This is how I do it (it's badly named; it's not rails-specific):
>> https://github.com/conversation/babushka-deps/blob/master/rails.rb#L1-L4
>> >
>> > - Ben
>> >
>> >
>> >
>> > On 1 May 2013 10:00, Steve H  wrote:
>> > I've had good luck with Unicorn. I use it with nginx but Apache will
>> work equally well, as you just reverse proxy a port or unix socket.
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Ruby or Rails Oceania" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to rails-oceania+unsubscr

Re: [rails-oceania] [BEGINNER] Implicit vs Explicit return values

My other reason, which I think I value more, is that using return means
thinking in a procedural way. "Right, step one, return the first result of
scanning like this":

  def first_word(text)
return text.scan(/\w+/).first
  end

But without return, it reads declaratively. "the first word is the first
result from scanning like this":

  def first_word(text)
text.scan(/\w+/).first
  end

The method doesn't look like instructions anymore; it just _is_ the first
result of scanning the string. The method just has a certain value because
it's defined that way.

It's a much more functional design: you can think of the method like a
mapping from input to output, like a mathematical function.

Of course, it could well be side-effecting; this is stylistic only. But I
think what arises reads well (these 4 or 5 methods are a set that recurse
together):
https://github.com/benhoskings/babushka/blob/master/lib/babushka/dep.rb#L313

- Ben

On 7 May 2013 14:56, Craig Ambrose  wrote:

>  That's a pretty good question Sam. There's a definite convention amongst
> ruby programmers to rely on the implicit return value. Certainly I never
> use the return keyword unless I'm doing an early exit from a method (which
> is not something I do often). This seemed strange to me for my first few
> weeks using ruby, but now I wouldn't want to do it any other way. It's
> particularly clear if you use small methods, like in your example, and then
> you start to think of the methods almost as logical expressions.
>
> --
> Craig Ambrose
> Atamai Village, Motueka
> Please join us on facebook at http://www.facebook.com/atamaivillage
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rails-oceania+unsubscr...@googlegroups.com.
> To post to this group, send email to rails-oceania@googlegroups.com.
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
Cheers
Ben

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] [BEGINNER] Implicit vs Explicit return values

I strongly favour implicit returns. I see return as a surprise, and I think
the flow of conditional logic is a better way to express return values.

If that logic becomes too complex, I think the answer is to break up the
method, not use 'return'.

The idealised version of ruby in my head doesn't have a 'return' keyword.

- Ben



On 7 May 2013 14:33, Sam Howie  wrote:

> Hi all,
>
> <
> My name is Sam Howie. I am a gameplay programmer looking to diversify into
> the more stable field of web development.
>
> A good friend of mine highly recommended Ruby and Ruby on
> Rails, emphasising that the community is friendly and supportive. I liked
> the sound of that. So, here I am learning the ins and out of Ruby before
> I tackle the Rails framework.
>
> PREAMBLE
>
>
> I have noticed that Ruby functions, like CoffeeScript functions, always 
> return a value. This allows for implicitly returning values like the 
> following:
>
>
> def add(a, b)
>
>   a + b
>
> end
>
>
> However, you can also explicitly return values from function as in the 
> following:
>
>
> def add(a, b)
>
>   return a + b
>
> end
>
>
> Now, I was wondering, is there an established best practice for this in terms 
> of readability?
>
>
> Personally, I come from a background where I would favour explicitly 
> returning values. At first glance it seems that explicitly returning values 
> would allow for quicker code scanning. What does the community think?
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rails-oceania+unsubscr...@googlegroups.com.
> To post to this group, send email to rails-oceania@googlegroups.com.
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Cheers
Ben

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Helping Junior Rubists Find Work

2013-05-03 Thread Ben Taylor

I definitely agree with Steven. I was lucky enough to discover Ruby + Rails via 
a friend and ended up doing freelance and contract work while I was at Uni, but 
many other students aren't in the same boat. Either they never find out about 
the community (does Ruby AU do outreach to universities?) or they don't have 
the time (can you imagine learning Ruby on Rails on the side while also writing 
an Honours thesis and working weekends to cover your expenses?). Big companies 
are very visible and they have obvious grad programs that are easy to sign up 
to.

Some of the best CS students I know have ended up in graduate roles at Banks 
and Consultancy firms. Many of them would love to transition to Ruby on Rails 
work, or Django work, or iOS dev or just about anything that doesn't involve 
three meetings a day and a slew of bland work. But the community just doesn't 
seem to want them. The silly bit is that for many of them getting productive in 
a new language isn't a big deal.

As the others have said, graduate or intern programs could definitely help your 
business (and give back to the community!)

- Ben


On Friday, 3 May 2013 at 5:02 PM, Steven Farlie wrote:

> My anecdotal experience (as a volunteer coach/organiser in OpenTechSchool) is 
> that the talent base for junior programmers is incredibly broad but it is 
> there. There are people with programming knowledge but not domain knowledge 
> (e.g. Python but not web), or domain knowledge without the platform (web but 
> not specifically Ruby/Rails is very common). Lots of people from the sciences 
> (there are no jobs in science!). Aside from the lucky few who fell into the 
> scene outside of their studies they simply don't know where to go. Others go 
> through private courses like Sydney Dev Camp or App Academy. I know there is 
> a supply of raw talent, but it is difficult for employers to find. Not to 
> mention the problem of evaluating. Picking a good hire is a lottery at the 
> best of times.
> 
> If anyone is musing about opening a junior role I would encourage it. It can 
> be immensely rewarding both for the dev and the team. Think of all those bad 
> habits they would never even have the chance to learn! 
> -- 
> Steven
> 
> 
> 
> On 3 May 2013 14:56, Michael Pearson  (mailto:mipear...@gmail.com)> wrote:
> > This isn't consistent with my most recent experiences recruiting: we 
> > advertised at all levels, and received very few applications from junior 
> > developers. You're welcome to search the list and find the job ad I posted.
> > 
> > At the time, we were looking specifically at both ends of the spectrum: 
> > either somebody shit hot to help teach us some cool new tricks (which is 
> > what we got, in the end) or somebody fresh that who could bring in some 
> > optimism and take some of the load off while we worked out how to fix 
> > everything. 
> > 
> > It's also possible that I, being the one who posted the ad, was being 
> > deliberately exclusionary: I only wanted juniors to apply via the mailing 
> > list rather than via recruiters or seek. I wanted somebody who was keen 
> > enough about Ruby to be part of the community (or at least be aware that it 
> > exists), rather than somebody who's just graduated a Java-heavy CS degree 
> > and will now latch on to anything that will help them make rent this month. 
> > 
> > So it's possible that we're not hostile towards juniors - but possibly 
> > we're doubtful of juniors put forward via recruiters, thanks to being 
> > burned before by resume-fiddling and other such nasty things. 
> > 
> > Also - do these several amazing juniors have github accounts, or other 
> > proof of capability? Are they on this list (at least filtered for anything 
> > with [JOB] in the title)? 
> > 
> > 
> > On Fri, May 3, 2013 at 2:26 PM, Ashley Pettit  > (mailto:is_ash_is_g...@hotmail.com)> wrote:
> > > Hi Guys,
> > > 
> > > I've noticed a bit of a problem with the ruby community and I wanted to 
> > > voice my concerns.  
> > > 
> > > Firstly let me say the ruby community is great. Full of passionate people 
> > > who love what they do and 9 times out of 10 something built in ruby is 
> > > better than something not purely because the developers are so passionate 
> > > about creating awesome products. 
> > > 
> > > So where's the problem?
> > > 
> > > Ruby is a language which has been embraced by start-ups and small-medium 
> > > sized businesses. It's not something the larger companies have taken to. 
> > > 
> > > Why is this a problem?
> &g

Re: [rails-oceania] [JOB] Contract/Perm Ruby Dev Roles - Melbourne Based

2013-05-03 Thread Ben Schwarz

Comments on job threads are often better handled off-list (privately) 
Locking this thread. 

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] [JOB] Contract/Perm Ruby Dev Roles - Melbourne Based

2013-05-03 Thread Ben Taylor

Daniel, while you may be technically correct it's really not useful to point 
out.

At various points in the past people have attempted to patch the masculine 
version of pronouns to be gender non-specific (see: 
http://en.wikipedia.org/wiki/Gender-neutral_pronoun). This has been widely 
unsuccessful and while "guys" to you may be the equivalent of "people" it 
definitely has gendered tones. The best solution is to try your best to stick 
to gender neutral versions. Saying "Hey everyone" or "Hey rubyists" or "Hello 
there, reader" can all work.

This goes across the board, if you don't have enough information to pin a 
gender, you should try not to. I personally enjoy playing "the gender-neutral 
game" by trying to avoid all references to gender, even when the subject is 
obviously gendered to all parties (see: 
http://en.wikipedia.org/wiki/Wikipedia:Gender-neutral_language).

And now a lesson: When someone expresses they feel like they're being excluded, 
the easiest way to make that worse is to explicitly tell them they're wrong.

I personally believe you had the best of intentions, but I recommend more tact 
in the future.

These conversations can easily flame up - so I'm hoping that we won't have too 
many more replies. Let's all try to keep this list on topic (while still 
allowing people to bring up issues of inequity and unprofessional conduct).  

- Ben

On Friday, 3 May 2013 at 5:33 PM, Daniel Sabados wrote:

>  
> On Fri, May 3, 2013 at 2:49 PM, Alex "Skud" Bayley  (mailto:s...@infotrope.net)> wrote:
> > On 3/05/13 9:17 AM, Brent Thomson wrote:
> > >  
> > > Hi Guys,
> > >  
> > >  
> >  
> >  
> > Just a reminder that not everyone on this mailing list is a guy.
>  
> Just a reminder guys that "guys" refers to either sex.
>  
> http://oxforddictionaries.com/definition/english/guy  
>  
>  (guys) people of either sex:you guys want some coffee?  
> http://www.merriam-webster.com/dictionary/guy
>  
> b : person (http://www.merriam-webster.com/dictionary/person) —used in plural 
> to refer to the members of a group regardless of sex  the guys>  
>  
> Just saying..
>   
> >  
> > A.
> >  
> > -- Alex "Skud" Bayley s...@infotrope.net (mailto:s...@infotrope.net) 
> > http://infotrope.net/  
> >  
> > --  
> > You received this message because you are subscribed to the Google Groups 
> > "Ruby or Rails Oceania" group.
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to rails-oceania+unsubscr...@googlegroups.com 
> > (mailto:rails-oceania%2bunsubscr...@googlegroups.com).
> > To post to this group, send email to rails-oceania@googlegroups.com 
> > (mailto:rails-oceania@googlegroups.com).
> > Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >   
> >   
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rails-oceania+unsubscr...@googlegroups.com 
> (mailto:rails-oceania+unsubscr...@googlegroups.com).
> To post to this group, send email to rails-oceania@googlegroups.com 
> (mailto:rails-oceania@googlegroups.com).
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>   
>   

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[rails-oceania] Re: Mid-2013 Melbourne RailsCamp?

2013-05-02 Thread Ben Schwarz

Announce is coming soon, but: 

It'll be June 21—24, in Melbourne. 

Still plenty of time for flights. 

Follow @railscamp_au on Twitter to keep in touch. 

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Re: Running rack apps

2013-04-30 Thread Ben Hoskings

Yeah, that's a good idea when they're a small extra piece.

In this case, they're distinct apps with their own DBs (to postgres via
sequel), and so I want each one to have separate DB credentials, to run as
a separate unix user, etc.

- Ben



On 1 May 2013 10:35, Andrew Harvey  wrote:

> I'm a big fan of using config.ru to mount my rack apps next to my rails
> app where it's useful as well.
>
> I've only used it when taking a path and routing to that, so if need to
> work by domain, then a separate unicorn instance is probably the go.
>
> A.
>
> On 30/04/2013, at 5:20 PM, Ben Hoskings  wrote:
>
> We run two production rack/sinatra apps at TC. I recommend nginx + unicorn.
>
> This is how I do it (it's badly named; it's not rails-specific):
> https://github.com/conversation/babushka-deps/blob/master/rails.rb#L1-L4
>
> - Ben
>
>
>
> On 1 May 2013 10:00, Steve H  wrote:
>
>> I've had good luck with Unicorn. I use it with nginx but Apache will work
>> equally well, as you just reverse proxy a port or unix socket.
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Ruby or Rails Oceania" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to rails-oceania+unsubscr...@googlegroups.com.
>> To post to this group, send email to rails-oceania@googlegroups.com.
>> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>
>
> --
> Cheers
> Ben
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rails-oceania+unsubscr...@googlegroups.com.
> To post to this group, send email to rails-oceania@googlegroups.com.
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rails-oceania+unsubscr...@googlegroups.com.
> To post to this group, send email to rails-oceania@googlegroups.com.
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Cheers
Ben

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Re: Running rack apps

2013-04-30 Thread Ben Hoskings

We run two production rack/sinatra apps at TC. I recommend nginx + unicorn.

This is how I do it (it's badly named; it's not rails-specific):
https://github.com/conversation/babushka-deps/blob/master/rails.rb#L1-L4

- Ben



On 1 May 2013 10:00, Steve H  wrote:

> I've had good luck with Unicorn. I use it with nginx but Apache will work
> equally well, as you just reverse proxy a port or unix socket.
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rails-oceania+unsubscr...@googlegroups.com.
> To post to this group, send email to rails-oceania@googlegroups.com.
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Cheers
Ben

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Testing before_filters

2013-04-29 Thread Ben Hoskings

I think it makes debugging easier, not harder -- it produces a hard
exception with a complete callstack. A 404 caused by a before_filter can
take a lot of spelunking to track down.

- Ben



On 30 April 2013 09:24, Clifford Heath  wrote:

> On 29/04/2013, at 9:28 PM, William Madden  wrote:
> > Nice approach Ben, that (memoized helpers) is a lot cleaner than before
> filters.
>
> Just beware that this approach delays the "record not found" exception
> until
> you first call the helper. That might be inside some view code, which can
> make
> debugging harder.
>
> Clifford Heath
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rails-oceania+unsubscr...@googlegroups.com.
> To post to this group, send email to rails-oceania@googlegroups.com.
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>


-- 
Cheers
Ben

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[rails-oceania] [OT] Support the Draft Digital Technologies Curriculum

2013-04-29 Thread Ben Taylor

Some of you may have seen me post in the past about a High School camp I help
tutor for where we teach students Python and general Web Development skills.
Those involved with running the camp (NCSS, particularly James Curran, Tara
Murphy and Nicky Ringland) have been part of the Draft process for a new
Digital Technologies Curriculum which looks very promising, involving students
in CS topics long before High School. You can support it here:

https://www.change.org/en-AU/petitions/australian-curriculum-assessment-and-reporting-authority-acara-support-the-draft-digital-technologies-curriculum

You may remember your own High School experiences and how significantly lacking
they were. I remember studying Software Development in year 12 using a textbook
which was authored before I started primary school. Not much has changed since
then. NCSS outreach helps many highly motivated students, but those less
motivated never get the chance to see the fantastic things they could
potentially create. I personally hope that in the future this won't be the case.

Cheers,
- Ben

--
You received this message because you are subscribed to the Google Groups "Ruby
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Re: Testing before_filters

2013-04-28 Thread Ben Hoskings

"AAA" is the response they elicit in me when I see a bunch of them atop a
controller. :)

I assume you mean auth*n? A single before_filter for auth is reasonable, I
think, but I've also designed it without any filter at all, having the
#current_user method lazily auth. That worked really nicely. This is
approximately what it does:

def current_user
  @current_user ||= retrieve_user.tap do |user|
store_session_for(user)
set_time_zone_for(user)
  end
end
helper_method :current_user

def retrieve_user
  retrieve_user_from_session || retrieve_user_from_cookie ||
retrieve_user_from_login_token
end

Which means #before_filter really can be avoided (almost) entirely:
http://d.pr/1Rms (Forgive me for that #skip_before_filter; I wrote that
code in the days when flash was the only way to do multiple file uploads
and the resulting requests don't preserve the session.)

- Ben



On 29 April 2013 12:19, Michael Pearson  wrote:

> That's clever, Ben.
>
> What about the AAA role that before_filters tend to perform?
>
>
> On Mon, Apr 29, 2013 at 12:16 PM, Ben Hoskings  wrote:
>
>> This is my problem with before_filters: they side-effect to do their job.
>> Store-and-call is a huge smell in this situation. It causes awful coupling,
>> and leads to very confusing bugs because the before_filter isn't in the
>> action callstack.
>>
>> They also lead to extensive instance variable use in views, which is also
>> a really bad pattern, since they default to nil and can't be worked with
>> reasonably like a method call can.
>>
>> I think before_filters are best avoided whenever possible (there are a
>> select few cases where they're useful, though). I prefer to use lazy
>> private helpers instead, like:
>>
>>   def post
>> @post ||= Post.from_params!(params[:that_you_want])
>>   end
>>   helper_method :post
>>
>>
>>
>>
>> On 29 April 2013 12:08, Mario Visic  wrote:
>>
>>> Hi Will
>>>
>>> Nice writeup, looks like it's really useful.
>>> One thing to think about is that your before filter is now a public
>>> method on the controller.
>>> Perhaps you should move it to private/protected so that others don't
>>> rely on it.
>>>
>>> The one problem with this approach is that once it's a private method
>>> it's no longer a good idea to test the method directly anymore.
>>> The only other solution then would be to test the side affects of the
>>> method each time which can get cumbersome.
>>>
>>> If only controller testing were easier :)
>>>
>>> Cheers
>>> Mario
>>>
>>> On Saturday, April 27, 2013 11:56:12 PM UTC+10, William Madden wrote:
>>>>
>>>> Hey guys,
>>>>
>>>> I haven't seen a satifactory answer on the web for how to test before
>>>> filters thoroughly and without introducing duplication into my tests so I
>>>> worked out a solution of my own.
>>>>
>>>> The TL;DR is that you test the filter method on its own, then test that
>>>> it's invoked by each action you expect to be covered by it.
>>>>
>>>> There are a few hacks to get everything to behave so I wrote up how I
>>>> did 
>>>> it<http://tech.letsgeddit.com/2013/04/testing-beforefilters-in-isolation.html>
>>>> .
>>>>
>>>> Hope it helps,
>>>> Will
>>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "Ruby or Rails Oceania" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to rails-oceania+unsubscr...@googlegroups.com.
>>> To post to this group, send email to rails-oceania@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>>
>>
>>
>>
>> --
>> Cheers
>> Ben
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Ruby or Rails Oceania" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to rails-oceania+unsubscr...@googlegroups.com.
>> To post to this group, send email to rails-oceania@googlegroups.com.
>> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
>> For more options, visit https://groups.google.c

Re: [rails-oceania] Re: Testing before_filters

2013-04-28 Thread Ben Hoskings

This is my problem with before_filters: they side-effect to do their job.
Store-and-call is a huge smell in this situation. It causes awful coupling,
and leads to very confusing bugs because the before_filter isn't in the
action callstack.

They also lead to extensive instance variable use in views, which is also a
really bad pattern, since they default to nil and can't be worked with
reasonably like a method call can.

I think before_filters are best avoided whenever possible (there are a
select few cases where they're useful, though). I prefer to use lazy
private helpers instead, like:

  def post
@post ||= Post.from_params!(params[:that_you_want])
  end
  helper_method :post




On 29 April 2013 12:08, Mario Visic  wrote:

> Hi Will
>
> Nice writeup, looks like it's really useful.
> One thing to think about is that your before filter is now a public method
> on the controller.
> Perhaps you should move it to private/protected so that others don't rely
> on it.
>
> The one problem with this approach is that once it's a private method it's
> no longer a good idea to test the method directly anymore.
> The only other solution then would be to test the side affects of the
> method each time which can get cumbersome.
>
> If only controller testing were easier :)
>
> Cheers
> Mario
>
> On Saturday, April 27, 2013 11:56:12 PM UTC+10, William Madden wrote:
>>
>> Hey guys,
>>
>> I haven't seen a satifactory answer on the web for how to test before
>> filters thoroughly and without introducing duplication into my tests so I
>> worked out a solution of my own.
>>
>> The TL;DR is that you test the filter method on its own, then test that
>> it's invoked by each action you expect to be covered by it.
>>
>> There are a few hacks to get everything to behave so I wrote up how I
>> did 
>> it<http://tech.letsgeddit.com/2013/04/testing-beforefilters-in-isolation.html>
>> .
>>
>> Hope it helps,
>> Will
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rails-oceania+unsubscr...@googlegroups.com.
> To post to this group, send email to rails-oceania@googlegroups.com.
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Cheers
Ben

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Best practices for return values

2013-04-26 Thread Ben Hoskings

It depends on whether you're calling the method for its value, or for a 
side-effect.

If you want the value, then I'd make repeated calls just return the value, so 
the method is memoized (assuming the initial call is expensive).

If it's side-effecting, my feeling is that the method should always do its job 
whenit's called. If that causes an error, then you'll get a legitimate 
exception, which should be handled by the caller.

One exception is a method that explicitly should only run once, like ruby's 
#require. In that case, I think returning false (and true for the initial call 
that does work) makes sense; that's how #require behaves.

- Ben


Sent from my iPhone

On 26/04/2013, at 3:05 PM, Sebastian Porto  wrote:

> (Sorry if this ends as a double post, as I send this using email, but for 
> some reason it doesn't show in the group. So I am posting it again directly 
> on the group page.)
> 
> Hi All
> 
> I'm building a gem and trying to decide what is the best way to provide 
> return values.
> 
> Let's say that my gem add the do_something method to user:
> 
> user.do_something
> 
> But if that something is already done I want to provide meaningful feedback, 
> I can't decide what is a best practice here or what is better, these is what 
> I can think of:
> 
> Option 1. return false
> 
> res = user .do_something
> res //=> false
> user.errors //=> ['already done'] information about the errors, like 
> active record
> 
> Option 2. raise an exception (seems a little drastic)
> 
> begin
> res = user .do_something
> rescue MyGem::AlreadyDoneException => e
> 
> end
> 
> Option 3. return an error code
> 
> res = user.do_something
> res //=> 3 (meaning already done)
> 
> Option 4. return an object
> 
> res = user.do_something
> res.success //=> false
> res.messages //=> ['already done']
> 
> Any recommendations on what is a best practice here?
> 
> Thanks,
> Sebastian
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rails-oceania+unsubscr...@googlegroups.com.
> To post to this group, send email to rails-oceania@googlegroups.com.
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Using form_for with nested resources in a namespace

2013-04-24 Thread Ben Taylor

The big difference is that you're namespacing your models. Without the model 
namespacing it would "just work".

- Ben


On Wednesday, 24 April 2013 at 5:18 PM, Michael Webb wrote:

> Thanks Pat, will do. It is a bit of a pain when you're using the same form 
> for :new and :edit cause then you're stuck with ternary ifs all up in your 
> form_fors, but, if that's how Rails rolls, who am I to argue?
>  
> It's a bit bewildering as there are several suggestions that this should 
> "just work":
> http://stackoverflow.com/questions/2718059/nested-resources-in-namespace-form-for
>   
> http://stackoverflow.com/questions/4909988/rails-3-nested-resource-route-problem-as-form-for
>   
> https://github.com/rails/rails/issues/9146  
>  
> On Wednesday, April 24, 2013 5:13:16 PM UTC+10, Pat Allan wrote:
> > Ben's suggestions are spot on - if your models are namespaced, then the 
> > namespace is part of the generated route name.
> > You could probably work around this (see ActiveModel::Naming, which is 
> > included in ActiveRecord::Base), but personally I would just specify the 
> > url manually instead - sometimes it's not worth fighting Rails' opinions 
> > (and it could be that changing the model_name class method could result in 
> > complications elsewhere).
> > So:
> >   form_for @charge_rate, :url => 
> > reconciliation_charge_charge_rates_path(@charge, @charge_rate), #…
> > If you find yourself writing it a lot, I guess you could wrap it up in a 
> > helper.
> > --  
> > Pat
> > On 24/04/2013, at 9:00 AM, Ben Taylor wrote:
> > > I don't have a complete understanding here, but from what I'm seeing I'm 
> > > assuming that the way the URL is determined from a form_for takes into 
> > > account the objects type. So you have:
> > >  
> > > [:reconciliation, Reconciliation::Charge, Reconciliation::ChargeRate]
> > >  
> > > which rails is deciding should make a URL that looks like...
> > >  
> > > ["reconciliation", "reconciliation_charge", "reconiciliation_charge_rate"]
> > >  
> > > when what you actually want is
> > >  
> > > ["reconciliation", "charge", "charge_rate"]  
> > >  
> > > I've never namespaced my models, so I've never personally come across 
> > > this. If you are okay with a fix that changes your models, you could 
> > > remove the namespacing from your models and that would fix it.
> > >  
> > > Looking at StackOverflow all I can see is a recommendation to specify the 
> > > URL yourself. 
> > > http://stackoverflow.com/questions/11713427/form-for-with-module-and-namespace
> > >  
> > > Does that help?
> > >  
> > > - Ben
> > >  
> > > On Wednesday, 24 April 2013 at 3:34 PM, Michael Webb wrote:
> > >  
> > >> Hi all,
> > >>  
> > >> I'm building a fairly large Rails app for my current client and am doing 
> > >> a bit of a restructure of the database after a manic few months getting 
> > >> version one up and running.
> > >>  
> > >> I've tried to group tables into namespaces based on functionality and am 
> > >> having some serious difficulty getting form_for to work when it is 
> > >> operating on nested resources within a namespace.
> > >>  
> > >> From routes.rb:
> > >> ...
> > >> namespace :reconciliation do
> > >> resources :charges do
> > >> resources :charge_rates
> > >>  end
> > >> end
> > >> ...
> > >>  
> > >> From the relevant _form.html:
> > >> = form_for [:reconciliation, @charge, @charge_rate], :html => 
> > >> {:multipart => true, :class => "edit_form"} do |f|
> > >> ...
> > >>  
> > >> The line above raises: undefined method 
> > >> `reconciliation_reconciliation_charge_reconciliation_charge_rates_path' 
> > >> for #<#:0x3778080> in polymorphic_url.
> > >>  
> > >> I have verified that both @charge and @charge_rate are not null and are 
> > >> of the appropriate type (Reconciliation::Charge and 
> > >> Reconciliation::ChargeRate).
> > >>  
> > >> rake routes shows that the reconciliation_charge_charge_rates_path 
> > >> exists.
> > &g

Re: [rails-oceania] Using form_for with nested resources in a namespace

2013-04-24 Thread Ben Taylor

I don't have a complete understanding here, but from what I'm seeing I'm 
assuming that the way the URL is determined from a form_for takes into account 
the objects type. So you have:

[:reconciliation, Reconciliation::Charge, Reconciliation::ChargeRate]

which rails is deciding should make a URL that looks like...

["reconciliation", "reconciliation_charge", "reconiciliation_charge_rate"]

when what you actually want is

["reconciliation", "charge", "charge_rate"] 

I've never namespaced my models, so I've never personally come across this. If 
you are okay with a fix that changes your models, you could remove the 
namespacing from your models and that would fix it. 

Looking at StackOverflow all I can see is a recommendation to specify the URL 
yourself. 
http://stackoverflow.com/questions/11713427/form-for-with-module-and-namespace

Does that help?

- Ben


On Wednesday, 24 April 2013 at 3:34 PM, Michael Webb wrote:

> Hi all,
> 
> I'm building a fairly large Rails app for my current client and am doing a 
> bit of a restructure of the database after a manic few months getting version 
> one up and running.
> 
> I've tried to group tables into namespaces based on functionality and am 
> having some serious difficulty getting form_for to work when it is operating 
> on nested resources within a namespace.
> 
> From routes.rb:
> ...
> namespace :reconciliation do
> resources :charges do
> resources :charge_rates
> 
>  end
> end
> ...
> 
> From the relevant _form.html:
> = form_for [:reconciliation, @charge, @charge_rate], :html => {:multipart => 
> true, :class => "edit_form"} do |f|
> ...
> 
> The line above raises: undefined method 
> `reconciliation_reconciliation_charge_reconciliation_charge_rates_path' for 
> #<#:0x3778080> in polymorphic_url.
> 
> I have verified that both @charge and @charge_rate are not null and are of 
> the appropriate type (Reconciliation::Charge and Reconciliation::ChargeRate).
> 
> rake routes shows that the reconciliation_charge_charge_rates_path exists.
> 
> According to every article I could find on Stack Overflow, my _form.html code 
> should work, what am I doing wrong?
> 
> Thanks,
> 
> Mike 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rails-oceania+unsubscr...@googlegroups.com 
> (mailto:rails-oceania+unsubscr...@googlegroups.com).
> To post to this group, send email to rails-oceania@googlegroups.com 
> (mailto:rails-oceania@googlegroups.com).
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Hacknight

2013-04-11 Thread Ben Taylor

I intend to bring a project which is purely for evil.

- Ben


On Thursday, 11 April 2013 at 5:52 PM, Daryl Manning wrote:

> It's more a guideline, than a hard and fast rule. If it's FOSS that charities 
> *could* use, then sure!... And hey, even then "Hack Freestyle" is the 
> fallback.
> 
> ciao ! 
> Daryl.
>  
> 
> 
> 
> On Thu, Apr 11, 2013 at 5:36 PM, Jon Rowe  (mailto:m...@jonrowe.co.uk)> wrote:
> > If I bring open source to hack on, is that charitable enough :P
> > 
> > (I could be swayed into helping someone else on an actual charity project, 
> > especially if pairing) 
> > 
> > Jon Rowe
> > -
> > m...@jonrowe.co.uk (mailto:m...@jonrowe.co.uk)
> > jonrowe.co.uk (http://jonrowe.co.uk)
> > 
> > 
> > On Thursday, 11 April 2013 at 16:52, Daryl Manning wrote:
> > 
> > > Wiki has been updated with HackNight details. Sign up Rubyists! (um, or 
> > > javascript-ists! We're only banning Haskell users this time... =p ).
> > > 
> > > https://github.com/rails-oceania/roro/wiki/rorosyd-hack-night#do-gooder-and-freestyle-hacknight--the-institute-for-sustainable-futures
> > > 
> > > Please sign up early and especially let people know if you have a 
> > > charitable project that could use some assistance. 
> > > 
> > > thanks !
> > > Daryl.
> > > 
> > > 
> > > 
> > > On Thu, Apr 11, 2013 at 4:34 PM, Daryl Manning  > > (mailto:daryl.mann...@gmail.com)> wrote:
> > > > [Sorry, Andrew, this is probably my fault in not talking about 
> > > > HackNight as I wasn't at RORO. Thanks for the prod.]
> > > > 
> > > > Hack Night for April will take place on 23rd April at the Institute for 
> > > > Sustainable Futures 11th floor of Building 10 at the University of 
> > > > Technology Sydney (to the side of the large tower-y thing) on 235 Jones 
> > > > St. Out good friends at Ninefold cannot host this month. 
> > > > 
> > > > Pizza, cider, beer, non-alcoholic drinks will be provided in our 
> > > > (currently in middle of refurbishment) digs.
> > > > 
> > > > Details for access (Tim and I's phone number) to get into the secure 
> > > > building, will be posted on the wiki.  
> > > > 
> > > > We were hoping to have a "charitable" theme, this month. Find a project 
> > > > or a charity that needs some IT help and hack the hell out of it for a 
> > > > good cause (for example, I'm working on a worldwide Species Assurance 
> > > > database for endangered amphibians... fascinating project actually... 
> > > > ), but if you don't have anything, just come and "Hack As You Are." 
> > > > 
> > > > If you do have a charity project you'd like help with, let it be 
> > > > known... if you want oneand don't have one, ask a smaller charity whose 
> > > > work you like if you can help em out. Trust me, heaps of places in the 
> > > > industry *badly* need help, especially here in Aus. Volunteering is 
> > > > good for you...  
> > > > 
> > > > If you have any questions, let me know. Easiest to ping me @awws on 
> > > > twitter or Tim on @tjmcewan.
> > > > 
> > > > ciao !
> > > > Daryl. 
> > > > 
> > > > 
> > > > On Thu, Apr 11, 2013 at 3:27 PM, Andrew Grimm  > > > (mailto:andrew.j.gr...@gmail.com)> wrote:
> > > > > For the benefit of those not there on Tuesday, there was a hacknight 
> > > > > announced, but the wiki hasn't been updated.
> > > > > 
> > > > > Also, it's been announced that there'll be a monthly series of 
> > > > > installfests, but this month's installfest is booked out. 
> > > > > http://www.meetup.com/Ruby-On-Rails-Oceania-Sydney/events/109188632/ 
> > > > > 
> > > > > Andrew 
> > > > > 
> > > > > -- 
> > > > > You received this message because you are subscribed to the Google 
> > > > > Groups "Ruby or Rails Oceania" group.
> > > > > To unsubscribe from this group and stop receiving emails from it, 
> > > > > send an email to rails-oceania+unsubscr...@googlegroups.com 
> > > > > (mailto:rails-oceania%2bunsubscr...@googlegroups.com).
> > > > > To post to this group, send email to rails-oceania@goog

[rails-oceania] Re: Inviting corporate reps to RoRo ...

2013-04-08 Thread Ben Schwarz

I think its best to leave to the discretion of the organiser of said group 
— they do an incredible job to help speakers get their content out… I can't 
remember the last time we had an issue with some nasty commercial talk 
being given… so that seems like its working well already.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Trying to implement per tenant ID's

2013-04-03 Thread Ben Hoskings

Firstly, I'd keep this display ID (maybe "member ID") separate from users.id.
Any non-standard behaviour there is asking for trouble. There's a lot of
convention built up in activerecord around having a single artificial
integer PK, and veering from this standard isn't worth the trouble it
causes. (We used some composite PKs for a time at TC as part of a migration
strategy, and they were very inconvenient to work with.)

I'd recommend having a unique users.id column like normal, and then a
separate member_id that you use for routing, which is unique within each
tenant (enforced in the DB).

I'd add a unique index to the users table on (tenant_id, member_id):

add_index :users, [:tenant_id, :member_id], unique: true

Then I'd add a validation in the model, for reasonable error messages (the
real "validation" is done by the DB's unique index):

validates :member_id, presence: true, uniqueness: {scope: :tenant_id}

Then I'd auto-populate that field before the model's validation happens.

before_validation :assign_member_id_if_required

def assign_member_id_if_required
  self.member_id ||= begin
max_member_id = tenant.users.order('member_id
DESC').limit(1).pluck(:member_id).first
(max_member_id || 0) + 1
  end
end

That will query efficiently:

SELECT "users"."member_id" FROM "users" WHERE "users"."tenant_id" =
12345 ORDER BY member_id DESC LIMIT 1

- Ben


On 3 April 2013 20:29, Rich Buggy  wrote:

> Hi everyone,
>
> I'm building a multi-tenant application and I'd like some of the ID's to
> be per tenant. It's using the path based multi-tenant approach. For example
> - /:account/invoices/:id
>
> I've got the routing working correctly but the ID's are being generated
> automatically so they are unique across the application, not just the
> tenant. This isn't ideal because each tenant should start from 1.
>
> I already store the next id in the tenant table so they can choose to
> start from a number other than 1. This is important as someone with
> existing data may decide to not start from 1. I think there are a number of
> ways I can deal with this.
>
> 1. If I was doing this without rails I'd make the tenant_id + id a
> composite field and set the id manually when creating the record. Is there
> are an easy way to do this with rails?
>
> 2. I could add number field and accept that number != id. This is easy but
> ugly because /demo/invoices/123456 could be invoice 1
>
> 3. I could add a number field and try to muck with the routing so it used
> number instead of id
>
> Does anyone know of a good guide or blog post on how to do this?
>
> Rich
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rails-oceania+unsubscr...@googlegroups.com.
> To post to this group, send email to rails-oceania@googlegroups.com.
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Cheers
Ben

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[rails-oceania] Re: [Sydney] Introduce myself

2013-04-01 Thread Ben Schwarz

Marcos, 

This is a great place to introduce yourself. 
Keep an eye on this list to watch for the monthly sydney ruby meetup (aka, 
RORO) and also for job postings.

Good luck!

On Monday, 1 April 2013 13:45:53 UTC+11, marcos Bellucci wrote:
>
> Hello guys, i am Marcos a computing engineer from Uruguay ( Latin America 
> ).
> I want to visit Sydney for a few months to improve my english.
> So i would like to get an english scolarship, and at the same time get a 
> ruby job to survive :)
> Can anyone help me to find one?
> Maybe recommending related sites.
>
> (i apologize if this is not the proper comunication way)
>
> best regards!
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Re: How to calculate an hourly, contractual rate

2013-03-17 Thread Ben Schwarz

Ben, they're two totally different subjects. 
I'm so not getting into one of those "define what you mean" discussion 
threads. 

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Re: How to calculate an hourly, contractual rate

2013-03-17 Thread Ben Taylor

Or we could measure on "how good they are" rather than "how many years they sat 
at a desk".

- Ben


On Monday, 18 March 2013 at 3:39 PM, Ben Schwarz wrote:

> I wouldn't call anyone with less than 10 years experience a senior.  
>  
> In my mind:  
>  
> Junior:   1 – 4 years
> Mid-weight: 5 – 9
> Senior: 10+  
>  
> We're talking not only skill, but mastery of craft and processes.  
>  
>  
> On Monday, 18 March 2013 at 3:35 PM, Michael Pearson wrote:
>  
> > On Mon, Mar 18, 2013 at 3:29 PM, Ashley Pettit  > (mailto:is_ash_is_g...@hotmail.com)> wrote:
> > > $400 day for someone mid level (~2-3 years by my loose definition) is 
> > > pretty rocking stuff in my opinion. Most of my friends are around 24 
> > > years old and I can't quite say any of them earn anything near this! 
> > > (Again disclaimer *you may definitely be worth it* I don't know)  
> >  
> > IMO 2-3 years isn't mid level.
> >  
> > Mid level is (years that you've been working in the industry) / 2.
> >  
> > Junior is (years ..) / 3
> >  
> > Senior is max( (years ...) - 1, 3)
> >  
> > --  
> > Michael Pearson
> >  
> > --  
> > You received this message because you are subscribed to a topic in the 
> > Google Groups "Ruby or Rails Oceania" group.
> > To unsubscribe from this topic, visit 
> > https://groups.google.com/d/topic/rails-oceania/aJUEhoE89mo/unsubscribe?hl=en.
> > To unsubscribe from this group and all its topics, send an email to 
> > rails-oceania+unsubscr...@googlegroups.com 
> > (mailto:rails-oceania+unsubscr...@googlegroups.com).
> > To post to this group, send email to rails-oceania@googlegroups.com 
> > (mailto:rails-oceania@googlegroups.com).
> > Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >   
> >   
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rails-oceania+unsubscr...@googlegroups.com 
> (mailto:rails-oceania+unsubscr...@googlegroups.com).
> To post to this group, send email to rails-oceania@googlegroups.com 
> (mailto:rails-oceania@googlegroups.com).
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>   
>   

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Re: How to calculate an hourly, contractual rate

2013-03-17 Thread Ben Schwarz

I wouldn't call anyone with less than 10 years experience a senior.  

In my mind:  

Junior:   1 – 4 years
Mid-weight: 5 – 9
Senior: 10+  

We're talking not only skill, but mastery of craft and processes.  


On Monday, 18 March 2013 at 3:35 PM, Michael Pearson wrote:

> On Mon, Mar 18, 2013 at 3:29 PM, Ashley Pettit  (mailto:is_ash_is_g...@hotmail.com)> wrote:
> > $400 day for someone mid level (~2-3 years by my loose definition) is 
> > pretty rocking stuff in my opinion. Most of my friends are around 24 years 
> > old and I can't quite say any of them earn anything near this! (Again 
> > disclaimer *you may definitely be worth it* I don't know)  
>  
> IMO 2-3 years isn't mid level.
>  
> Mid level is (years that you've been working in the industry) / 2.
>  
> Junior is (years ..) / 3
>  
> Senior is max( (years ...) - 1, 3)
>  
> --  
> Michael Pearson
>  
> --  
> You received this message because you are subscribed to a topic in the Google 
> Groups "Ruby or Rails Oceania" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/rails-oceania/aJUEhoE89mo/unsubscribe?hl=en.
> To unsubscribe from this group and all its topics, send an email to 
> rails-oceania+unsubscr...@googlegroups.com 
> (mailto:rails-oceania+unsubscr...@googlegroups.com).
> To post to this group, send email to rails-oceania@googlegroups.com 
> (mailto:rails-oceania@googlegroups.com).
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>   
>   

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] RedDotRubyConf 2013

2013-03-16 Thread Ben Caldwell

Nearly missed the early bird! Thanks for the reminder :)

On Thursday, March 14, 2013 12:51:20 PM UTC+8, Winston Teo wrote:
>
> Hi Guys,
>
> Just want to let you all know that RedDotRubyConf early bird is going to 
> end soon. Have you bought your tix? http://www.reddotrubyconf.com
>
> Hope to see you guys in June!
>
> Thank you!
>
> Cheers,
> Winston
>
> On Thursday, 21 February 2013 00:28:26 UTC+8, Winston Teo wrote:
>>
>> Hi Daryl,
>>
>> Warren gave a pretty good answer. Ibis Bencoolen was the hotel of choice 
>> for the last two years but we didn't get any preferential rates for that. 
>>
>> We will be approaching hotels soon to arrange for lodging for our invited 
>> speakers and I'll update if we manage to get any bulk discount rates.
>>
>> Thank you for your support!
>>
>> Cheers,
>> Winston
>>
>>
>> On Wednesday, 20 February 2013 08:08:07 UTC+8, Daryl wrote:
>>>
>>> Actually, the Ibis looks like a pretty solid choice from TripAdvisor etc 
>>> (also if you book 30 days ahead you can get a 30% discount if you book 
>>> direct with Ibis on 
>>> http://www.accorhotels.com/gb/booking/rates.shtml?packId=58910310737which 
>>> lowers the cost a titch.).
>>>
>>> thanks Warren!
>>> Daryl.
>>>
>>>
>>>
>>> On Wed, Feb 20, 2013 at 10:44 AM, Warren Seen wrote:
>>>
 It's probably easiest to stay somewhere in the city close to one of the 
 MRT stations on the city or east/west lines, you'll have a wider choice of 
 hotels and easier access to the city itself then.

 The Ibis on Bencoolen is a good option based on my experience, and has 
 free wifi. Looks like it's around AU$130/night at the time the conference 
 is on, but Singapore seems to have a hotel for every budget :) 
 http://wego.com.au has a pretty good search engine for hotels there.

 On 20/02/2013, at 9:58 AM, Daryl Manning  wrote:

 Hey Winston!

 (Already signed up!). 

 I was wondering whether there is any recommended hotel or such nearby 
 for the conference for attendees. Especially if R.R negotiated conference 
 rates and for those whose first time it is in Singapore, it would be very 
 helpful logistically.

 thanks !
 Daryl.


 On Wed, Feb 20, 2013 at 12:59 AM, Winston Teo wrote:

> Hi Guys!
>
> I am Winston, organizer of RedDotRubyConf 2013. You might be more 
> familiar with Andy Croll who ran the last two RDRC, but he's currently 
> back 
> in UK waiting for the arrival of his twins. So.. I (and a few others) 
> volunteered ourselves for RDRC this year.
>
> RedDotRubyConf is the annual Ruby conference of Singapore and we are 
> in our third edition. It will be on 7-8 June 2013 at Matrix (Biopolis). 
> Please refer to http://reddotrubyconf.com for more details.
>
> We have a great list of speakers already lined up:
>  
> - Jim Weirich
> - Josè Valim
> - Aaron Patterson
> - Steve Klabnik
> - Ola Bini
> - Akira Matsuda
> - Prem Sichanugrist (not yet up on the website)
>  
> So.. Get your tickets early, like now (
> http://reddotrubyconf.com/registrations/new)! 
>  
> Or, if you have a great idea to share, you can submit a talk to our 
> CFP too (http://reddotrubyconf.com/call_for_proposals).
>  
> Drop me an email if you have any questions - win...@neo.com and 
> follow @reddotrubyconf for more updates.
>  
> Thank you! Hope to see you guys in SG!
>  
> Cheers,
> Winston
>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to rails-oceani...@googlegroups.com.
> To post to this group, send email to rails-...@googlegroups.com.
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
>


 -- 
 You received this message because you are subscribed to the Google 
 Groups "Ruby or Rails Oceania" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to rails-oceani...@googlegroups.com.
 To post to this group, send email to rails-...@googlegroups.com.
 Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  


  -- 
 You received this message because you are subscribed to the Google 
 Groups "Ruby or Rails Oceania" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to rails-oceani...@googlegroups.com.
 To post to this group, send email to rails-...@googlegroups.com.
 Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
 For more options, visit https://group

Re: [rails-oceania] Re: How to calculate an hourly, contractual rate

2013-03-14 Thread Ben Taylor

These aren't abnormal positions (AFAIK). A Ph. D would get higher. From 
discreet conversations with friends who took graduate roles between 4 years ago 
until now the going rate is around 60-80k. All have Degrees from the Group of 8 
in either Computer Science, Engineering or IT and are working in either 
consulting or development roles. Example companies:

 * IBM
 * Google

 * Deloitte Digital
 * Macquarie Bank
 * Atlassian
 * Commonwealth Bank
 * NAB

FYI the ones I know who were super capable (PhDs and such) often got taken by 
American companies for >$100K graduate positions. 

- Ben


On Friday, 15 March 2013 at 4:27 PM, Michael Pearson wrote:

> On Fri, Mar 15, 2013 at 4:17 PM, Ben Taylor  (mailto:m...@taybenlor.com)> wrote:
> > Sorry, I meant before tax. But yeah $70k before tax is what I've seen 
> > recent CS graduates go into.
> > 
>  
> That's how I first read it, and my response is still the same.
> 
> Did they have Ph.Ds? Had they developed a popular JavaScript framework from 
> scratch? Was the hiring company desperate for hires because they'd sullied 
> their name in the local community? Did the graduate have a specialist skill? 
> Were they a short-lived, burn-brightly-then-flip overfunded startup? Can I 
> have my salary for the first five or six years of my career in IT 
> retro-actively adjusted to this new entry rate, pretty please? 
> 
> -- 
> Michael Pearson
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rails-oceania+unsubscr...@googlegroups.com 
> (mailto:rails-oceania+unsubscr...@googlegroups.com).
> To post to this group, send email to rails-oceania@googlegroups.com 
> (mailto:rails-oceania@googlegroups.com).
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Re: How to calculate an hourly, contractual rate

2013-03-14 Thread Ben Taylor

You also need to take into account lack of holiday pay, sick leave and job 
security.

$70k after tax is what you would expect from a graduate IT position. And with 
contracting you don't get the perks of a normal job.

- Ben


On Friday, 15 March 2013 at 3:59 PM, Dan Cheail wrote:

> Nicholas: 
> 
> How do you figure? $50 / hour for a 40 hour week comes out to a gross of 
> $104,000. Less  11% super contribution, that's still a gross of ~$95k, (~$70k 
> after tax)
> 
> -- 
> Dan Cheail, Geek
> 0402 114 697
> 
> 
> On Friday, 15 March 2013 at 3:31 PM, Nicholas Faiz wrote:
> 
> > Ashley, 
> > 
> > Those rates are too low. The idea of the post was to let people know how to 
> > fairly identify a rate of pay.
> > 
> > Using the original calculation for an hourly rate (see the original post), 
> > that's saying a mid level developer would be charging $50 an hour, which 
> > maps to earning about 50 k (super included) per annum in a full-time role. 
> > I don't think you'd see any full-time mid level Rails roles offered for 
> > that.
> > 
> > Nicholas
> > 
> > On Friday, March 15, 2013 2:36:03 PM UTC+11, Ashley Pettit wrote:
> > > Hey guys,
> > > 
> > > People are often just plainly asking me what they should charge.
> > > 
> > > Here's my two cents for contracts > 3 months and 40 hrs /week. 
> > > 
> > > Mid-level developer ~$400 day.
> > > 
> > > Senior-level ~$600 day.
> > > 
> > > As Nick said if you want more you need to have to really think about the 
> > > business. How to improve it. Invest in the business and give suggestions 
> > > on how they can be more profitable.
> > > 
> > > Also you need to value your service and have connections with people who 
> > > really value what you do. 
> > > 
> > > Chaio,
> > > 
> > > Ash 
> > 
> > -- 
> > You received this message because you are subscribed to the Google Groups 
> > "Ruby or Rails Oceania" group.
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to rails-oceania+unsubscr...@googlegroups.com 
> > (mailto:rails-oceania+unsubscr...@googlegroups.com).
> > To post to this group, send email to rails-oceania@googlegroups.com 
> > (mailto:rails-oceania@googlegroups.com).
> > Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >  
> >  
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rails-oceania+unsubscr...@googlegroups.com 
> (mailto:rails-oceania+unsubscr...@googlegroups.com).
> To post to this group, send email to rails-oceania@googlegroups.com 
> (mailto:rails-oceania@googlegroups.com).
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[rails-oceania] Re: Recommendation for a distributed CI service

2013-03-13 Thread Ben Schwarz

You know, I reckon if you asked Konstantin or Josh super nicely, you might 
get access to Travis-CI private.




On Sunday, 27 May 2012 22:51:28 UTC+10, Trung LE wrote:
>
> Hi all
>
> I am looking for a free/paid online CI service that is similar to Travis 
> CI but support private GitHub repo for my company. I really appreciate if 
> someone could share me a recommendation.
>
> Many thanks
>
> Trung
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Ruby/Rails in the Bay Area

2013-02-28 Thread ben wiseley

Andrew,

I moved to SF in Nov.  The company I work for causes.com has parties fairly
often in our office (we're about 60 people) that are attended by many Ruby
guys (we're a Rails shop).  (We're also hiring... we've got 3 Aussies
working for us and sponsor visas).  21st floor, down town, tons of booze,
open balcony... pretty fun.

I haven't been to their meetup yet but the local Ruby group is
http://www.sfruby.info/

Drop me a line and we'll take you out while you're here.  You're welcome to
come hang out at the office too if you want a desk for the day.

-ben
415-405-5410


On Thu, Feb 28, 2013 at 12:49 AM, Andrew Grimm wrote:

> I tried meetup.com for Ruby in Sydney, and RORO wasn't listed.
> Likewise, when I tried for Sendai, or Sapporo, or Osaka, I didn't get
> Tohoku on Rails, Ruby Sapporo, or Minami.rb . The only hit I did get
> was when trying for Ruby in Tokyo, and that got me Tokyo Rails, but
> not Asakusa.rb
>
> So it's not bulletproof.
>
> Another site to check is http://rubyusergroups.org/
>
> Incidentally, when I searched for Ruby in Sydney with meetup.com , I
> came across Sydney on Rails http://www.meetup.com/Sydney-on-Rails/ -
> anyone know what that group's like?
>
> Andrew
>
> On Thu, Feb 28, 2013 at 12:50 PM, Craig Read 
> wrote:
> > Andrew,
> >
> > I asked a friend who lives (and codes) in the bay area.
> > He sent me this link.  I'm somewhat surprised he didn't send me a link to
> > http://lmgtfy.com/.
> >
> > Craig...
> >
> >
> > On Thu, Feb 28, 2013 at 11:18 AM, Andrew Harvey 
> wrote:
> >>
> >> I've just found out that I'm going to be in the bay area for a couple of
> >> days in mid-march, and was looking to connect a bit with the ruby/rails
> >> communities there.
> >>
> >> Does anyone have suggestions for meet ups or events to go to or people
> to
> >> meet?
> >>
> >> Feel free to contact me off list if you prefer :)
> >>
> >> Andrew
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups
> >> "Ruby or Rails Oceania" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an
> >> email to rails-oceania+unsubscr...@googlegroups.com.
> >> To post to this group, send email to rails-oceania@googlegroups.com.
> >> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> >> For more options, visit https://groups.google.com/groups/opt_out.
> >>
> >>
> >
> >
> >
> > --
> > Craig Read
> >
> > @Catharz
> > https://github.com/Catharz
> > http://stackoverflow.com/users/158893/catharz
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Ruby or Rails Oceania" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to rails-oceania+unsubscr...@googlegroups.com.
> > To post to this group, send email to rails-oceania@googlegroups.com.
> > Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rails-oceania+unsubscr...@googlegroups.com.
> To post to this group, send email to rails-oceania@googlegroups.com.
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Help send Konstantin to Magma conf

2013-02-24 Thread Ben Schwarz

Now we've established that the form is secure, and that Konstantin is a 
baller—send some bucks. 


On Sunday, 24 February 2013 19:51:44 UTC+11, pythonic wrote:
>
>
> Nah, the form's submitted via https, served by Stripe.
>
>
> You are assuming the form action is not modified by a MITM.
>
> Thanks,
>
> Nicholas
>
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Help send Konstantin to Magma conf

2013-02-23 Thread Ben Schwarz

Good point Alex, David already kinda covered it, but—
Konstantin flew all the way from Berlin to speak at Rubyconf in Melbourne 
last week, where he gave a great talk. 

Magmaconf is a community run event, and seeing as we just had such a 
fantastic community run event locally, I figured we should share the love. 

On Sunday, February 24, 2013 6:15:50 PM UTC+11, Alex Bayley wrote:
>
> On 24/02/13 6:11 PM, Ben Schwarz wrote: 
> > Our Mexican ruby buddies run a conference called Magma conf, they've 
> > been trying to get Konstantin to Mexico since the conference started 3 
> > years ago. 
> > So, after all the love of Rubyconf in Australia, why not donate some 
> > bucks to help make another community run event absolutely rad? 
>
> Who is Konstantin and why would I want to do this?  As a relative newbie 
> I have no idea why I would want to give money to this, and the website 
> doesn't tell me anything. 
>
> A. 
>
>
> -- 
> Alex "Skud" Bayley 
> sk...@growstuff.org  
> http://growstuff.org/ 
> For personal stuff, please use sk...@infotrope.net  
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[rails-oceania] Help send Konstantin to Magma conf

2013-02-23 Thread Ben Schwarz

Our Mexican ruby buddies run a conference called Magma conf, they've been 
trying to get Konstantin to Mexico since the conference started 3 years 
ago. 
So, after all the love of Rubyconf in Australia, why not donate some bucks 
to help make another community run event absolutely rad? 

http://bring-konstantin-to.magmaconf.com

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] More vulnerabilities today: rails & json need updates

(But then, most popular gems would end up flagged as "unsafe". :) For a
start, every version of rails before 3.2.12 would be "unsafe" as of today.)


On 12 February 2013 11:25, Ben Hoskings  wrote:

> I think it's always best to not yank the gem, but I like the idea of
> having some sort of annotation. Bundler could then exclude them by default,
> with an --include-unsafe option to pull them in when required.
>
> - Ben
>
>
>
> On 12 February 2013 11:21, Simon Russell  wrote:
>
>> That situation actually makes me wonder whether it wouldn't be good if
>> RubyGems warned you if you were installing a version of a gem that had
>> known security problems.  (Or perhaps in serious situations, the gem
>> publisher could yank them...)
>>
>> I'd certainly find it useful if bundler would tell me it was knowingly
>> installing an old version of a gem because of a dependency.
>>
>>
>> On Tue, Feb 12, 2013 at 11:16 AM, Ben Hoskings  wrote:
>>
>>> That's a good option too.
>>>
>>> My intent with the version constraint isn't to lock it, so much as to
>>> make it explicit that the gem shouldn't be rolled back in the future. That
>>> is, that there's a specific reason it's at that version, aside from that
>>> being the latest version at the time it was incorporated.
>>>
>>> - Ben
>>>
>>>
>>>
>>> On 12 February 2013 09:48, Jon Rowe  wrote:
>>>
>>>> If you feel the need to lock to a specific version rather than just
>>>> `bundle update json` then ~> is safer than >= as it will only allow patch
>>>> version updates.
>>>>
>>>> Jon Rowe
>>>> -
>>>> m...@jonrowe.co.uk
>>>> jonrowe.co.uk
>>>>
>>>> On Tuesday, 12 February 2013 at 09:38, Ben Hoskings wrote:
>>>>
>>>> There are three. Here they are with tl-dr.
>>>>
>>>> 1)
>>>> https://groups.google.com/forum/?hl=en&fromgroups=#!topic/rubyonrails-security/AFBKNY7VSH8
>>>> #attr_protected can be circumvented in controllers.
>>>> Fixed in rails 3.2.12, 3.1.11, 2.3.17.
>>>>
>>>> 2)
>>>> https://groups.google.com/forum/?hl=en&fromgroups=#!topic/rubyonrails-security/KtmwSbEpzrU
>>>> #serialize calls in models can be exploited to execute remote code.
>>>> 3.1.0 and newer are not affected.
>>>> Fixed in rails 2.3.17. There is no release for 3.0.x because of policy:
>>>> you'll have to manually apply the patch.
>>>>
>>>> 3)
>>>> https://groups.google.com/forum/?hl=en&fromgroups=#!topic/rubyonrails-security/4_YvCpLzL58
>>>> There's a denial of service and unsafe object creation bug using
>>>> 'json_class' in json.gem.
>>>> Fixed in json 1.7.7, 1.6.8, 1.5.5.
>>>> N.B. You have to update json.gem separately to rails to ensure you're
>>>> safe.
>>>>
>>>>
>>>> For anyone unsure, the easiest way to update is to lock out the old
>>>> versions in your gemfile and then `bundle update`. For example:
>>>>
>>>> 1) Check Gemfile.lock for 'json' and note the version. (e.g. say you
>>>> had json-1.7.6, as we did.)
>>>> 2) Add or update the 'json' entry in your Gemfile to the safe version
>>>> corresponding to your minor version, as follows:
>>>> gem 'json', '>= 1.7.7'
>>>> 3) Run `bundle update json`
>>>> 4) Run specs
>>>> 5) SHIP IT
>>>>
>>>>
>>>> Cheers
>>>> Ben
>>>>
>>>>  --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Ruby or Rails Oceania" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to rails-oceania+unsubscr...@googlegroups.com.
>>>> To post to this group, send email to rails-oceania@googlegroups.com.
>>>> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>
>>>>
>>>>
>>>>
>>>>  --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Ruby or Rails Oceania" group.
>>>> To unsubscribe from this group and

Re: [rails-oceania] More vulnerabilities today: rails & json need updates

I think it's always best to not yank the gem, but I like the idea of having
some sort of annotation. Bundler could then exclude them by default, with
an --include-unsafe option to pull them in when required.

- Ben



On 12 February 2013 11:21, Simon Russell  wrote:

> That situation actually makes me wonder whether it wouldn't be good if
> RubyGems warned you if you were installing a version of a gem that had
> known security problems.  (Or perhaps in serious situations, the gem
> publisher could yank them...)
>
> I'd certainly find it useful if bundler would tell me it was knowingly
> installing an old version of a gem because of a dependency.
>
>
> On Tue, Feb 12, 2013 at 11:16 AM, Ben Hoskings  wrote:
>
>> That's a good option too.
>>
>> My intent with the version constraint isn't to lock it, so much as to
>> make it explicit that the gem shouldn't be rolled back in the future. That
>> is, that there's a specific reason it's at that version, aside from that
>> being the latest version at the time it was incorporated.
>>
>> - Ben
>>
>>
>>
>> On 12 February 2013 09:48, Jon Rowe  wrote:
>>
>>> If you feel the need to lock to a specific version rather than just
>>> `bundle update json` then ~> is safer than >= as it will only allow patch
>>> version updates.
>>>
>>> Jon Rowe
>>> -
>>> m...@jonrowe.co.uk
>>> jonrowe.co.uk
>>>
>>> On Tuesday, 12 February 2013 at 09:38, Ben Hoskings wrote:
>>>
>>> There are three. Here they are with tl-dr.
>>>
>>> 1)
>>> https://groups.google.com/forum/?hl=en&fromgroups=#!topic/rubyonrails-security/AFBKNY7VSH8
>>> #attr_protected can be circumvented in controllers.
>>> Fixed in rails 3.2.12, 3.1.11, 2.3.17.
>>>
>>> 2)
>>> https://groups.google.com/forum/?hl=en&fromgroups=#!topic/rubyonrails-security/KtmwSbEpzrU
>>> #serialize calls in models can be exploited to execute remote code.
>>> 3.1.0 and newer are not affected.
>>> Fixed in rails 2.3.17. There is no release for 3.0.x because of policy:
>>> you'll have to manually apply the patch.
>>>
>>> 3)
>>> https://groups.google.com/forum/?hl=en&fromgroups=#!topic/rubyonrails-security/4_YvCpLzL58
>>> There's a denial of service and unsafe object creation bug using
>>> 'json_class' in json.gem.
>>> Fixed in json 1.7.7, 1.6.8, 1.5.5.
>>> N.B. You have to update json.gem separately to rails to ensure you're
>>> safe.
>>>
>>>
>>> For anyone unsure, the easiest way to update is to lock out the old
>>> versions in your gemfile and then `bundle update`. For example:
>>>
>>> 1) Check Gemfile.lock for 'json' and note the version. (e.g. say you had
>>> json-1.7.6, as we did.)
>>> 2) Add or update the 'json' entry in your Gemfile to the safe version
>>> corresponding to your minor version, as follows:
>>> gem 'json', '>= 1.7.7'
>>> 3) Run `bundle update json`
>>> 4) Run specs
>>> 5) SHIP IT
>>>
>>>
>>> Cheers
>>> Ben
>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "Ruby or Rails Oceania" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to rails-oceania+unsubscr...@googlegroups.com.
>>> To post to this group, send email to rails-oceania@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>>
>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "Ruby or Rails Oceania" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to rails-oceania+unsubscr...@googlegroups.com.
>>> To post to this group, send email to rails-oceania@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>>
>>
>>
>>
>> --
>> Cheers
>> Ben
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Ruby or Rails Oceania" group.
>>

Re: [rails-oceania] More vulnerabilities today: rails & json need updates

That's a good option too.

My intent with the version constraint isn't to lock it, so much as to make
it explicit that the gem shouldn't be rolled back in the future. That is,
that there's a specific reason it's at that version, aside from that being
the latest version at the time it was incorporated.

- Ben



On 12 February 2013 09:48, Jon Rowe  wrote:

> If you feel the need to lock to a specific version rather than just
> `bundle update json` then ~> is safer than >= as it will only allow patch
> version updates.
>
> Jon Rowe
> -
> m...@jonrowe.co.uk
> jonrowe.co.uk
>
> On Tuesday, 12 February 2013 at 09:38, Ben Hoskings wrote:
>
> There are three. Here they are with tl-dr.
>
> 1)
> https://groups.google.com/forum/?hl=en&fromgroups=#!topic/rubyonrails-security/AFBKNY7VSH8
> #attr_protected can be circumvented in controllers.
> Fixed in rails 3.2.12, 3.1.11, 2.3.17.
>
> 2)
> https://groups.google.com/forum/?hl=en&fromgroups=#!topic/rubyonrails-security/KtmwSbEpzrU
> #serialize calls in models can be exploited to execute remote code.
> 3.1.0 and newer are not affected.
> Fixed in rails 2.3.17. There is no release for 3.0.x because of policy:
> you'll have to manually apply the patch.
>
> 3)
> https://groups.google.com/forum/?hl=en&fromgroups=#!topic/rubyonrails-security/4_YvCpLzL58
> There's a denial of service and unsafe object creation bug using
> 'json_class' in json.gem.
> Fixed in json 1.7.7, 1.6.8, 1.5.5.
> N.B. You have to update json.gem separately to rails to ensure you're safe.
>
>
> For anyone unsure, the easiest way to update is to lock out the old
> versions in your gemfile and then `bundle update`. For example:
>
> 1) Check Gemfile.lock for 'json' and note the version. (e.g. say you had
> json-1.7.6, as we did.)
> 2) Add or update the 'json' entry in your Gemfile to the safe version
> corresponding to your minor version, as follows:
> gem 'json', '>= 1.7.7'
> 3) Run `bundle update json`
> 4) Run specs
> 5) SHIP IT
>
>
> Cheers
> Ben
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rails-oceania+unsubscr...@googlegroups.com.
> To post to this group, send email to rails-oceania@googlegroups.com.
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rails-oceania+unsubscr...@googlegroups.com.
> To post to this group, send email to rails-oceania@googlegroups.com.
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Cheers
Ben

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] More vulnerabilities today: rails & json need updates

Good call.

I commit with `git add --patch` (`gap`) and `git commit -v` (`gc`) so I
always see the diffs I'm committing, and that stuff can't slip through.

- Ben



On 12 February 2013 09:53, Michael Pearson  wrote:

> On Tue, Feb 12, 2013 at 9:38 AM, Ben Hoskings  wrote:
>
>>
>> 1) Check Gemfile.lock for 'json' and note the version. (e.g. say you had
>> json-1.7.6, as we did.)
>> 2) Add or update the 'json' entry in your Gemfile to the safe version
>> corresponding to your minor version, as follows:
>> gem 'json', '>= 1.7.7'
>> 3) Run `bundle update json`
>> 4) Run specs
>>
>
> 4.5) Run 'git diff Gemfile.lock' to ensure that only the things that you
> thought should update updated (I've run 'bundle update' when I meant to run
> 'bundle update gemname' before)
>
>
>> 5) SHIP IT
>>
>>
>
> --
> Michael Pearson
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rails-oceania+unsubscr...@googlegroups.com.
> To post to this group, send email to rails-oceania@googlegroups.com.
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Cheers
Ben

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[rails-oceania] More vulnerabilities today: rails & json need updates

There are three. Here they are with tl-dr.

1)
https://groups.google.com/forum/?hl=en&fromgroups=#!topic/rubyonrails-security/AFBKNY7VSH8
#attr_protected can be circumvented in controllers.
Fixed in rails 3.2.12, 3.1.11, 2.3.17.

2)
https://groups.google.com/forum/?hl=en&fromgroups=#!topic/rubyonrails-security/KtmwSbEpzrU
#serialize calls in models can be exploited to execute remote code.
3.1.0 and newer are not affected.
Fixed in rails 2.3.17. There is no release for 3.0.x because of policy:
you'll have to manually apply the patch.

3)
https://groups.google.com/forum/?hl=en&fromgroups=#!topic/rubyonrails-security/4_YvCpLzL58
There's a denial of service and unsafe object creation bug using
'json_class' in json.gem.
Fixed in json 1.7.7, 1.6.8, 1.5.5.
N.B. You have to update json.gem separately to rails to ensure you're safe.

For anyone unsure, the easiest way to update is to lock out the old
versions in your gemfile and then `bundle update`. For example:

1) Check Gemfile.lock for 'json' and note the version. (e.g. say you had
json-1.7.6, as we did.)
2) Add or update the 'json' entry in your Gemfile to the safe version
corresponding to your minor version, as follows:
gem 'json', '>= 1.7.7'
3) Run `bundle update json`
4) Run specs
5) SHIP IT

Cheers
Ben

--
You received this message because you are subscribed to the Google Groups "Ruby
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Understanding Brixen's comments about Ruby security

2013-02-08 Thread Ben Hoskings

I think the difference is that in ruby land, "YAML.load" is a pretty standard 
thing to do. Operating in the normal way, it's an unsafe operation on 
non-trusted input. That's not true of a language like Haskell, where you have 
to explicitly turn on cowboy mode before anything unsafe can happen. Any harm 
it could do would be a side-effect, which the compiler has guaranteed will not 
happen.

I strongly agree with Mark's point about not doing any more than is necessary 
at any point. Gemspecs should be a literal-data-only subset of YAML (i.e. they 
should be JSON); marshaling things shouldn't have any connection to param 
parsing; models shouldn't be able to see the request; the user account on 
rubygems that processes incoming gemspecs shouldn't have read access to 
./config/, and so on.

Whether it's in code or in ops or overall design, the good solutions arise 
through forcing separation. It's good design anyway, because a decoupled system 
is more testable.

In ruby this separation has to be achieved by convention, not the compiler, but 
I think there's still a lot we can do. In separating concerns and pushing hard 
in the direction of 'lo-fi', you shrink the attackable surface.

- Ben

Sent from my iPhone

On 09/02/2013, at 4:36 PM, Nicholas Jefferson  wrote:

>> in the context I mentioned
> 
> The relevant context here has web developers who thought nothing of calling 
> "YAML.load", and would think nothing of calling "eval" from a function with 
> an IO annotation. In this context an arbitrary code execution vulnerability 
> in any Haskell web framework is only a few lines of code away.
> 
> Thanks,
> 
> Nicholas
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rails-oceania+unsubscr...@googlegroups.com.
> To post to this group, send email to rails-oceania@googlegroups.com.
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Understanding Brixen's comments about Ruby security

2013-02-08 Thread Ben Hoskings

No, he doesn't mean that (if I'm interpreting him right). I think he means ruby 
the ecosystem and community, not ruby the language.

When a flaw that huge is found in rails it reflects on ruby the ecosystem and 
community as a whole, whether that's fair or not.

The implication is that the flaw existed and went unpatched for so long because 
the ruby community is culturally too relaxed with security. Again, whether 
that's fair or not is another question.

But I think he's right that it only adds to existing criticisms (that we're 
cavalier, and value glitz over rigour).

- Ben


Sent from my iPhone

On 08/02/2013, at 9:32 PM, Andrew Grimm  wrote:

> In the latest Ruby Rogues podcast, @Brixen (formerly Brian Ford, now
> Brian Shirai) said
> 
>> But I caution people who think, “It’s working okay. Let’s just do more of 
>> this.” I caution that, that is not necessarily going to be
>> sufficient. And I will point to a couple things. What I’ve seen is talents 
>> bleed away from Ruby to other languages because Ruby
>> couldn’t do things like concurrency well. These recent exploits in Rails and 
>> stuff are of great concern. We already have strikes
>> against us as a Ruby language for a bunch of reasons and what we really 
>> don’t need is big companies who pay developers to say,
>> “You know what? We’re not using Ruby. There’s no Ruby going to be on my 
>> server because I’m not having someone exploit my
>> servers.” Point and click, and you have a remote shell, right?
> 
> Would I be correct in interpreting him as saying that the recent YAML
> exploits with Rails indicate a problem with Ruby, rather than just
> Rails? That in a more secure programming language, even if the web
> development framework stuffed up, the hackers wouldn't be able to
> execute arbitrary shell code?
> 
> Andrew
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rails-oceania+unsubscr...@googlegroups.com.
> To post to this group, send email to rails-oceania@googlegroups.com.
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rails-oceania+unsubscr...@googlegroups.com.
To post to this group, send email to rails-oceania@googlegroups.com.
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [rails-oceania] Rails Security Vulnerability

2013-01-08 Thread Ben Hoskings

Thanks for posting this, John.

All: note well that unlike the fix in 3.2.10 which turned out to have a limited 
impact, this one (CVE-2013-0156) is serious business.

Bumping production to 3.2.11 (or turning off the XML params parser in an 
initializer) should be priority #1 for everyone today :)

- Ben


Sent from my iPhone

On 09/01/2013, at 9:26 AM, Jon Rowe  wrote:

> Hey Rubyists
> 
> In case you've missed this mornings "news", there's a *new* Rails 
> vulnerability which requires patching:
> 
> https://groups.google.com/forum/#!topic/rubyonrails-security/61bkgvnSGTQ/discussion
> 
> Just FYI you know...
> 
> Jon Rowe
> -
> m...@jonrowe.co.uk
> jonrowe.co.uk
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To post to this group, send email to rails-oceania@googlegroups.com.
> To unsubscribe from this group, send email to 
> rails-oceania+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/rails-oceania?hl=en.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To post to this group, send email to rails-oceania@googlegroups.com.
To unsubscribe from this group, send email to 
rails-oceania+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en.

[rails-oceania] Fwd: SQL Injection Vulnerability in Ruby on Rails (CVE-2012-5664)

2013-01-02 Thread Ben Hoskings

Hi all, forwarding for those who aren't on the security list.

This vulnerability looks potentially serious―using finders in this way is 
pretty standard. (I haven't looked into it further than the announcement.)

Cheers
Ben


Begin forwarded message:

> From: Aaron Patterson 
> Date: 3 January 2013 7:22:22 AM AEST
> To: rubyonrails-secur...@googlegroups.com, oss-secur...@lists.openwall.com
> Subject: SQL Injection Vulnerability in Ruby on Rails (CVE-2012-5664)
> Reply-To: rubyonrails-secur...@googlegroups.com
> 
> SQL Injection Vulnerability in Ruby on Rails
> 
> There is a SQL injection vulnerability in Active Record in ALL versions. This 
> vulnerability has been assigned the CVE identifier CVE-2012-5664.
> 
> Versions Affected:  All.
> Not affected:   NONE.
> Fixed Versions: 3.2.10, 3.1.9, 3.0.18
> 
> Impact 
> -- 
> Due to the way dynamic finders in Active Record extract options from method 
> parameters, a method parameter can mistakenly be used as a scope.  Carefully 
> crafted requests can use the scope to inject arbitrary SQL.
> 
> All users running an affected release should either upgrade or use one of the 
> work arounds immediately. 
> 
> Impacted code passes user provided data to a dynamic finder like this:
> 
>  Post.find_by_id(params[:id])
> 
> Releases 
>  
> The  3.2.10, 3.1.9 & 3.0.18 releases are available at the normal locations. 
> 
> Workarounds 
> --- 
> The issue can be mitigated by explicitly converting the parameter to an 
> expected value.  For example, change this:
> 
>  Post.find_by_id(params[:id])
> 
> to this:
> 
>  Post.find_by_id(params[:id].to_s)
> 
> 
> Patches 
> --- 
> To aid users who aren't able to upgrade immediately we have provided patches 
> for the two supported release series and two unsupported versions.  They are 
> in git-am format and consist of a single changeset. 
> 
> * 3-2-dynamic_finder_injection.patch - Patch for 3.2 series
> * 3-1-dynamic_finder_injection.patch - Patch for 3.1 series
> * 3-0-dynamic_finder_injection.patch - Patch for 3.0 series
> * 2-3-dynamic_finder_injection.patch - Patch for 2.3 series
> 
> Please note that only the 3.1.x and 3.2.x series are supported at present.  
> Users of earlier unsupported releases are advised to upgrade as soon as 
> possible as we cannot guarantee the continued availability of security fixes 
> for unsupported releases.
> 
> -- 
> Aaron Patterson
> http://tenderlovemaking.com/
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby on Rails: Security" group.
> To post to this group, send email to rubyonrails-secur...@googlegroups.com.
> To unsubscribe from this group, send email to 
> rubyonrails-security+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/rubyonrails-security?hl=en.
> 
From 9de9b359d0d24f70f0f6c5c58a7ad8750684d456 Mon Sep 17 00:00:00 2001
From: Aaron Patterson 
Date: Sun, 23 Dec 2012 11:07:07 -0800
Subject: [PATCH] CVE-2012-5664 options hashes should only be extracted if
 there are extra parameters

---
 activerecord/lib/active_record/base.rb |6 +-
 activerecord/test/cases/finder_test.rb |   12 
 2 files changed, 17 insertions(+), 1 deletion(-)

diff --git a/activerecord/lib/active_record/base.rb 
b/activerecord/lib/active_record/base.rb
index 461007f..809a38c 100755
--- a/activerecord/lib/active_record/base.rb
+++ b/activerecord/lib/active_record/base.rb
@@ -1897,7 +1897,11 @@ module ActiveRecord #:nodoc:
   # end
   self.class_eval <<-EOS, __FILE__, __LINE__ + 1
 def self.#{method_id}(*args)
-  options = args.extract_options!
+  options = if args.length > #{attribute_names.size}
+  args.extract_options!
+else
+  {}
+end
   attributes = construct_attributes_from_arguments(
 [:#{attribute_names.join(',:')}],
 args
diff --git a/activerecord/test/cases/finder_test.rb 
b/activerecord/test/cases/finder_test.rb
index c779a69..9e3ab92 100644
--- a/activerecord/test/cases/finder_test.rb
+++ b/activerecord/test/cases/finder_test.rb
@@ -66,6 +66,18 @@ end
 class FinderTest < ActiveRecord::TestCase
   fixtures :companies, :topics, :entrants, :developers, :developers_projects, 
:posts, :comments, :accounts, :authors, :customers
 
+  def test_find_by_id_with_hash
+assert_raises(ActiveRecord::StatementInvalid) do
+  Post.find_by_id(:limit => 1)
+end
+  end
+
+  def test_find_by_title_and_id_with_hash
+assert_raises(ActiveRecord::Statemen

Re: [rails-oceania] Is there a way to reuse scopes in a has-many-through association?

2012-12-17 Thread Ben Hoskings

Good catch. The rule is that the #joins call is responsible for naming all the 
tables that the conditions in the merges will reference.

- Ben



On 18/12/2012, at 3:35 PM, Michael Gall  wrote:

> I've been working with this a bit lately, and the 1 point that's kinda 
> brushed over in Ben's post is in this line:
>  Figure.joins(:article => :collaborations
> ).
>   merge(
> Article.drafting)
> 
> 
> If Article.drafting references the Collaborations, then you must use the 
> hashrocket/through notation in the join. It's a bit of a trick because the 
> error message doesn't really help you to fix it.
> 
> Cheers,
> 
> Michael
> 
> 
> 
> On Tue, Dec 18, 2012 at 2:31 PM, Ben Hoskings  wrote:
> >
> > There is indeed, in fact I wrote a post on this very thing a little while 
> > ago :)
> >
> > http://benhoskin.gs/2012/07/04/arel-merge-a-hidden-gem
> >
> > - Ben
> >
> >
> >
> > On 18/12/2012, at 2:17 PM, Iain Beeston  wrote:
> >
> > > I've had an activerecord problem that's been bugging me for a while. If 
> > > you have a has-many-through association, and have scopes defined on the 
> > > "through" model, is it possible to re-use the scopes in the definition of 
> > > the has-many-through? (without copying the where clause of the scope in 
> > > the has-many-through)
> > >
> > > eg.
> > >   • a -> b -> c
> > >   • there is a "blah" scope on b
> > >   • you'd like to define "a has many c's through b, where b.c"
> > >
> > > I've already posted this on stackoverflow with a more full explanation 
> > > and example (but it's had a pretty lukewarm response)
> > >
> > > http://stackoverflow.com/questions/13696045/reusing-activerecord-scopes-on-has-many-through-associations
> > >
> > >
> > > Does anyone have any good suggestions about how to do this in a "DRY" way?
> > >
> > >
> > > Iain
> > >
> > >
> > > --
> > > You received this message because you are subscribed to the Google Groups 
> > > "Ruby or Rails Oceania" group.
> > > To post to this group, send email to rails-oceania@googlegroups.com.
> > > To unsubscribe from this group, send email to 
> > > rails-oceania+unsubscr...@googlegroups.com.
> > > For more options, visit this group at 
> > > http://groups.google.com/group/rails-oceania?hl=en.
> >
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Ruby or Rails Oceania" group.
> > To post to this group, send email to rails-oceania@googlegroups.com.
> > To unsubscribe from this group, send email to 
> > rails-oceania+unsubscr...@googlegroups.com.
> > For more options, visit this group at 
> > http://groups.google.com/group/rails-oceania?hl=en.
> >
> 
> 
> 
> --
> Checkout my new website: http://myachinghead.net
> http://wakeless.net
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To post to this group, send email to rails-oceania@googlegroups.com.
> To unsubscribe from this group, send email to 
> rails-oceania+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/rails-oceania?hl=en.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To post to this group, send email to rails-oceania@googlegroups.com.
To unsubscribe from this group, send email to 
rails-oceania+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en.

Re: [rails-oceania] Is there a way to reuse scopes in a has-many-through association?

2012-12-17 Thread Ben Hoskings

There is indeed, in fact I wrote a post on this very thing a little while ago :)

http://benhoskin.gs/2012/07/04/arel-merge-a-hidden-gem

- Ben



On 18/12/2012, at 2:17 PM, Iain Beeston  wrote:

> I've had an activerecord problem that's been bugging me for a while. If you 
> have a has-many-through association, and have scopes defined on the "through" 
> model, is it possible to re-use the scopes in the definition of the 
> has-many-through? (without copying the where clause of the scope in the 
> has-many-through)
> 
> eg.
>   • a -> b -> c
>   • there is a "blah" scope on b
>   • you'd like to define "a has many c's through b, where b.c"
> 
> I've already posted this on stackoverflow with a more full explanation and 
> example (but it's had a pretty lukewarm response)
> 
> http://stackoverflow.com/questions/13696045/reusing-activerecord-scopes-on-has-many-through-associations
> 
> 
> Does anyone have any good suggestions about how to do this in a "DRY" way?
> 
> 
> Iain
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To post to this group, send email to rails-oceania@googlegroups.com.
> To unsubscribe from this group, send email to 
> rails-oceania+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/rails-oceania?hl=en.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To post to this group, send email to rails-oceania@googlegroups.com.
To unsubscribe from this group, send email to 
rails-oceania+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en.

Re: [rails-oceania] RoRo Talks

2012-12-10 Thread Ben Taylor

All presentations must be accompanied with typewriter noises and each letter 
entering one by one. 

 - Ben


On Tuesday, 11 December 2012 at 11:11 AM, Julio Cesar Ody wrote:

> What do you mean "no transitions"? Where's the fun in that?
> 
> 
> 
> On Tue, Dec 11, 2012 at 11:07 AM, Steven Ringo  (mailto:goo...@stevenringo.com)> wrote:
> > Whatever you feel is appropriate.
> > 
> > On Tuesday, 11 December 2012 at 9:38 AM, Jon Rowe wrote:
> > 
> > Hey Rubyists,
> > 
> > Does anyone know if the "no transitions" guidelines for RoRo presentations
> > include bullet points appearing one by one? Is it a technical limitation or
> > one of style? (If I output to pdf this will look the same, but be a tonne
> > more slides ;) )
> > 
> > Cheers
> > Jon
> > -
> > m...@jonrowe.co.uk (mailto:m...@jonrowe.co.uk)
> > jonrowe.co.uk (http://jonrowe.co.uk)
> > 
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Ruby or Rails Oceania" group.
> > To post to this group, send email to rails-oceania@googlegroups.com 
> > (mailto:rails-oceania@googlegroups.com).
> > To unsubscribe from this group, send email to
> > rails-oceania+unsubscr...@googlegroups.com 
> > (mailto:rails-oceania+unsubscr...@googlegroups.com).
> > For more options, visit this group at
> > http://groups.google.com/group/rails-oceania?hl=en.
> > 
> > 
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Ruby or Rails Oceania" group.
> > To post to this group, send email to rails-oceania@googlegroups.com 
> > (mailto:rails-oceania@googlegroups.com).
> > To unsubscribe from this group, send email to
> > rails-oceania+unsubscr...@googlegroups.com 
> > (mailto:rails-oceania+unsubscr...@googlegroups.com).
> > For more options, visit this group at
> > http://groups.google.com/group/rails-oceania?hl=en.
> > 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To post to this group, send email to rails-oceania@googlegroups.com 
> (mailto:rails-oceania@googlegroups.com).
> To unsubscribe from this group, send email to 
> rails-oceania+unsubscr...@googlegroups.com 
> (mailto:rails-oceania+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/rails-oceania?hl=en.
> 
> 


-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To post to this group, send email to rails-oceania@googlegroups.com.
To unsubscribe from this group, send email to 
rails-oceania+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en.

Re: [rails-oceania] Hung server processes in rails

2012-12-05 Thread Ben Taylor

Does Heroku forcefully timeout requests that go beyond 30 seconds? 

I've had success using Unicorn and changing my timeout time to be 60+ seconds 
(hack to avoid switching to direct-to-s3 uploads). 

 - Ben


On Thursday, 6 December 2012 at 3:00 PM, Iain Beeston wrote:

> Thanks Pat. Heroku also suggested we use rack-timeout. I hadn't thought about 
> using the stacktrace to track down the cause of the problem though, good idea!
> 
> 
> 
> Iain
> 
> 
> On 6 December 2012 14:25, Pat Allan  (mailto:p...@freelancing-gods.com)> wrote:
> > One thing I've found tremendously helpful for increasing awareness of 
> > timeouts - and then hunting down the cause - is rack-timeout. It'll ensure 
> > those timeouts get raised as exceptions (and thus, you get stack traces, 
> > and I think New Relic gets visibility too).
> > 
> > https://github.com/kch/rack-timeout
> > 
> > If you do change the default time limit (15 seconds), make sure you keep it 
> > below 30 seconds when on Heroku (as that's when they'll consider a request 
> > has timed out).
> > 
> > --
> > Pat
> > 
> > On 06/12/2012, at 2:17 PM, Iain Beeston wrote:
> > 
> > > Thanks Chris. We're not using papertrail but we are using logentries, 
> > > which I believe has similar features. There's really nothing to go on in 
> > > the logs other than where the timeouts are happening (we've increased the 
> > > amount of logging but it hasn't helped us find the problem yet). Rather 
> > > than rely on the logs for monitoring the app we use pingdom to hit the 
> > > site periodically, but the end result is similar.
> > >
> > >
> > >
> > > Iain
> > >
> > >
> > >
> > > On 6 December 2012 13:46, Chris Aitchison  > > (mailto:cmaitchi...@gmail.com)> wrote:
> > > Add the Papertrail add-on to your app and you'll have a lot more logging 
> > > information to work with. It can even send you an email when a log entry 
> > > that matches a particular regex occurs, which sounds like it could be 
> > > helpful here (assuming the logs indicate some sort of issue). And it 
> > > could be free.
> > >
> > > Without more information, it would only be a guess to whether the issue 
> > > lies in Heroku or the app code. If you only have one dyno, it will sleep 
> > > after a few minutes of inaction, but I get the impression you are running 
> > > more than one dyno so this shouldn't happen - and besides, the single 
> > > dyno is still supposed to wake up.
> > >
> > > I think the log data is vital, even if you have to crank up the logging 
> > > level until you find the culprit.
> > >
> > > Chris
> > >
> > >
> > >
> > >
> > > On 06/12/2012, at 13:03, Iain Beeston  > > (mailto:iain.bees...@gmail.com)> wrote:
> > >
> > >> Lately we've had problems with the web-server processes in our rails 3.1 
> > >> app intermittently stop responding. We haven't been able to work out why 
> > >> (no exceptions, high cpu or memory usage or networking calls) - it just 
> > >> seems like every few days one them just randomly hangs and never 
> > >> recovers. The process is still there, but not responding to requests and 
> > >> everything sent to it times out. We're using heroku so our logging 
> > >> options are limited.
> > >>
> > >> So, I was wondering - what do people use to keep their servers 
> > >> responsive? (Especially on "hands-off" platforms like heroku) How common 
> > >> is it to routinely restart processes? (Sounds like the wrong solution to 
> > >> me, but some people recommend it)
> > >>
> > >>
> > >> Iain Beeston
> > >>
> > >>
> > >> --
> > >> You received this message because you are subscribed to the Google 
> > >> Groups "Ruby or Rails Oceania" group.
> > >> To post to this group, send email to rails-oceania@googlegroups.com 
> > >> (mailto:rails-oceania@googlegroups.com).
> > >> To unsubscribe from this group, send email to 
> > >> rails-oceania+unsubscr...@googlegroups.com 
> > >> (mailto:rails-oceania%2bunsubscr...@googlegroups.com).
> > >> For more options, visit this group at 
> > >> http://groups.google.com/group/rails-oceania?hl=en.
> > >
> > > --
> > > You received this message

Re: [rails-oceania] Ruby and Sockets ...

2012-11-27 Thread Ben Hoskings

Thirded, it's a very good book. Unix is a beautiful thing.

- Ben



On 28/11/2012, at 8:51 AM, jamesl  wrote:

> If you are interested in Ruby and Sockets then you might want to sign up for 
> a new eBook by Jesse Storimer
> I have subscribed to
> 
> Working with TcpSockets 
> 
> And the content is really good. You can sign up here:
> 
> http://workingwithtcpsockets.com or http://workingwithunixprocesses.com.
> 
> - James.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/rails-oceania/-/RI8KEPvDs_oJ.
> To post to this group, send email to rails-oceania@googlegroups.com.
> To unsubscribe from this group, send email to 
> rails-oceania+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/rails-oceania?hl=en.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To post to this group, send email to rails-oceania@googlegroups.com.
To unsubscribe from this group, send email to 
rails-oceania+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en.

Re: [rails-oceania] Call for Speakers @ Melbourne Meetup

2012-11-26 Thread Ben Hoskings

If there's interest, I'd like to talk about postgres replication, how to set it 
up securely and simply, and how to monitor it.

- Ben



On 27/11/2012, at 9:25 AM, David Goodlad  wrote:

> Hi all
> 
> We've had a couple of people pull out for speaking this month at the 
> Melbourne meetup this Thursday. Is anyone interested in doing a short talk 
> about something that you're passionate about? Full talk, lighting talk, you 
> name your game :)
> 
> If you're in, please let us know asap!
> 
> Cheers
> Dave & Justin

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To post to this group, send email to rails-oceania@googlegroups.com.
To unsubscribe from this group, send email to 
rails-oceania+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en.

Re: [rails-oceania] How to run CI tests in parallel

2012-11-25 Thread Ben Hoskings

Mm, vagrant is great for this sort of stuff.

FYI this isn't a problem any more: there's a master build that triggers the 6 
(now 7) parallel builds, and it only passes if all the sub-builds pass.

The one bit of extra work is that to find each failure, you have to check 
multiple build logs, but in practice it hasn't been an issue.

- Ben



On 26/11/2012, at 9:28 AM, James Healy  wrote:

> A previous project I worked on used Jenkins with a vagrant plugin to run 
> concurrent tests in isolated VMs.
> 
> It took a bit of setting up, but once it got going it was amazing and dropped 
> our build time from >20 minutes to <5 minutes.
> 
> The downside was that it became tricker to understand the "state of the 
> build" at a glance. Instead of checking 1 project, you had to check 6 (unit 
> tests, acceptance tests 1, acceptance tests 2, etc).
> 
> We also tried parallel_tests for a while and it mostly worked, but we ran 
> into a few issues with parallel acceptance specs stepping on each others toes.
> 
> James
> 
> 
> On 22 November 2012 13:12, Sebastian Porto  wrote:
> Hi Guys
> 
> There was a discussion the other day about CI server and it was mention 
> several times how good it is to run the tests in parallel. I am intrigued by 
> this and will like to implement this. But I don't know where to start. 
> 
> What is your approach for running CI test in parallel? We are using TeamCity 
> at the moment, were using Jenkins before. And Rspec.
> 
> Thanks
> Sebastian
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/rails-oceania/-/HqhReVKyNx0J.
> To post to this group, send email to rails-oceania@googlegroups.com.
> To unsubscribe from this group, send email to 
> rails-oceania+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/rails-oceania?hl=en.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To post to this group, send email to rails-oceania@googlegroups.com.
> To unsubscribe from this group, send email to 
> rails-oceania+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/rails-oceania?hl=en.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To post to this group, send email to rails-oceania@googlegroups.com.
To unsubscribe from this group, send email to 
rails-oceania+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en.

Re: [rails-oceania] Multi-tenancy book

2012-11-22 Thread Ben Schwarz

Is the book going to be published by you? Or someone else? 
Paper? Ebook? Both? 

Pricing is hard, but there are many questions to answer before then. 
A couple of people who have self published (and written incredible books) 
are: 

* Mathias Meyer, http://riakhandbook.com/
* Marc-André Cournoyer, http://createyourproglang.com/

Maybe they're worth reaching out to, or mimicking :-)

Best of luck.

On Thursday, 22 November 2012 16:06:03 UTC+11, Ryan Bigg wrote:
>
> You're right. It's a Rails engine that will allow features to be scoped 
> underneath an account.
>
>
> On 22 November 2012 15:52, Robert Gravina 
> > wrote:
>
>>
>>
>>
>> On 22 November 2012 13:45, Robert Gravina 
>> > wrote:
>>
>>> Excuse my ignorance, but does multi-tenancy simply mean multi-user, or 
>>> is there more to it than that?
>>
>>
>> OK I did a bit of googling and think I know what it is now - one Rails 
>> application with content/features scoped by user, company etc.
>>
>> Robert
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Ruby or Rails Oceania" group.
>> To post to this group, send email to rails-...@googlegroups.com
>> .
>> To unsubscribe from this group, send email to 
>> rails-oceani...@googlegroups.com .
>> For more options, visit this group at 
>> http://groups.google.com/group/rails-oceania?hl=en.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/rails-oceania/-/IislBqduUosJ.
To post to this group, send email to rails-oceania@googlegroups.com.
To unsubscribe from this group, send email to 
rails-oceania+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en.

Re: [rails-oceania] Recommendations for AJAX buttons & actions in Rails 3.2

2012-11-21 Thread Ben Taylor

Something I use a lot is AJAX'd modals. So I have a little bit of JS that looks 
like:  

$ ->
  $(document).on 'click', '[data-load-modal]', ->
url = $(this).attr('data-load-modal')
Modal.open(url)


  $(document).on 'click', '[data-close-modal]', Modal.close  

window.Modal =  
  close: ->
$overlay.addClass "hidden"
$modal.addClass "hidden"

  open: (url) ->
$overlay.removeClass "hidden"

extras =  
  modal: true

 # this should be done by a URL parser
if /\?/.exec(url)
  for pair in url.split('?')[1].split('&')
a = pair.split("=")[0]
b = pair.split("=")[1]
extras[a] = b

$.ajax
  url: url
  data: extras
  dataType: 'html'
  success: (result) => $modal.html(result)
  error: (xhr, string, errorThrown) ->
  direError "There was an error contacting the server"


You could potentially follow this pattern and do something like:

<%= link_to "More", articles_path(offset: @offset + @step), :remote => true, 
"data-append-to" => "#articles" %>

$(document).on "ajax:success", "[data-append-to]", (event, result) ->
  selector = $(event.target).attr("data-append-to")
  $(selector).append(result)

Then add others, like data-replace and data-prepend-to. This way you don't have 
to write a lot of JS and get something similar to the 2.3 behaviour.

 - Ben


On Wednesday, 21 November 2012 at 11:54 PM, Dave Perrett wrote:

> Interesting, thanks Adam - I've been meaning to have a look at angular. This 
> is the kind of thing I've been doing in backbone -> 
> https://gist.github.com/4124680 . Any thoughts?  
>  
> Adam Boas wrote:  
> > The real nub is defining what 'better' would mean.  
> > Simplest? Most Re-usable? Easiest to maintain? Least amount of effort?
> >  
> > Its always going to be a trade off. And the 'best' approach is going to be 
> > more to do with where you app is already at, what the skill set is of the 
> > developers, and where the app is going in terms of features and 
> > functionality.  
> >  
> > I tend to lean toward the simplest solution I can manage, particularly on 
> > pre-existing, large apps. If you already have controllers shipping HTML 
> > there is nothing wrong with leveraging that and sprinkling a little AJAX 
> > pixie dust to make the app seem more responsive. To me the only absolute is 
> > to keep the pixie dust out of the templates and make it clean and readable. 
> >  
> >  
> > I personally really like Backbone for building an app with significant rich 
> > client behaviour, but would never introduce it to an existing full page 
> > post application just to get a little bit of responsive behaviour in some 
> > forms. It introduces significant complexity that just doesn't make any 
> > sense for the kind of thing you have mentioned. And if you are not routing 
> > or changing views, and have no significant model(s) it really adds very 
> > little value.  
> >  
> > Angular is a framework I have been playing with a bit recently and it does 
> > seem to offer a nice, lighter weight alternative to just writing Jquery 
> > plugins for this kind of thing. Its binding behaviour can make responding 
> > to your posts nice and simple. I can definitely recommend having a bit of a 
> > look at if as an alternative, particularly if you want to play with the new 
> > shiny :-)  
> >  
> > Adam Boas
> > e: adam.b...@gmail.com (mailto:adam.b...@gmail.com)
> > m: +61 457 741 117
> >  
> >  
> >  
> > On 21/11/2012, at 8:41 PM, Michael Pearson  > (mailto:mipear...@gmail.com)> wrote:
> > > On Wed, Nov 21, 2012 at 8:10 PM, Adam Boas  > > (mailto:adam.b...@gmail.com)> wrote:
> > > > Hi Michael,
> > > >  
> > > > The bad news is that link_to_remote still exists. It has just changed 
> > > > syntax: link_to(…, remote: true)
> > > >  
> > > > This functionality would be trivial to write in JS or Coffee to attach 
> > > > to the button and form and post it via ajax. I definitely wouldn't 
> > > > inline it in the link_to though. Write a JQuery plugin and attach it in 
> > > > dom-ready. I would probably write it fairly generically, since this 
> > > > form/button/ response HTML/text pattern is pretty common.   
> > > >  
> > > You'll see I'm already using the new :remote => true syntax in my 
> > > exampl

Re: [rails-oceania] Rails Necromancy - Getting a 2.3.4 app running

Looks like the migration to Bamboo has gone smoothly. Pity Heroku didn't 
mention this was an option in any of their communications. I would have been 
pulling my hair out all week.  

 - Ben


On Tuesday, 20 November 2012 at 11:28 PM, Ben Taylor wrote:

> > heroku stack:migrate bamboo-ree-1.8.7
> >  
> > It just worked for me.  
> Ahh, I tried to create a new app on Bamboo and got denied (because they are 
> forcing everyone over to cedar). Will try migrating.  
>  
>  
>  - Ben
>  
>  
> On Tuesday, 20 November 2012 at 11:27 PM, Phil Oye wrote:
>  
> > I was in a similar situation but I gave up going to Cedar. Instead, I 
> > migrated to Bamboo and all was well without any code changes.  
> >  
> > heroku stack:migrate bamboo-ree-1.8.7
> >  
> > It just worked for me.  
> >  
> > Cheers,
> > p.
> >  
> >  
> > On 20/11/2012, at 10:36 PM, Ben Taylor  > (mailto:m...@taybenlor.com)> wrote:
> >  
> > > Hi RoRo,  
> > >  
> > > At work we have a very old app running on Heroku (yes, 2.3 is very old 
> > > now). It's on Aspen and I've been trying to migrate it over to Cedar, 
> > > unfortunately the original developer no longer works here. As part of 
> > > migrating it I've switched it over to using bundler and upgraded it to 
> > > 2.3.14 (though still on ruby 1.8.7). Of course I haven't been able to get 
> > > it running locally.
> > >  
> > > We're running out of time to get it running on Cedar (Aspen will be 
> > > sunsetted in a few days) so I'm starting to get desperate.
> > >  
> > > I've been banging my head against the wall for two days now and not 
> > > really getting anywhere. I've managed to figure out what versions of 
> > > everything it used to run on, but it won't run now. The culprit at the 
> > > moment is Devise.
> > >  
> > > I don't really understand the issue, but I'll give you a stack trace.
> > >  
> > > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/activesupport-2.3.14/lib/active_support/dependencies.rb:611:in
> > >  `to_constant_name': Anonymous modules have no name to be referenced by 
> > > (ArgumentError)
> > > from 
> > > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/activesupport-2.3.14/lib/active_support/dependencies.rb:417:in
> > >  `qualified_name_for'
> > > from 
> > > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/activesupport-2.3.14/lib/active_support/dependencies.rb:130:in
> > >  `const_missing'
> > > from 
> > > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/devise-0.4.3/lib/devise.rb:55:in
> > >  `mailer_sender='
> > > from /Users/ben/Dropbox/dev/redacted/config/initializers/devise.rb:21
> > > from 
> > > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/devise-0.4.3/lib/devise.rb:45:in
> > >  `setup'
> > > from /Users/ben/Dropbox/dev/redacted/config/initializers/devise.rb:5
> > >  
> > > …
> > >  
> > > The particular method it's calling is
> > >  
> > > module Devise
> > > def self.mailer_sender=(value)
> > >   DeviseMailer.sender = value
> > > end
> > >  
> > > end
> > >  
> > > The version of Devise is very old, but that's the one it's been running 
> > > on. I've tried it on devise up to 0.7 but still get the same errors. I'm 
> > > wary of going too far forwards as there were a bunch of breaking changes. 
> > >  
> > >  
> > > There seems to be some problem loading Devise's modules. If I work around 
> > > this particular Devise call, it later on stalls at:
> > >  
> > > class User < ActiveRecord::Base
> > > devise :all
> > > end
> > >  
> > > With
> > >  
> > > Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/activerecord-2.3.4/lib/active_record/base.rb:1959:in
> > >  `method_missing_without_paginate': undefined method `devise' for 
> > > # (NoMethodError)
> > > from 
> > > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:170:in
> > >  `method_missing'
> > > from /Users/ben/Dropbox/dev/redacted/app/models/user.rb:6
> > >  
> > >  
> > >  
> > > Would be amazing if anyone could point me at anything. I've been googling 
> > > all around, changing versions and diving into the Devise source, but I 
> > > feel

Re: [rails-oceania] Rails Necromancy - Getting a 2.3.4 app running

> heroku stack:migrate bamboo-ree-1.8.7
>  
> It just worked for me.  
Ahh, I tried to create a new app on Bamboo and got denied (because they are 
forcing everyone over to cedar). Will try migrating.  


 - Ben


On Tuesday, 20 November 2012 at 11:27 PM, Phil Oye wrote:

> I was in a similar situation but I gave up going to Cedar. Instead, I 
> migrated to Bamboo and all was well without any code changes.  
>  
> heroku stack:migrate bamboo-ree-1.8.7
>  
> It just worked for me.  
>  
> Cheers,
> p.
>  
>  
> On 20/11/2012, at 10:36 PM, Ben Taylor  (mailto:m...@taybenlor.com)> wrote:
>  
> > Hi RoRo,  
> >  
> > At work we have a very old app running on Heroku (yes, 2.3 is very old 
> > now). It's on Aspen and I've been trying to migrate it over to Cedar, 
> > unfortunately the original developer no longer works here. As part of 
> > migrating it I've switched it over to using bundler and upgraded it to 
> > 2.3.14 (though still on ruby 1.8.7). Of course I haven't been able to get 
> > it running locally.
> >  
> > We're running out of time to get it running on Cedar (Aspen will be 
> > sunsetted in a few days) so I'm starting to get desperate.
> >  
> > I've been banging my head against the wall for two days now and not really 
> > getting anywhere. I've managed to figure out what versions of everything it 
> > used to run on, but it won't run now. The culprit at the moment is Devise.
> >  
> > I don't really understand the issue, but I'll give you a stack trace.
> >  
> > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/activesupport-2.3.14/lib/active_support/dependencies.rb:611:in
> >  `to_constant_name': Anonymous modules have no name to be referenced by 
> > (ArgumentError)
> > from 
> > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/activesupport-2.3.14/lib/active_support/dependencies.rb:417:in
> >  `qualified_name_for'
> > from 
> > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/activesupport-2.3.14/lib/active_support/dependencies.rb:130:in
> >  `const_missing'
> > from 
> > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/devise-0.4.3/lib/devise.rb:55:in 
> > `mailer_sender='
> > from /Users/ben/Dropbox/dev/redacted/config/initializers/devise.rb:21
> > from 
> > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/devise-0.4.3/lib/devise.rb:45:in 
> > `setup'
> > from /Users/ben/Dropbox/dev/redacted/config/initializers/devise.rb:5
> >  
> > …
> >  
> > The particular method it's calling is
> >  
> > module Devise
> > def self.mailer_sender=(value)
> >   DeviseMailer.sender = value
> > end
> >  
> > end
> >  
> > The version of Devise is very old, but that's the one it's been running on. 
> > I've tried it on devise up to 0.7 but still get the same errors. I'm wary 
> > of going too far forwards as there were a bunch of breaking changes.  
> >  
> > There seems to be some problem loading Devise's modules. If I work around 
> > this particular Devise call, it later on stalls at:
> >  
> > class User < ActiveRecord::Base
> > devise :all
> > end
> >  
> > With
> >  
> > Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/activerecord-2.3.4/lib/active_record/base.rb:1959:in
> >  `method_missing_without_paginate': undefined method `devise' for 
> > # (NoMethodError)
> > from 
> > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:170:in
> >  `method_missing'
> > from /Users/ben/Dropbox/dev/redacted/app/models/user.rb:6
> >  
> >  
> >  
> > Would be amazing if anyone could point me at anything. I've been googling 
> > all around, changing versions and diving into the Devise source, but I feel 
> > like there's much too much going on here for me to understand every 
> > possibility. It also doesn't help that the app is quite old.
> >  
> > Cheers,
> >  - Ben
> >  
> > --  
> > You received this message because you are subscribed to the Google Groups 
> > "Ruby or Rails Oceania" group.
> > To post to this group, send email to rails-oceania@googlegroups.com 
> > (mailto:rails-oceania@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > rails-oceania+unsubscr...@googlegroups.com 
> > (mailto:rails-oceania+unsubscr...@googlegroups.com).
> > For more options, visit this group at 
> > http://groups.google.com/group/rails-oceania?hl=en.
> --  
> You rece

Re: [rails-oceania] Rails Necromancy - Getting a 2.3.4 app running

Ahh, of course.  

It's  

Devise.mailer_sender = "nore...@redacted.com"


 - Ben


On Tuesday, 20 November 2012 at 11:25 PM, Pat Allan wrote:

> Ben, what's line 21 of your devise.rb initialiser?
>  
> On 20/11/2012, at 10:36 PM, Ben Taylor wrote:
>  
> > Hi RoRo,
> >  
> > At work we have a very old app running on Heroku (yes, 2.3 is very old 
> > now). It's on Aspen and I've been trying to migrate it over to Cedar, 
> > unfortunately the original developer no longer works here. As part of 
> > migrating it I've switched it over to using bundler and upgraded it to 
> > 2.3.14 (though still on ruby 1.8.7). Of course I haven't been able to get 
> > it running locally.
> >  
> > We're running out of time to get it running on Cedar (Aspen will be 
> > sunsetted in a few days) so I'm starting to get desperate.
> >  
> > I've been banging my head against the wall for two days now and not really 
> > getting anywhere. I've managed to figure out what versions of everything it 
> > used to run on, but it won't run now. The culprit at the moment is Devise.
> >  
> > I don't really understand the issue, but I'll give you a stack trace.
> >  
> > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/activesupport-2.3.14/lib/active_support/dependencies.rb:611:in
> >  `to_constant_name': Anonymous modules have no name to be referenced by 
> > (ArgumentError)
> > from 
> > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/activesupport-2.3.14/lib/active_support/dependencies.rb:417:in
> >  `qualified_name_for'
> > from 
> > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/activesupport-2.3.14/lib/active_support/dependencies.rb:130:in
> >  `const_missing'
> > from 
> > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/devise-0.4.3/lib/devise.rb:55:in 
> > `mailer_sender='
> > from /Users/ben/Dropbox/dev/redacted/config/initializers/devise.rb:21
> > from 
> > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/devise-0.4.3/lib/devise.rb:45:in 
> > `setup'
> > from /Users/ben/Dropbox/dev/redacted/config/initializers/devise.rb:5
> > …
> >  
> > The particular method it's calling is
> >  
> > module Devise
> > def self.mailer_sender=(value)
> > DeviseMailer.sender = value
> > end
> > end
> >  
> > The version of Devise is very old, but that's the one it's been running on. 
> > I've tried it on devise up to 0.7 but still get the same errors. I'm wary 
> > of going too far forwards as there were a bunch of breaking changes.  
> >  
> > There seems to be some problem loading Devise's modules. If I work around 
> > this particular Devise call, it later on stalls at:
> >  
> > class User < ActiveRecord::Base
> > devise :all
> > end
> >  
> > With
> >  
> > Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/activerecord-2.3.4/lib/active_record/base.rb:1959:in
> >  `method_missing_without_paginate': undefined method `devise' for 
> > # (NoMethodError)
> > from 
> > /Users/ben/.rvm/gems/ruby-1.8.7-p371/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:170:in
> >  `method_missing'
> > from /Users/ben/Dropbox/dev/redacted/app/models/user.rb:6
> >  
> >  
> > Would be amazing if anyone could point me at anything. I've been googling 
> > all around, changing versions and diving into the Devise source, but I feel 
> > like there's much too much going on here for me to understand every 
> > possibility. It also doesn't help that the app is quite old.
> >  
> > Cheers,
> > - Ben
> >  
> >  
> > --  
> > You received this message because you are subscribed to the Google Groups 
> > "Ruby or Rails Oceania" group.
> > To post to this group, send email to rails-oceania@googlegroups.com 
> > (mailto:rails-oceania@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > rails-oceania+unsubscr...@googlegroups.com 
> > (mailto:rails-oceania+unsubscr...@googlegroups.com).
> > For more options, visit this group at 
> > http://groups.google.com/group/rails-oceania?hl=en.
> >  
>  
>  
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To post to this group, send email to rails-oceania@googlegroups.com 
> (mailto:rails-oceania@googlegroups.com).
> To unsubscribe from this group, send email to 
> rails-oceania+unsubscr...@googlegroups.com 
> (mailto:rails-oceania+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/rails-oceania?hl=en.
>  
>  


-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To post to this group, send email to rails-oceania@googlegroups.com.
To unsubscribe from this group, send email to 
rails-oceania+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en.

[rails-oceania] Rails Necromancy - Getting a 2.3.4 app running