I installed rails 1.1.6 and then tried to run "rake db:migrate" and here's what I get:
/Users/cyoung/Code/sds/trunk/config/boot.rb:28:Warning: require_gem is obsolete. Use gem instead. ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment rake aborted! no such file to load -- ruby-debug /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' /usr/local/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/ active_support/dependencies.rb:147:in `require' /usr/local/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb: 191:in `load_environment' /usr/local/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb: 168:in `load_environment' /usr/local/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/ active_support/core_ext/kernel/reporting.rb:11:in `silence_warnings' /usr/local/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb: 165:in `load_environment' /usr/local/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:82:in `process' /usr/local/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:42:in `send' /usr/local/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:42:in `run' /Users/cyoung/Code/sds/trunk/config/../config/environment.rb:17 /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' /usr/local/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/ active_support/dependencies.rb:147:in `require' /usr/local/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/tasks/misc.rake:3 /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `call' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:362:in `invoke' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in `synchronize' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in `invoke' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:369:in `invoke_prerequisites' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1003:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1003:in `send' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1003:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:368:in `invoke_prerequisites' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:361:in `invoke' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in `synchronize' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in `invoke' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in `standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1733:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1711:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in `standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1708:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/bin/rake:7 /usr/local/bin/rake:16:in `load' /usr/local/bin/rake:16 Any ideas? Thanks. Cynick On May 11, 2:04 pm, Aaron <[EMAIL PROTECTED]> wrote: > The default behavior for logging in: > 1) Checks your credentials against the sunflower db > a) if it successfully authenticates, syncs your data to the local db > b) if unsuccessful, checks your credentials in the local db and > logs you in or fails, depending > > So if you can't access the sunflower db, you'll jump to 1b) and it > will check against the local db. > > Right now, logging in doesn't get you any better or worse access to > the SDS. All functionality is open to anyone. Now, obviously that's > not a great way to run the SDS, but full authentication and access > controls are coming at a later date. > > The SDS needs rails 1.1.6 to run for now. Fortunately, rails gems can > generally coexist with different versions of themselves. Simply run > 'gem install rails --version 1.1.6', and you should be good to go. > > To choose which version of rails, in your config/environment.rb, edit > the line: > RAILS_GEM_VERSION = '1.1.6' > and change the version to whatever version you'd like. > > Hope this helps- > -- Aaron > > On May 11, 2007, at 1:11 PM, Cynick wrote: > > > > > In the setup, there's a section about requiring a sunflower database > > for login purposes. "Login functionality will not work correctly > > without a valid username and password to sunflower, which is still to > > be provided. Fortunately, logging in is not necessary at this point in > > time (but that is expected to change)." I'm confused. Login is not > > necessary but this sunflower database is still required in the > > configuration? > > > Also, how and why are we connecting to database.concord.org? Does > > this mean we can't *truly* have a local SDS running outside of > > Concord? Can I run the local SDS on my laptop when there's no net > > connection? > > > sunflower: > > adapter: mysql > > database: sunflower > > host: database.concord.org > > username: TBD > > password: TBD > > > When I was doing the "rake db:migrate" step, I got the following > > error: > > > Cannot find gem for Rails =1.1.6: > > Install the missing gem with 'gem install -v=1.1.6 rails', or > > change environment.rb to define RAILS_GEM_VERSION with your > > desired version. > > > Does the SDS only work with Rails 1.1.6? I have rails (1.2.3) > > installed. Do I need both versions installed? Can they co-exist > > simultaneously? I don't want to uninstall 1.2.3 because of other > > applications I'd like to run. How do I choose which version of rails > > my application is running? > > > I'm almost there getting this thing running. > > > Cynick > > > On Apr 13, 4:25 pm, Aaron Unger <[EMAIL PROTECTED]> wrote: > >> I've finished writing a how-to for setting up the SDS locally. I > >> posted it to the TELS Confluence:http://www.telscenter.org/ > >> confluence/display/SAIL/Setting+up+a+local+SDS > > >> The instructions cover setting up the software infrastructure (ruby, > >> rails, mysql), checking out and configuring the SDS, and finally > >> running the SDS. The instructions do not cover running the SDS in a > >> production environment (under Apache or Lighttpd, for example). The > >> software infrastructure section is fairly detailed for Mac OS X, but > >> not so much for other platforms. Feel free to add instructions for > >> any other platforms that you get set up with! > > >> Currently the instructions will not import any existing SDS data, so > >> you'll finish with a clean install. I'd like to post a mysql dump for > >> anyone who is interested, but need to converse with Stephen about > >> this first. > > >> Any feedback is welcome. > > >> -- Aaron > > >> -- > >> Aaron Unger > >> The Concord Consortium > >> [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
