Add Runner class to monitor and activate ember apps

[seanpdoyle]

Should address #107 and #139

[rwz]

Does it work for you?

Any feedback from your projects @rondale-sc?

[seanpdoyle]

@rwz this worked great for me!

[seanpdoyle]

@rwz I've covered the positive use case, would it make sense also covering a negative case:

!path.starts_with?("/api/")

[rwz]

I guess it's automatically implied. Anyone who sees a lambda passed in as an option should figure out it could be used for negative case by just inverting the logic.

[rondale-sc]

@rwz @seanpdoyle Works on our production app without any changes!

LGTM

🍻

(kinda obvi, but it doesn't restart ember until the next request)

[rwz]

Released 0.3.0

[slashmili]

How does this enable option work?

I have this config for EmberCLI

EmberCLI.configure do |c|
  c.app :myapp,
    path: "ui/myapp",
    enable: -> path { !path.starts_with?("/api/") }
end

And I have these routes:

Rails.application.routes.draw do
  root 'application#index'
  scope "/api/v1" do
    resources :users
  end
end

When I open http://localhost:3000/api/v1/users it goes to Ember and it complains that

Uncaught UnrecognizedURLError: /api/v1/users

[seanpdoyle]

@slashmili I believe the root declaration must come last (at the bottom) in your routes file.

[slashmili]

Correct! Thanks

BTW it was not obvious though.

[seanpdoyle]

@slashmili I agree. However, root isn't an ember-cli-rails construct, but something that comes from Rails itself: http://guides.rubyonrails.org/routing.html#using-root

[tonywok]

@seanpdoyle I'm not super familiar with asset pipeline internals. We have some assets that are still managed by rails - (fonts, images, etc). Would it step on the ember-cli-rails middleware to also flip enabled to false on cases of /assets/. Looking through the source and I'm not quite sure how that lamba's "path" maps to a "request uri".