I strongly recommend using a frontend like ngix or Apache. The efficiency
> of the Sagenb server when doing encryption is low. Let an industrial
> strength web server handle that and the encryption. I just proxy a local
> instance of the Sagenb behind Apache when I want a secure connection and
> then all the certificate stuff is taken care of by the frontend. See this
> pull request which makes things work very cleanly, but has not been
> incorporated because it changes path names slightly:
> https://github.com/sagemath/sagenb/pull/328
>
>
By the way, my plan is to start looking at the active pull requests before
US Thanksgiving. Really wish there was a way to at least redirect the /pub
one - is it possible to add a rule somehow for those in one of the server
files like flask_version/base.py
@base.route('/pub')
as opposed to the options at
https://github.com/sagemath/sagenb/pull/328#issuecomment-137893789 that you
suggest, which seem to require additional effort by the user?
By the way, does that pull request (which somehow is stale, though I'm not
sure how that happened!) allow for using sagenb *without* a proxy? This
just makes it more easy to *use* one, right? E.g. for local installations
on your laptop!
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.
