On 02/11/2012 03:12 PM, Volker Braun wrote:
If you want to compile the flask notebook then I think we should
recommend installing openssl-dev but not require it. So on machines
without ssl it'll just build without ssl support, easy.
For distributed binaries we don't need ssl headers, only ssl libraries.
Its fine (by most legal opinions) to distribute binaries that link to
ssl on OS'es that ship with openssl.
(Disclaimer: I have never used the notebook.)
When ruby became popular for web apps, there was a similar problem. All
of the existing application servers sucked, so new ones popped up just
to run rails.
Rather than build SSL support into the application servers, everyone
deployed apache or nginx as an SSL proxy in front of them. Could this
work for the sage notebook?
The notebook would always run on e.g. localhost:8080 unencrypted,
without linking to OpenSSL. If someone wants to make his notebook server
public, he downloads nginx/apache and a tiny config file that proxies
0.0.0.0:8080 to localhost:8080, possibly using SSL.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
