On Jan 9, 6:14 pm, Frederick Cheung
wrote:
> On Jan 9, 1:10 pm, JD wrote:
>
> > Hello all,
>
> > I'm relatively new to rails and have been doing ok with it but I have
> > run into an issue that I'm sure has a really easy solution that I just
&
Well I've figured this one out so no worries.
On Jan 9, 1:10 pm, JD wrote:
> Hello all,
>
> I'm relatively new to rails and have been doing ok with it but I have
> run into an issue that I'm sure has a really easy solution that I just
> can't seem to see.
&
Hello all,
I'm relatively new to rails and have been doing ok with it but I have
run into an issue that I'm sure has a really easy solution that I just
can't seem to see.
Basically I have an app and have namespaced and admin section to it.
I'm getting the following error:
No route matches {:acti
> Make sure you don't have gems installed in different places. We were
> getting this when run from rc.local because a couple gems had gotten
> installed in a user directory (~/.gem) instead of the system path.
Forgot; use: gem list -d
to see where things are installed
--
Posted via http://www.
Morgan Morgan wrote:
> Missing the Rails gem. Please `gem install -v= rails`, update your
> RAILS_GEM_VERSION setting in config/environment.rb for the Rails version
> you do have installed, or comment out RAILS_GEM_VERSION to use the
> latest version installed.
Make sure you don't have gems insta
For the sake of information (maybe it'll be useful to some of you
lurking for information on Rails 3 but following neither the commits
or rubyonrails-core mailing list), note that Rails edge does not have
a script/* structure anymore. The new way to go is to use the rails
command provided as script
More information about the new structure of Bundler:
http://yehudakatz.com/2010/02/01/bundler-0-9-heading-toward-1-0/
--
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-t...@googlegroups.com.
The fix was quicker than I expected :)
Bundler has been revamped as a binary, so wycats instructions are
invalid now.
To get rails edge rolling, one must do :
(sudo) gem uninstall bundler
(sudo) gem install bundler --prerelease
cd to/your/rails/app/
bundle install
More information: http://github
BLE: /opt/ruby1.9/bin/ruby1.9
- EXECUTABLE DIRECTORY: /opt/ruby1.9/bin
- RUBYGEMS PLATFORMS:
- ruby
- x86-linux
- GEM PATHS:
- /opt/ruby1.9/lib/ruby1.9/gems/1.9.1
- /home/jd/.gem/ruby/1.9.1
- GEM CONFIGURATION:
- :update_sources => true
- :verbose =>
ethod to temporary make the super method public, yielding to it in
this context. Anyway, the main issue is solved ^^
On 27 juil, 05:10, Frederick Cheung
wrote:
> On Jul 27, 2:23 am, jd wrote:
>
> > Hi.
>
> > I'm currently writing a plugin, which "could" be a
igure out why :)
Here's a gist for this implementation: http://gist.github.com/155990
Feel free to push if needed ;)
Thank you for your help !
jd
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails:
I'm having trouble with Rails Integrations tests on Rails 2.3 not
setting the query string on post actions. I'm testing a rails metal
so when the env["QUERY_STRING"] variable isn't set, in the test, the
metal doesn't get any of the query string params. For some reason
this is only set on a GET r
I'm new to Ruby/Rails and trying to understand Time/Date/DateTime. I
came across this weirdness while playing around and was wondering if
someone can tell me what is going on here:
>> w = Work.find(9)
=> #
>> w.created_at.class
=> ActiveSupport::TimeWithZone
>> w.created_at
=> Mon, 06 Apr 2009 16
13 matches
Mail list logo