Openssl added for https

[SidharthBansal]

@jywarren new Facebook settings allow the login through the localhost only if we are using https. I found that we can provide the https in development by creating the certificates by openssl gem and running the
passenger start --ssl --ssl-certificate localhost.crt --ssl-certificate-key localhost.key --ssl-port 3000 command instead of passenger start.

This blog might be helpful. https://www.devmynd.com/blog/rails-local-development-https-using-self-signed-ssl-certificate/

Also, I have changed the installation guidelines a little. Check it out.

[jywarren]

I think this is OK and if it does not interrupt the existing SSL config on production (@icarito can tell us it's ok or not?) then we should be fine and I"m OK merging this in. I think we're still seeing some issues with the travis containers so that may hold us up a bit first. Thanks!

[SidharthBansal]

OK great to hear that. Please check this twice on production before merging @icarito. Also, we need to notify the existing developers about the command to launch the passenger server is changed.

[SidharthBansal]

@jywarren I tried to understand the Travis issues but was not able to. Any help is greatly appreciated.

[jywarren]

Retriggering! Now it's solved...

[PublicLabBot]

	2 Messages
📖	@SidharthBansal Thank you for your pull request! I’m here to help with some tips and recommendations. Please take a look at the list provided and help us review and accept your contribution! And don’t be discouraged if you see errors – we’re here to help.
📖	This pull request doesn’t link to a issue number. Please refer to the issue it fixes (if any) in the body of your PR, in the format: Fixes #123.

Generated by 🚫 Danger

[jywarren]

Could we move this into the development gems only, since we won't be using this in production? Thanks!!!

[SidharthBansal]

yes for sure.

[jywarren]

And if you could change the docs -- the README or corresponding file -- but just say that passenger start is fine for default, but /if you're working on Facebook integration or something that needs SSL/, then you should use the command passenger start --ssl --ssl-certificate localhost.crt --ssl-certificate-key localhost.key --ssl-port 3000 -- then we should be fine and won't complicate things for most developers. Thanks!!!

[SidharthBansal]

@jywarren for the non-secure connection (HTTP) we can use port number 3000 using the passenger start command as we currently use.
For the secure connections, we can use the port number 3001. We will use passenger start --ssl --ssl-certificate localhost.crt --ssl-certificate-key localhost.key --ssl-port 3001 command.
We can't use one port for both HTTPS and HTTP. Hence, I have defined two different ports.
I have made the required changes in the readme and the config/environments/development file.
Thanks

[SidharthBansal]

I hope it is ready to be merged.

[jywarren]

Ah, i think this was affected by the previous issue of Dockerfile config. If you rebase it over the latest master branch, it should pass!

[SidharthBansal]

@jywarren can we merge this?

[jywarren]

Perfect, thank you!!!! 👍 👍 👍