--deployment switch is being stripped off and Gemfile.lock is rebuilt. If the file differs from what’s in the git repository, the deploy will fail with a somewhat mysterious error message. Work-around: Specify the bundler gem version to v1.0.3 (perhaps even up to v1.0.5) in your Gemfile.proxy_temp_path is writable. You can also control the size when this happens by adjusting proxy_temp_file_write_size. The more interesting thing is that if the directory is not writable, you won’t see an error message in the logs, but strace is still your friend.“Should I include
Gemfile.lockin a repository for a gem?”
“What library should I use for GUIDs?”
“Project Sprouts was originally designed (as AsProject) to solve a specific set of problems and was later entirely refactored to become a modular set of libraries that are built on top of Ruby, RubyGems and Rake.” — Luke Bayes
“So how will Sencha monetize? The company plans to sell its tools, like Sencha Animator, at a premium. It’ll also offer premium support plans.” — Tech Crunch
“Does anyone have experience with (slower) performance on EC2 compared to Heroku”
Some suggestions:
“Can you run cucumber with its own database instance?”
Responses:
... cucumber: <<: *TEST ...
rake db:test:prepare is wired to :test and won’t support a :cucumber in the database.yml without extra rake tasks that have continuing maintenance costs
Google deprecated their Local Search API and suggest to use the Maps API GoogleBar instead. However, as it turns out, the API GoogleBar is just a wrapper around the Local Search API, that was just deprecated. You could use the Google Places API instead, but that one is currently in developer preview only. What are we supposed to do Google? Googling it did not reveal any fully satisfying answer…
When attaching JQuery UI’s datepicker you should not use the class hasDatepicker since JQuery UI uses this class to mark DOM objects that already have a datepicker attached. So it won’t attach a datepicker to elements with that class.
It is possible to sort results in Solr using any criteria you want and use the Solr score for a secondary sort. Some people thought that you were only able to use the Solr score as your primary sorting criteria.
We request a PNG via IE7 from inside Parallels, but the file doesn’t get returned. The Nginx log just shows an empty line for the request.
Suggestion: Look also in Nginx’s error.log for the failing request. The request might be logged here and help find out what actually went wrong.
Sometimes .* in regular expressions matches more than we would like it too. Let’s say you have a string that includes some numbers you want to extract from a string. Our string might look like this:
some text 123 more text
now we might try to use the following regular expression to get the 123.
.*([d]+)
However, this will only get us the 3. This happens because .* will match as match as possible. Adding a ? will change this to only match what is needed.
.*?([d]+)
Now we get the 123 as desired.
A nice toll to experiment with regular expressions is rubular.com. Rubular allows you to see the effects of your regex in combination with an example string instantly.
Sarah will give a Ruby introduction class for kids at RubyConf. However, there won’t be any Internet connection available, but the participants will need to install several gems.
A solution to this problem is the gem geminabox which allows you to run a server providing gems. Other users who have geminabox installed then are able to install gems from that server.
bundle install --without test excludes the test group in your Gemfile from the install. It works well for reducing the size of your Heroku slug. However, there’s a glitch with this option on Heroku — when you specify it, Heroku reinstalls every included gem every time you deploy. It does respect your Gemfile.lock, so you’re trading a smaller slug for a longer deploy.
Pivotal’s open source CIMonitor project now supports OpenID! Thanks Tyler and Josh.
Arel has a bug that makes it difficult to use in rails console. Every time you add a predicate, the number of internal objects in the Arel result increases exponentially. So, by the time you have 5 or 6 predicates, the console finishes generating the expression more or less instantly, and then spends 15+ minutes calling to_s on the resulting Arel object in order to display it to you. tl;dr: when you’re playing with Arel in rails console, end every line with ; nil to avoid having it print out the result. The exponential object explosion will be fixed in Rails 3.1.