/explore
|
You are here 
|
willj.net | ||
| | | | |
whatibroke.com
|
|
| | | | | Hey everyone, I was having a bit of trouble with CarrierWave on Amazon S3 today. When attempting to upload files that were larger than ~150kb I received one of the following errors (depending on config): getaddrinfo: Name or service not known carrierwave Excon::Errors::SocketError in PhotosController#create Broken pipe (Errno::EPIPE) Despite the vague error, the solution... | |
| | | | |
whatibroke.com
|
|
| | | | | Hey everyone, Just a quick post on how to retrieve a remote JSON source so I don't forget. require 'open-uri' require 'json' #Retrieve source (controller/model) @results = JSON.parse(open("http://www.myjsonsource.com/jsonfeed_num1").read) #In view That's all there is to it, let me know if you have any problems! | |
| | | | |
danq.me
|
|
| | | | | ... By 2005, Ruby had become more popular, but it was still not a mainstream programming language. That changed with the release of Ruby on Rails. Ruby on Rails was the "killer app" for Ruby, and it did more than any other project to popularize Ruby. After the release of Ruby on Rails, interest in Ruby shot up across the board, as measured by the TIOBE language index: It's sometimes joked that the only programs anybody writes in Ruby are Ruby-on-Rails web applications. That makes it sound as if Ruby on Rails completely took over the Ruby community, which is only partly true. While Ruby has certainly come to be known as that language people write Rails apps in, Rails owes as much to Ruby as Ruby owes to Rails. ... Two-Bit History As an early adopter of Ruby (... | |
| | | | |
macoy.me
|
|
| | | [AI summary] The article discusses the debate between free and proprietary software models, emphasizing the importance of community ownership, open-source practices, and the ethical implications of paywalled communities versus decentralized, open-source alternatives. | ||
