-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTPS support #240
HTTPS support #240
Conversation
@mvdbeek we could enable https with self-signed certs by default. Any objections? |
Yes, we have no access to port 443 on the IFB cloud, but if we don't forward 80 to 443 people can still leak their credentials. |
Also for dev purposes a self-signed cert is very annoying, you'll constantly have to turn off verification (bioblend, requests, etc). |
Ok, thats sad but a valid reason :) |
It's a pretty selfish reason though, there's no real problem to to say |
I trust @zfrenchee to update the docs after the merge. |
@bgruening I'm happy to -- would you be against a gh-pages branch to make a pretty website with docs for this project? I think that would be better. |
gh-pages are not needed anymore. Actually my plan was to use the new |
That's what github pages is! We had the same idea! On Sun, Sep 18, 2016 at 6:52 AM, Björn Grüning [email protected]
Alex Lenail |
@zfrenchee as it seems you have not updated the docs! ;) |
@bgruening sorry! Want me to update the |
@zfrenchee readme would be fantastic! |
To use a self-signed certificate and HTTPS, start with
-e USE_HTTPS=True
.If you have your own certificates, copy them to /export/{server.key,server.crt}.
If you want to use letsencrypt, start with
-e USE_HTTPS_LETSENCRYPT=True -e GALAXY_CONFIG_GALAXY_INFRASTRUCTURE_URL =<your_domain>
.If you use HTTPS, you also need to make sure port 443 is available.
@zfrenchee can you add the more extended documentation you had in galaxyproject/ansible-galaxy-extras#103 ?