Posted by Codejoy
Tue, 24 Apr 2007 21:18:07 GMT
I finished my latest toy, and after 17 days of trying to get it deployed finally did. Huge pain in the rear. In either case I will announce it shortly. I also would like to stop for a second and point out the fact that Typo's ability to filter spam sucks. It says "allow for non-ajax comments", leaving it unchecked is supposed to limit spam NOT! This is horrid, and I would like to take this moment to say that spammers should be beaten to death with their own shoes.
Posted in Rails, Ruby | no comments
Posted by Codejoy
Thu, 01 Feb 2007 15:52:00 GMT
Finally, got rails and ruby and rflickr and RMagick all playing nice together... it took a bit but in the end I got it done. The drawinports way is the way I chose, and it worked well. The process is roughly like:
Use the MacOS X cd's to install the X11SDK package, and then the x11 package. This package (the x11 one) is hard to find, its on the cd in the "other packages" .mpkg file. Though I don't have the cd on me now so let me double check that name.
After thats done, you can get darwinports and follow the instructions here:
http://blog.nanorails.com/articles/2006/07/11/installing-rails-on-mac-os-x-tiger
A few gotcha's with RMagick, if you install it with the gem apparently you need to use:
require 'rubygems' before the
require 'RMagick'
Then you can install rflickr by calling:
sudo gem install rflickr --remote
and
Instead of:
require_gem 'rflickr'
do
require 'flickr'
as per here:
http://rubyforge.org/forum/forum.php?thread_id=11449&forum_id=4256
So all that to say I now have Ruby On Rails working with RadRails on my macOSX tiger intel core 2 duo. w00t
Posted in Rails, Ruby, MacOS X | Tags macos, radrails, rails, ruby, success, x, x11 | no comments
Posted by Codejoy
Tue, 30 Jan 2007 22:40:00 GMT
So I decided I need to get ruby on rails running...I did get it running using the one click install called "locomotion", but my curiosity got the better of me and I wanted to use
radrails. It was soon apparent that a normal install of Rails was needed so off to the net I go to find out all the info. It turns out
darwinports is used to get this ruby on rails thing going, and I follow this nice guide
here to do so.
Now for the problem, it turns out that I am getting this error when I try to install ruby gems, apparently after some hunting it turns out the
darwinports version of gems is broke (sudo port install rb-rubygems). Turns out much to my suprsie this is documented and you can google the exact error you get when you try to (sudo gem install -y rails). Now folks for the bad news, all the "fixes" I found on the net, all the things that said "oh ya its easy just do this...or change that line here" don't work. I realized I don't exactly recall installing ruby, as per the tutorial I used...it was already installed so perhaps things are getting mis matched for locations of install paths *shrug*, I am not a linux enough guru yet to figure all this out, so far. Rails is not working as it should...It seems to be in Locomotive but not on its own :( Hopefully I will be able to have a better report soon...
Posted in Rails | no comments
Posted by Codejoy
Sat, 20 Jan 2007 21:51:00 GMT
I am finally getting serious about Ruby, and Rails as i just went out and bought the book "Ruby for Rails". So far I am not that far into it, but I have my rails environment set up on my Ubuntu install, and once my macbook gets in there too. The most important Gems I use when using Ruby is:
The RMagick gem (image manipulation)
and the rFlickr gem (flickr API gem).
I have a few flickr toy ideas ruminating in my head so I will have to start seriously to get to coding on this. I have decided of all the web technologies out there, Rails is the one I want to become pro on. This is a hard choice, as I most likely will not use it at work ever (they are mostly JSF). Such is life...choose life, choose rails.
Posted in Rails, Ruby | Tags JSF, rails, ruby, Ruby for Rails | no comments
Posted by Codejoy
Wed, 25 Oct 2006 20:07:00 GMT
I might of jumped the gun, I figured the flickr links not working was operator error. But several things came together at onceu to make me think it was just flat out dead, it turns out had just the logging been working I would of seen the error instantly: "Expired api key for flickr api", WHA????? I double check, and it seems the installed flickr gem had someone elses' flickr api key in the flickr.rb file. A change of that, and not only am I back up and running but I am getting statistics too! :) Woo Hoo! :D Now if I could just stop the spam from coming in... :(
Posted in Rails, Ruby | no comments
