Were you able to get HTTPS working with OneTimeSecret?

[brink668]

I am new to Docker and wanted to know if you were able to get HTTPS working with your Docker version of OneTimeSecret?

[carlasouza]

@brink668 I didn't try yet, but I think it is possible by setting this line to true. I can try to abstract that into a environment variable or on the puppet manifest, or both. What you think?

[brink668]

Hi Carla thank you for showing me that setting. I tried to get some other things to work but the Docker Environment is so new to me I need to learn this first. So at this point in time I am going to buy some books and watch some videos on the subject. I am too new to make sense of what is going on and don't want to waste your time.

Thank you though for your help. The site does load well and your docker version was the only one I got running successfully!

[D-3lf]

I got it working with ssl on a bare metal install by running thin with this command:

"bundle exec thin -e dev -R config.ru -p 7143 start --ssl --ssl-key-file ~/path/to/server.key --ssl-cert-file ~/path/to/server.crt"

However, if you plan to run this in production I'd deploy it behind nginx (or similar) and configure ssl there.

[brink668]

Thank you for the reply, I will have to check next week I am out town.

If your in the states have a happy memorial day weekend if not, have a
great weekend!

-Richard

On Thu, May 26, 2016 at 11:23 AM, mwgreenjr [email protected]
wrote:

I got it working with ssl on a bare metal install by running thin with
this command:

"bundle exec thin -e dev -R config.ru -p 7143 start --ssl --ssl-key-file
~/path/to/server.key --ssl-cert-file ~/path/to/server.crt"

However, if you plan to run this in production I'd deploy it behind nginx
(or similar) and configure ssl there.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#1 (comment)

*****************************************************This e-mail,
including any attachments, is intended only for use by the addressee(s)
named herein and may contain legally privileged and/or confidential
information. If you are not the intended recipient of this e-mail, you are
hereby notified any dissemination, distribution or copying of any part of
this e-mail is strictly prohibited; please contact the sender and
permanently delete the original and any copies of it.