Using Ember initializers and injections to setup the `currentUser` within your app.

account_routes.js

App.AccountEditRoute = Ember.Route.extend({
  setupController: function(controller) {
    controller.set('content', this.get('currentUser'));
  }
});

index.html.haml

%noscript
  .container
    .alert
      %strong
        Javascript is disabled!
      The AppName UI is built entirely in Javascript, as such you need to enable
      Javascript in your browser to continue.

:javascript
  var currentUser = jQuery.parseJSON('#{current_user_json}');

injections.js

Ember.Application.initializer({
  name: "currentUser",

  initialize: function(container, application) {
    var store = container.lookup('store:main');
    var obj = store.load(CrashLog.User, currentUser);

    container.optionsForType('user', { instantiate: false, singleton: true });
    container.register('user', 'current', CrashLog.User.find(obj.id));
  }
});

Ember.Application.initializer({
  name: "injectCurrentUser",
  after: 'currentUser',

  initialize: function(container) {
    container.injection('controller:application', 'currentUser', 'user:current');
    container.typeInjection('route', 'currentUser', 'user:current');
  }
});

Is there a non-private alternative to typeInjection?

@amaanr @AlexanderZaytsev I use the readiness calls that @listrophy suggests.

Remember to tell currentUser Initializer to fire up after loading store, otherwise store will be undefined

Ember.Application.initializer({
  name: 'currentUser',
  after: 'store',