secret_token in development

[darkleaf]

I see error in js console after Danthes.subscribe is executed.

error for /messages/new: Incorrect signature.

I run:

rackup danthes.ru -s thin -E production  # Rails.env == 'production'
rails s # Rails.env == 'development'

So I can't send messages because secret_token in development is 'secret' but secret_token in production is 'some random string'.

Please update generator or\and update README.

Thanks!

[bogdanRada]

+1. any update on this? i have same problem. I have a Procfile that i use to run the application using foreman

web: RAILS_ENV=development bundle exec rails s
faye: bundle exec rackup danthes.ru -s puma -E development

Although they seem to be in same environment, i get same error in console. What am i doing wrong?

[simonoff]

Simply set same password for all env. rails run in development and run danthes in production mode

[bogdanRada]

i figured it out now. It seems you're doing ::Digest::SHA1.hexdigest([config[:secret_token]) , so in javascript using the original secret_token fails because it will be different, instead i have to use the digested token . Thank you very much

[darkleaf]

@simonoff, I did so, but it is not too obvious.

[bogdanRada]

I honestly was not able to use the sign method directly in javascript, because no matter what token i was using, the message signature was always different from the server signature for when subscribing to a channel. because the timestamps seems to be different somehow.

So i made a little change to the subscribe_to helper to be able to pass the javascript callbacks for when receiving messages from the subscribed channel to the view helper.
You can see it here https://gist.github.com/bogdanRada/bedb803a5b9f40859209 and this works perfectly.