Differences

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

--- web2py_on_dreamhost [2017/01/25 09:01] – [Sending Email from Web2Py Using Google G Suite] jtkorb
+++ web2py_on_dreamhost [2019/05/10 07:09] (current) – [Installing Web2Py on DreamHost] jtkorb
@@ Line 12: / Line 12: @@
   $ cd ~
   $ virtualenv python
+  $ source python/bin/activate
+  $ pip install requests  # needed by cams app and others
-  * 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 57: / Line 59: @@
 ===== Remote Admin Access =====
+These steps allow remote browser access to the Web2Py administrative control panels (both the master panel at ''admin'' as well as the app-specific panels at ''MYAPP/appadmin''.
   * Enable https from the DreamHost [[https://panel.dreamhost.com/index.cgi?tree=domain.manage|domain management panel]].
@@ Line 62: / Line 66: @@
   * Wait for a few minutes for the certificate to get created and installed.
   * Restart the web server by touching tmp/restart.txt.
+  * Set an admin password.
+  $ python web2py.py -p 443 -a "secret-secure-password"
+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 redirect all accesses to be via https, there are two options:
+  - 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.