Configurando o Redmine no OS X

1

Estou seguindo as instruções de instalação do redmine. Eu estou instalando isso no OS X 10.6.2 com o mysql 5.1.41. Eu tenho o banco de dados definido no local Db; Eu posso entrar no banco de dados local com o usuário de redmine e usar o banco de dados de redmine, no entanto, quando eu corro:

RAILS_ENV=production rake db:migrate --trace

Alguém pode adicionar algum significado ao seguinte rastreamento de pilha:

** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
rake aborted!
can't convert Hash into String
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/fileutils.rb:1408:in 'directory?'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/fileutils.rb:1408:in 'fu_each_src_dest0'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/fileutils.rb:1393:in 'fu_each_src_dest'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/fileutils.rb:840:in 'install'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:1070:in 'install'
/Users/wrbarbour/projects/redmine/config/environment.rb:60
/Library/Ruby/Gems/1.8/gems/rails-2.3.4/lib/initializer.rb:111:in 'run'
/Users/wrbarbour/projects/redmine/config/environment.rb:20
/Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in 'gem_original_require'
/Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in 'require'
/Library/Ruby/Gems/1.8/gems/activesupport-2.3.4/lib/active_support/dependencies.rb:156:in 'require'
/Library/Ruby/Gems/1.8/gems/activesupport-2.3.4/lib/active_support/dependencies.rb:521:in 'new_constants_in'
/Library/Ruby/Gems/1.8/gems/activesupport-2.3.4/lib/active_support/dependencies.rb:156:in 'require'
/Library/Ruby/Gems/1.8/gems/rails-2.3.4/lib/tasks/misc.rake:4
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:617:in 'call'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:617:in 'execute'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:612:in 'each'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:612:in 'execute'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:578:in 'invoke_with_call_chain'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/monitor.rb:242:in 'synchronize'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:571:in 'invoke_with_call_chain'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:588:in 'invoke_prerequisites'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:585:in 'each'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:585:in 'invoke_prerequisites'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:577:in 'invoke_with_call_chain'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/monitor.rb:242:in 'synchronize'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:571:in 'invoke_with_call_chain'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:564:in 'invoke'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:2027:in 'invoke_task'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in 'top_level'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in 'each'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in 'top_level'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in 'standard_exception_handling'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:1999:in 'top_level'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:1977:in 'run'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in 'standard_exception_handling'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/lib/rake.rb:1974:in 'run'
/Users/wrbarbour/.gem/ruby/1.8/gems/rake-0.8.4/bin/rake:31
/usr/bin/rake:19:in 'load'
/usr/bin/rake:19
    
por Boiler Bill 04.12.2009 / 03:58

2 respostas

0

Quais instruções você segue?

Quais são as suas versões do Redmine, Rails?

Você atualiza seu redmine_dir / config / database.yml com suas configurações de banco de dados de produção?

    
por 04.12.2009 / 09:33
1

Acontece que meu problema era com a gem do MySQL 2.8.1 como foi descoberta nesta postagem do blog

    
por 09.12.2009 / 20:35