web2py_on_dreamhost
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
web2py_on_dreamhost [2017/01/25 09:37] – [Remote Admin Access] jtkorb | web2py_on_dreamhost [2017/01/28 14:34] – jtkorb | ||
---|---|---|---|
Line 13: | Line 13: | ||
$ virtualenv python | $ virtualenv python | ||
- | * Clone sources from Web2Py github site into web-server directory (using web2py.bikmort.com as an example): | + | * Clone sources from the Web2Py github site((You might prefer to got to github.com and create a fork of the Web2Py sources, then clone your fork. That's what all the cool kids do.)) into web-server directory (using web2py.bikmort.com as an example): |
$ git clone --recursive https:// | $ git clone --recursive https:// | ||
Line 70: | Line 70: | ||
This command will give errors (for among other reasons, a user process cannot listen on port 443), but it will have generated the necessary '' | This command will give errors (for among other reasons, a user process cannot listen on port 443), but it will have generated the necessary '' | ||
| | ||
+ | To redirect all accesses to be via https, there are two options: | ||
+ | - Use an .htaccess file to do a redirect as described by DreamHost [[https:// | ||
+ | - Use Web2Py Auth(..., secure=True) setting, but note that this change breaks Travis CI testing. | ||
+ | In either case, there might be cached browser files that break the redirect, for example, redirecting http:// |
web2py_on_dreamhost.txt · Last modified: 2019/05/10 07:09 by jtkorb