Differences

This shows you the differences between two versions of the page.

--- web2py_on_dreamhost [2017/01/26 14:43] – [Remote Admin Access] jtkorb
+++ web2py_on_dreamhost [2018/04/22 14:53] – typo jtkorb
@@ Line 13: / Line 13: @@
   $ 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 go 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://github.com/web2py/web2py.git web2py.bikmort.com
@@ 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 ''parameters_443.py'' file.
-To "force" all accesses to be via https, there are two options:
+To redirect all accesses to be via https, there are two options:
-  - Use a .htaccess redirect as describe [[https://help.dreamhost.com/hc/en-us/articles/215747758-How-do-I-force-my-site-to-load-securely-with-an-htaccess-file-|here]].
+  - Use an .htaccess file to do a redirect as described by DreamHost [[https://help.dreamhost.com/hc/en-us/articles/215747758-How-do-I-force-my-site-to-load-securely-with-an-htaccess-file-|here]].
   - 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://www.mysite.com/myapp to https://www.mysite.com/public/myapp.  Verify by opening an incognito window; fix by clearing cached files in the browser.