http://www.mrcheapstuff.com/categories/electronics/buycom-coupons/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To
Russell Norris and i agree with this message.
RSL
On Tue, Oct 14, 2008 at 4:09 AM, August Lilleaas
<[EMAIL PROTECTED]>wrote:
>
> Because the require 'test_helper' at the top of all the tests is
> relative now (it used to be something like require '../test_helper'),
if you look at the template customization code, it's PHP.
RSL
On Sat, Oct 4, 2008 at 10:29 AM, Phlip <[EMAIL PROTECTED]> wrote:
>
> Railsters;
>
> I can't Google for this because I keep hitting all the spinoffs.
>
> Tx!
>
> --
> Phlip
>
>
> >
>
--~--~-~--~~~---~--~
paperclip allows you to use s3 buckets. checkout
http://dev.thoughtbot.com/paperclip/classes/Paperclip/ClassMethods.html#M04.
dunno why it's not more prominently displayed [in the readme or whatever].
gotta say, paperclip is just plain easy to setup. <3 simplicity.
disclaimer: i've never used
veering off topic... what does "Ferret is nice, until you try to make it run
in production." mean exactly? i've seen mention that ferret has problems in
production but i don't understand what other use you'd want it for. just to
develop an idea but never put into production?
agreed on sphinx being
not sure what @person.quizzes refers to [so this might not apply here] but
if it refers to an ActiveRecord association you could use the sum method in
ActiveRecord like @person.quizzes.sum(:some_field). link with more details:
http://api.rubyonrails.org/classes/ActiveRecord/Calculations/ClassMethod
if you need preexisting values/objects in the database for specific tests,
you should either create them in a setup block, create them with a factory
method [see things like Factory Girl or Fixture Replacement], or load them
via fixtures. if we had more specifics we could give more specific advice.
You shouldn't really need to call this within a controller. Rails uses a
convention called MVC which means that the model, the view, and the
controller concerns are all separate to themselves. Here's the wikipedia
article on it [http://en.wikipedia.org/wiki/Model-view-controller] and
here's an entr
paulo, what you're looking for in test::unit is under integration testing.
in rspec, it's usually done with stories. controller tests/specs are
specifically for one controller. integration testing is designed to test
your app as a system rather than in units. hope that helps.
RSL
On Sat, Sep 6, 2
9 matches
Mail list logo
