-
Data Down / Actions Up
- http://emberjs.jsbin.com/nayaho/edit?html,js - Interdependent select boxes. No observers.
- http://ember-twiddle.com/2d7246875098d0dbb4a4 - One Way Input
-
Plain JSBin's
-
Ember Version Base JSBin's
| git branch -m old_branch new_branch # Rename branch locally | |
| git push origin :old_branch # Delete the old branch | |
| git push --set-upstream origin new_branch # Push the new branch, set local branch to track the new remote |
Please read the new and updated version.
Sendy is a self hosted email newsletter application that lets you send trackable emails via Amazon Simple Email Service (SES).
You can deploy Sendy on Heroku using the following instructions (I assume you've already installed the heroku toolbelt).
| ValueObject = function(value) { | |
| this.value = value; | |
| } | |
| $.extend(ValueObject.prototype, { | |
| get: function() { | |
| return this.value; | |
| } | |
| }); |
| select.form-control + .chosen-container.chosen-container-single .chosen-single { | |
| display: block; | |
| width: 100%; | |
| height: 34px; | |
| padding: 6px 12px; | |
| font-size: 14px; | |
| line-height: 1.428571429; | |
| color: #555; | |
| vertical-align: middle; | |
| background-color: #fff; |
| # config/deploy.rb | |
| namespace :upstart do | |
| desc 'Generate and upload Upstard configs for daemons needed by the app' | |
| task :update_configs, except: {no_release: true} do | |
| upstart_config_files = File.expand_path('../upstart/*.conf.erb', __FILE__) | |
| upstart_root = '/etc/init' | |
| Dir[upstart_config_files].each do |upstart_config_file| | |
| config = ERB.new(IO.read(upstart_config_file)).result(binding) |
| class AppleRecord < Record | |
| end |
##Create an alias to MAMP's PHP installation
To do this, we can simply create an alias for our bash profile. We'll be doing this is nano, though you can do it in vim or a number of other editors as well.
Within the terminal, run:
nano ~/.bash_profile
This will open nano with the contents, at the top in a blank line add the following line:
| #Deploy and rollback on Heroku in staging and production | |
| %w[staging production].each do |app| | |
| desc "Deploy to #{app}" | |
| task "deploy:#{app}" => %W[deploy:set_#{app}_app deploy:push deploy:restart deploy:tag] | |
| desc "Deploy #{app} with migrations" | |
| task "deploy:#{app}:migrations" => %W[deploy:set_#{app}_app deploy:push deploy:off deploy:migrate deploy:restart deploy:on deploy:tag] | |
| desc "Rollback staging" |
I'm having trouble understanding the benefit of require.js. Can you help me out? I imagine other developers have a similar interest.
From Require.js - Why AMD:
The AMD format comes from wanting a module format that was better than today's "write a bunch of script tags with implicit dependencies that you have to manually order"
I don't quite understand why this methodology is so bad. The difficult part is that you have to manually order dependencies. But the benefit is that you don't have an additional layer of abstraction.