Welcome Guest Login Register Member List
ExpressionEngine Forums
Advanced Search
Username: Password:
Remember Me? forgot password?
You are here: Forum Home  >  Installation  >  Mac OS X  >  Thread
   
 
Mac OS X install without Locomotive
 
Saanvik
Posted: 21 October 2007 11:21 PM   [ Ignore ]  
Newbie
Rank
Total Posts:  2
Joined  2007-10-21

I really don’t want to install MySQL on my Mac, so I’m trying to install Tracks 1.043 without Locomotive.

Details:
  Mac Mini, intel processor
  OS 10.4.10
  Tracks 1.043
 
Installed gems okay
Installed sqlite3-ruby 1.2.1 using gems

And then I started to run into problems.

In the scripts directory, I opened the installation.html file
Under SQLite/SQLite3 it says that the instructions are the same as for MySQL, except they aren’t (okay, I’m paraphrasing).  The sentence ends with “so you’re ready to go”.  Go where?

So, I started reading the MySQL instructions.

Unzip tracks.  Okay, already did that.
Make a database - is this one of the steps that’s already done?  Sounds like it, so I skip to the next bullet point.
All about database.yml - ah, I don’t have to change that.
Next, change the salt in environment.rb.  Cool.  Done.
Now, rake migrate - oh oh, it doesn’t work.

rake aborted!
uninitialized constant API

(See full trace by running task with—trace)

Okay, let’s trace.

(in /Users/stevenanderson/applications/tracks-1.043)
** Invoke migrate (first_time)
** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:migrate
rake aborted!
uninitialized constant API
/Users/stevenanderson/applications/tracks-1.043/config/../vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:112:in `const_missing’
/Users/stevenanderson/applications/tracks-1.043/config/../vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:122:in `send’
/Users/stevenanderson/applications/tracks-1.043/config/../vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:122:in `const_missing’
/usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/driver/native/driver.rb:100:in `open’
/usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/database.rb:111:in `initialize’
/Users/stevenanderson/applications/tracks-1.043/config/../vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:17:in `new’
/Users/stevenanderson/applications/tracks-1.043/config/../vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:17:in `sqlite3_connection’
/Users/stevenanderson/applications/tracks-1.043/config/../vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:251:in `send’
/Users/stevenanderson/applications/tracks-1.043/config/../vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:251:in `connection_without_query_cache=‘
/Users/stevenanderson/applications/tracks-1.043/config/../vendor/rails/activerecord/lib/active_record/query_cache.rb:54:in `connection=‘
/Users/stevenanderson/applications/tracks-1.043/config/../vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:220:in `retrieve_connection’
/Users/stevenanderson/applications/tracks-1.043/config/../vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:78:in `connection’
/Users/stevenanderson/applications/tracks-1.043/config/../vendor/rails/activerecord/lib/active_record/migration.rb:280:in `migrate’
/Users/stevenanderson/applications/tracks-1.043/config/../vendor/rails/railties/lib/tasks/databases.rake:4
/Users/stevenanderson/applications/tracks-1.043/config/../vendor/rails/railties/lib/tasks/databases.rake:3:in `call’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `execute’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `each’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `execute’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:362:in `invoke’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in `synchronize’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in `invoke’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:369:in `invoke_prerequisites’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:368:in `each’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1003:in `send’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1003:in `each’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:368:in `invoke_prerequisites’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:361:in `invoke’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in `synchronize’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in `invoke’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in `top_level’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in `each’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in `top_level’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1733:in `standard_exception_handling’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1733:in `top_level’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1711:in `run’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1708:in `standard_exception_handling’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1708:in `run’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/bin/rake:7
/usr/bin/rake:16:in `load’
/usr/bin/rake:16


Any ideas?

Profile
 
Reinier Balt
Posted: 22 October 2007 06:38 AM   [ Ignore ]   [ # 1 ]  
Sr. Member
RankRankRankRank
Total Posts:  216
Joined  2006-10-05

when you say that you don’t have to change the database.yml, do you mean that your database.yml contains ‘database: /PATH/TO/TRACKS/db/tracks-104.db’ already? Make sure that the production database points to you correct tracks SQLite database

Profile
 
Saanvik
Posted: 22 October 2007 02:10 PM   [ Ignore ]   [ # 2 ]  
Newbie
Rank
Total Posts:  2
Joined  2007-10-21

I’m saying the directions say not do anything to the database.yml file.

I verified, though, that it does indeed point to

  db/tracks-104.db

which does exist in the tracks directory.  Does it matter that the path is not a complete path?

Profile
 
Reinier Balt
Posted: 24 October 2007 07:31 AM   [ Ignore ]   [ # 3 ]  
Sr. Member
RankRankRankRank
Total Posts:  216
Joined  2006-10-05

I’m not sure. You can try to put your complete path there

Profile
 
bsag
Posted: 30 October 2007 08:52 AM   [ Ignore ]   [ # 4 ]  
Administrator
Avatar
RankRankRankRank
Total Posts:  195
Joined  2006-03-05

Note also that you need to have the same path for the development: line because rake looks for the development database when running migrate, unless you tell it not too. If you point both the production: and development: lines to the same db, rake will upgrade it for you.

Also, you don’t need to install MySQL to use Locomotive, so if you still have trouble, you might find it easier to use that.

Profile
 
   
 
 
‹‹ MySQL > SQLite3 db transition (Tracks 1.043 Locomotive install on 10.4.10)      Slingshot: Syncing offline work a reality? ››

Powered By ExpressionEngine
Template Design By Sonnenvogel.com
Select a theme:

ExpressionEngine Discussion Forum - Version 2.1.1 (20081028)
Script Executed in 0.1211 seconds

Atom Feed
RSS 2.0