| # to remove: | |
| $ sudo chmod 600 /System/Library/CoreServices/Search.bundle/Contents/MacOS/Search | |
| # reboot | |
| # to enable: | |
| $ sudo chmod 755 /System/Library/CoreServices/Search.bundle/Contents/MacOS/Search | |
| # reboot |
These steps were sufficient to upgrade Cult Cosmetics to Spree 2.0.4 from 1.3.3. Here are some details on our environment.
| # example from the documentation | |
| # ============================== | |
| params = ActionController::Parameters.new({ | |
| person: { | |
| name: 'Francesco', | |
| age: 22, | |
| pets: [{ | |
| name: 'Purplish', | |
| category: 'dogs' | |
| }] |
| class MyApp < Scorched::Controller | |
| render_defaults.merge!( | |
| engine: :haml, | |
| layout: :index | |
| ) | |
| #redirect after a 404 error | |
| after status:404 do | |
| redirect('/') | |
| end | |
| middleware << proc { |
This is a brain dump of my experience trying to get something going with Ember.js. My goal was to get to know the ins and outs of the framework by completing a pretty well defined task that I had lots of domain knowledge about. In this case reproducing a simple Yammer feed. As of this time, I have not been able to complete that task. So this is a subjective rundown of the things I think make it difficult to get a handle on Ember. NOTE: My comments are addressing the Ember team and giving suggestions on what they could do to improve the situation.
The new guides have pretty good explanation of the various parts of the framework; routers, models, templates, views. But it's not clear how they all get strapped together to make something that works. There are snippets of examples all over the place like:
App.Router.map(function() {
match('/home').to('home');
});
| # -*- mode: ruby -*- | |
| # vi: set ft=ruby : | |
| Vagrant::Config.run do |config| | |
| # All Vagrant configuration is done here. The most common configuration | |
| # options are documented and commented below. For a complete reference, | |
| # please see the online documentation at vagrantup.com. | |
| # Every Vagrant virtual environment requires a box to build off of. |
| class ActiveRecord::Base | |
| mattr_accessor :shared_connection | |
| @@shared_connection = nil | |
| def self.connection | |
| @@shared_connection || ConnectionPool::Wrapper.new(:size => 1) { retrieve_connection } | |
| end | |
| end | |
| ActiveRecord::Base.shared_connection = ActiveRecord::Base.connection |
Dear Rubyists,
I just lost a contract because of my code in a Rails project.
The specific code in question is related to a "posting a comment" feature. Here are the details:
In this project, "posting a comment" does not simply entail inserting a row into the database. It involves a procedure to yes, insert a row, but also detect its language, check for spam, send emails, and "share" it to Twitter and Facebook. I believe this algorithm should be encapsulated. I do not believe it belongs in a controller or a model. I do not believe Active Record callbacks should be used.
The "senior developer", whom is the stake holder's right hand man, said this:
As configured in my dotfiles.
start new:
tmux
start new with session name: