Allow Pubnub to use SSL.

[bnazari]

Modify ruby settings to use SSL to allow PubNub to function.

https://www.pubnub.com/docs/ruby/api-reference-configuration

[coveralls]

Coverage decreased (-0.04%) to 88.891% when pulling a0e413b on bnazari:patch-7 into 67c2d68 on redcross:master.

[cecilia-donnelly]

@bnazari can you expand this PR message a bit? What does PubNub do in the application? Can you point to some documentation of why it needs SSL? Thanks!

[pjsier]

An update here, this looks like it won't cause problems, but I haven't been able to test it locally yet because of issues in my local environment relating to HStore field serialization. It seems like this is related to #119, so if it works for now we'll prioritize that upgrade first

[bnazari]

Still don’t know what this does. I fill like pulling the code from the application in general, as I suspect it was put in there at one point for mobile application development. Not sure if the notifications are received my some sort of watchdog elsewhere, which is causing me a bit of hesitation.

…

On Dec 12, 2017, at 11:55 AM, Patrick Sier ***@***.***> wrote: An update here, this looks like it won't cause problems, but I haven't been able to test it locally yet because of issues in my local environment relating to HStore field serialization. It seems like this is related to #119 <#119>, so if it works for now we'll prioritize that upgrade first — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#125 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAT00ZreN35TqGAXW9fmDuGp6rVRcKUvks5s_to8gaJpZM4QxGCP>.

[pjsier]

To close this one out, PubNub manages a lot of the real-time messaging functionality in the application. It can update the page with messages as they're received, but since we're getting an insecure content error right now that connection is blocked.

I tried out @bnazari's fix locally (adding a placeholder API key to make sure it loads the JS library), and it fixes the error. Updating the parameter only forces SSL connections if the current page isn't loaded over SSL, so this is pretty safe to update in general.