All to nought. No change alas.
Confirmation of version:
[root@ca-sna-pm01 puppet-dashboard]# gem list | grep rubygem
rubygems-update (1.8.25)
[root@ca-sna-pm01 puppet-dashboard]#
Retry of Schematization:
[root@ca-sna-pm01 puppet-dashboard]# !1441
rake RAILS_ENV=producti
Stuart, googling the rake error you were getting resulted in the following hit:
http://stackoverflow.com/questions/15349869/undefined-method-source-index-for-gemmodule-nomethoderror
Which indicated the version of rubygems is not compatible with the
rails application.
On Mon, Dec 16, 2013 at 10:3
Thanks Ramin.
A good tip.
Thank-you.
On Dec 16, 2013, at 1:49 PM, Ramin K wrote:
> No Ruby Mysql bindings aka the mysql gem.
>
> http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#installing-dependencies
>
> Ramin
>
> On 12/16/2013 12:37 PM, Stuart Cracraft wrote:
>> And the
I followed:
http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html
and have reached the point after
puppet dashboard install/configuration
MySQL server and MySQL client installation/configuration/startup
at
Preparing Schema
and now receive the error:
rake RAILS_ENV=prod
