http:\/\/rubyforge.org\/forum\/forum.php?thread_id=4161&forum_id=4050<\/a><\/p>\nPerhaps a nicer message might be – “Hey, I see you don’t have the ruby development headers installed, install some”, and maybe even download them.<\/p>\n
Even Perl is more user friendly than that when it comes to missing libraries, and Perl is famous for being obscure.<\/p>\n
Once I overcame that minor hurdle, the installer trundled away merrily, and failed on the next message<\/p>\n
Gem::InstallError: cloudfuji_paperclip requires Ruby version >= 1.9.2.
\nAn error occurred while installing cloudfuji_paperclip (3.0.3), and Bundler cannot continue.
\nMake sure that `gem install cloudfuji_paperclip -v '3.0.3'` succeeds before bundling.<\/code><\/p>\nDebian has Ruby 1.91, and Ruby 1.8 in stable.
\n*and* the previous compiled gem (eventmachine) required 1.8 specifically.
\nI’m already smelling versionitis… <\/p>\n
[more wizened geeks will say apologetic things like:<\/p>\n
#1 ah, but yes there is rb!
\n– Yes, but I’m coming at this from a fresh angle, and I don’t necessarily know about that.<\/p>\n
#2 This is quite debian specific!
\n– Yes, but it is a rather major distro..
\n]<\/p>\n
Lets see whats available from testing repo.<\/p>\n
apt-cache search -t testing ^ruby | grep 1.9<\/p>\n...
\nruby1.9.1 - Interpreter of object-oriented scripting language Ruby
\nruby1.9.1-dev - Header files for compiling extension modules for the Ruby 1.9.1
\nruby1.9.1-examples - Examples for Ruby 1.9
\nruby1.9.1-full - Ruby 1.9.1 full installation
\nruby1.9.3 - Interpreter of object-oriented scripting language Ruby, version 1.9.3
\n<\/code><\/p>\n
Ok, so 1.9.3 should do it, lets install that.<\/p>\n
\napt-get install -t testing ruby1.9.3
\n<\/code><\/p>\nRe-run the Bundle installer, and…<\/p>\n
\nInstalling cloudfuji_paperclip (3.0.3)
\nGem::InstallError: cloudfuji_paperclip requires Ruby version >= 1.9.2.
\nAn error occurred while installing cloudfuji_paperclip (3.0.3), and Bundler cannot continue.
\nMake sure that `gem install cloudfuji_paperclip -v '3.0.3'` succeeds before bundling.
\n<\/code><\/p>\nHmm…
\nLets double check.<\/p>\n
\n> ruby --version
\nruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]
\n<\/code><\/p>\nLets see. Ruby 1.9.3 >= 1.9.2 in my math book, so wtf.<\/p>\n
I can even install it fine manually, via “gem install cloudfuji_paperclip -v ‘3.0.3’” so its really full of poop.<\/p>\n
I decide to take a different tack –
\nLooking at the gems folder though, I don’t see the gem libraries for 1.9.3 there, so I guess Ruby is full of crap again, and lying about the error, although then why does building the gem manually NOT fail. Sigh.<\/p>\n
I decided to take the rvm route<\/p>\n
https:\/\/rvm.io -> curl -L https:\/\/get.rvm.io | bash -s stable –ruby<\/p>\n
then<\/p>\n
source \/etc\/profile.d\/rvm.sh<\/p>\n
(still need to add to apache www-data group, but first lets get this compiled)<\/p>\n
rvm trundled away and installed 1.9.3 gems, so that *finally* cloudfuji_paperclip wasn’t bitching.<\/p>\n
…and we get to the next error.<\/p>\n
An error occurred while installing pg (0.12.2), and Bundler cannot continue.
\nMake sure that `gem install pg -v '0.12.2'` succeeds before bundling.<\/code><\/p>\nI run that manually, and<\/p>\n
gem install pg -v '0.12.2'
\nBuilding native extensions. This could take a while...
\nERROR: Error installing pg:
\n\tERROR: Failed to build gem native extension.<\/p>\n \/usr\/local\/rvm\/rubies\/ruby-1.9.3-p374\/bin\/ruby extconf.rb
\nchecking for pg_config... no
\nNo pg_config... trying anyway. If building fails, please try again with
\n --with-pg-config=\/path\/to\/pg_config
\nchecking for libpq-fe.h... no
\nCan't find the 'libpq-fe.h header<\/code><\/p>\n
apt-get install libpq-dev solves that one.<\/p>\n
…and<\/p>\n
bombing on sqlite.<\/p>\n
apt-get install sqlite3<\/p>\n
retry<\/p>\n
Its at this point I start thinking about puppet and how that does dependencies in a graceful manner, but I digress.<\/p>\n
..and because I forget the development libraries, I need to also get those.<\/p>\n
apt-get install libsqlite3-dev <\/p>\n
Retry the bundle install, and *finally* getting a build.<\/p>\n
Oh joy.<\/p>\n
So, lets try run it.<\/p>\n
bundle exec rake db:create db:migrate kandan:bootstrap<\/p>\n
== CreateAttachments: migrating ==============================================
\n-- create_table(:attachments)
\n -> 0.0015s
\n== CreateAttachments: migrated (0.0016s) =====================================<\/p>\n== AddSessionsTable: migrating ===============================================
\n-- create_table(:sessions)
\n -> 0.0011s
\n-- add_index(:sessions, :session_id)
\n -> 0.0004s
\n-- add_index(:sessions, :updated_at)
\n -> 0.0004s
\n== AddSessionsTable: migrated (0.0020s) ======================================<\/p>\n
== DeviseCreateUsers: migrating ==============================================
\n-- create_table(:users)
\n -> 0.0435s
\n-- add_index(:users, :email, {:unique=>true})
\n -> 0.0005s
\n-- add_index(:users, :ido_id, {:unique=>true})
\n -> 0.0005s
\n-- add_index(:users, :authentication_token, {:unique=>true})
\n -> 0.0005s
\n== DeviseCreateUsers: migrated (0.0452s) =====================================<\/p>\n
== CreateChannels: migrating =================================================
\n-- create_table(:channels)
\n -> 0.0011s
\n== CreateChannels: migrated (0.0011s) ========================================<\/p>\n
== CreateActivities: migrating ===============================================
\n-- create_table(:activities)
\n -> 0.0012s
\n== CreateActivities: migrated (0.0013s) ======================================<\/p>\n
== AddGravatarHashToUsers: migrating =========================================
\n-- add_column(:users, :gravatar_hash, :text)
\n -> 0.0007s
\n== AddGravatarHashToUsers: migrated (0.0007s) ================================<\/p>\n
== AddActiveToUsers: migrating ===============================================
\n-- add_column(:users, :active, :boolean, {:default=>true})
\n -> 0.0007s
\n== AddActiveToUsers: migrated (0.0007s) ======================================<\/p>\n
Creating default user...
\nCreating default channel...
\nrake aborted!
\nundefined method `to_i' for #
\n\/usr\/local\/rvm\/gems\/ruby-1.9.3-p374\/gems\/activemodel-3.2.11\/lib\/active_model\/attribute_methods.rb:407:in `method_missing'
\n\/usr\/local\/rvm\/gems\/ruby-1.9.3-p374\/gems\/activerecord-3.2.11\/lib\/active_record\/attribute_methods.rb:149:in `method_missing'
\n\/usr\/local\/rvm\/gems\/ruby-1.9.3-p374\/gems\/activerecord-3.2.11\/lib\/active_record\/connection_adapters\/column.rb:178:in `value_to_integer'
\n\/usr\/local\/rvm\/gems\/ruby-1.9.3-p374\/gems\/activerecord-3.2.11\/lib\/active_record\/connection_adapters\/column.rb:78:in `type_cast'
\n\/usr\/local\/rvm\/gems\/ruby-1.9.3-p374\/gems\/activerecord-3.2.11\/lib\/active_record\/attribute_methods\/dirty.rb:86:in `_field_changed?'
\n\/usr\/local\/rvm\/gems\/ruby-1.9.3-p374\/gems\/activerecord-3.2.11\/lib\/active_record\/attribute_methods\/dirty.rb:63:in `write_attribute'
\n\/usr\/local\/rvm\/gems\/ruby-1.9.3-p374\/gems\/activerecord-3.2.11\/lib\/active_record\/attribute_methods\/write.rb:14:in `channel_id='
\n\/home\/cubieboard\/chat\/kandan\/lib\/tasks\/kandan.rake:35:in `block (3 levels) in '
\n\/home\/cubieboard\/chat\/kandan\/lib\/tasks\/kandan.rake:23:in `each'
\n\/home\/cubieboard\/chat\/kandan\/lib\/tasks\/kandan.rake:23:in `block (2 levels) in '
\n\/usr\/local\/rvm\/gems\/ruby-1.9.3-p374\/bin\/ruby_noexec_wrapper:14:in `eval'
\n\/usr\/local\/rvm\/gems\/ruby-1.9.3-p374\/bin\/ruby_noexec_wrapper:14:in `'
\nTasks: TOP => kandan:bootstrap
\n(See full trace by running task with --trace)<\/code><\/p>\nOh look, *what* a suprise. Another error.
\nI’m starting to think that nobody actually tests this stuff in real life.<\/p>\n
undefined method `to_i’<\/p>\n
A bit of googling, and it looks like Ruby has changed functionality, and broken things in 3.2.3<\/p>\n
See – http:\/\/stackoverflow.com\/questions\/13348980\/activerecord-to-i-method-removed-in-rails-3-2-9<\/p>\n
Plus, there are some security issues to in Rails (of course).<\/p>\n
*and* Kandan guys have cancelled it.<\/p>\n
However someone else has forked it, and is updating it.<\/p>\n
So, lets wipe all of that, and start again, shall we.<\/p>\n
-> https:\/\/github.com\/kandanapp\/kandan<\/p>\n
cd ..
\nrm -r kandan –with-prejudice
\ngit clone https:\/\/github.com\/kandanapp\/kandan<\/p>\n
edit the config\/database.yaml<\/p>\n
Add some sqlite3 (hey, the rest is, and at this point I just want something testable, I can tweak later).<\/p>\n
production:
\n adapter: sqlite3
\n host: localhost
\n database: db\/production.sqlite3
\n pool: 5
\n timeout: 5000<\/p>\n
save.<\/p>\n
exec rake db:create db:migrate kandan:bootstrap<\/p>\n
Done. Yay.<\/p>\n
Now to test.<\/p>\n
bundle exec thin start
\n>> Using rack adapter
\n>> Thin web server (v1.3.1 codename Triple Espresso)
\n>> Maximum connections set to 1024
\n>> Listening on 0.0.0.0:3000, CTRL+C to stop<\/p>\n
Ok, now *thats* finally working, I just need to setup a apache_proxy to that port on the actual url it will be sitting on, and finally it should work.<\/p>\n
*Famous last words*.<\/p>\n
Way more painful than it really needed to be. Grr…<\/p>\n","protected":false},"excerpt":{"rendered":"
As my friends in high places have been talking about Ruby for a long long time now, I thought I might take a look at installing a Ruby based app on one of our servers. Sure, I could have hosted it on Heroku or similar (as I know people that know people), but I tend […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[25,4],"tags":[438,437],"class_list":["post-927","post","type-post","status-publish","format-standard","hentry","category-technical-mumbo-jumbo","category-useful-info","tag-kandan","tag-ruby"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/posts\/927","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/comments?post=927"}],"version-history":[{"count":6,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/posts\/927\/revisions"}],"predecessor-version":[{"id":930,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/posts\/927\/revisions\/930"}],"wp:attachment":[{"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/media?parent=927"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/categories?post=927"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.computersolutions.cn\/blog\/wp-json\/wp\/v2\/tags?post=927"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}