Deployed app shows iron:router welcome screen, local app works fine about meteor-restivus

[stubailo]

Should be fixed by #41

[kahmali]

Absolutely, @stubailo. I'm reviewing #41 now and it looks good so far (I'll post all this and more on the actual pull request later today). I just have an exam I need to cram for until Wednesday, so I may not be able to finish reviewing it until then. Sorry for the hold up on this! I look forward to getting rid of all these iron:router issues once and for all.

[stubailo]

No problem, @kahmali! Take as much time as you need.

[kahmali]

This is resolved by #46. Thanks so much for reporting it!

[renewsoqv]

Im receiving the same error on the file nimble_restivus.js:124 Uncaught ReferenceError: Route is not defined

[kahmali]

@renewsoqv There's no reason to configure or define routes on the client. Just do everything on the server and you should be fine. I'll be sure to only export Restivus on the server and make that very clear in the next update.

If you're not using Iron Router on the client, then you'll have to wait until v0.7.0 is published (or clone an early build from the 0.7.0 branch).

[renewsoqv]

@kahmali My config is as:

Restivus.configure
  useAuth: true
  prettyJson: true
  useClientRouter: false
  onLoggedIn: -> console.log "#{@user.email} (#{@userId}) logged in on api"
  onLoggedOut: -> console.log "#{@user.email} (#{@userId}) logged out on api"

On the common folder, i used it there following the instructions on docs. Should i move it to a server folder?

[kahmali]

@renewsoqv See #65 (specifically, this response). The short answer is yes. Config should happen on server.

[renewsoqv]

@kahmali Thanks, placing the config on the server folder solved my issue, plus the reading of #65 really clarify everything.

[kahmali]

Sorry for leaving the docs out of sync once that bug was discovered! I should have removed that information. I've created a new issue and I'll fix it in the next update (0.6.6).