One Paragraph of project description goes here
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
| { | |
| "app/adapters/*.js": { | |
| "command": "adapter", | |
| "template": [ | |
| "import ApplicationAdapter from './application';", | |
| "", | |
| "export default ApplicationAdapter.extend({", | |
| "", | |
| "});" | |
| ], |
| $ brew update && brew doctor # Repeat, until you've done *all* the Dr. has ordered! | |
| $ brew install postgresql # You'll need postgres to do this... you may also need to 'initdb' as well. Google it. | |
| $ brew install elixir | |
| $ mix local.hex # Answer y to any Qs | |
| $ createuser -d postgres # create the default 'postgres' user that Chris McCord seems to like -- I don't create mine w/a pw... | |
| # Use the latest Phoenix from here: http://www.phoenixframework.org/docs/installation -- currently this is 1.0.3 | |
| # ** Answer y to any Qs ** | |
| $ mix archive.install https://github.com/phoenixframework/phoenix/releases/download/v1.0.3/phoenix_new-1.0.3.ez |
| require 'webrick' | |
| require 'webrick/https' | |
| require 'ds9' | |
| class HTTP2Server < WEBrick::HTTPServer | |
| SETTINGS = [ [DS9::Settings::MAX_CONCURRENT_STREAMS, 100] ] | |
| class HTTP2Response < WEBrick::HTTPResponse | |
| def initialize config, ctx, stream_id | |
| @ctx = ctx |
Hi Nicholas,
I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:
The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't
This post is also on my blog, since Gist doesn't support @ notifications.
Components are taking center stage in Ember 2.0. Here are some things you can do today to make the transition as smooth as possible:
Ember.Controller instead of Ember.ArrayController or Ember.ObjectControllerEmber.Controller, otherwise a proxy will be generated. You can use Ember.RSVP.hash to simulate setting normal props on your controller.| var EmberApp = require('ember-cli/lib/broccoli/ember-app'); | |
| var pickFiles = require('broccoli-static-compiler'); | |
| var mergeTrees = require('broccoli-merge-trees'); | |
| var vulcanize = require('broccoli-vulcanize'); | |
| var app = new EmberApp(); | |
| var polymerVulcanize = vulcanize('app', { | |
| input: 'elements.html', | |
| output: 'assets/vulcanized.html', |
| if Rails.env.test? | |
| require 'active_record/fixtures' | |
| require File.expand_path('../../test/config/geocoder.rb', __FILE__) | |
| DatabaseCleaner.strategy = :transaction | |
| class DatabaseResetter | |
| def self.start | |
| DatabaseCleaner.start |