Cursory overview of configuration details for a full openplans.org deployment.

As is evident from our architecture diagram, a full OpenPlans deployment consists of a number of different independent processes working together.  This page is for storing some of the details of how these pieces are configured.

The following describes the server delivery pipeline, as it's set up in our live and staging environments:

        browser / user agent
                 |
                 V
          Apache (port 80)
                 |
                 V
          Squid (port 81)
                 |
                 V
        Deliverance (port 4570) [includes vhoster, transcluder]
                 /|\
                / | \
               /  |  \
              /   |   \
             /    V    \
  Zope (8080)  WP(8090)  TaskTracker(5050)

The "WP" in this case stands for WordPress, which we'll be rolling out soon as a blogging solution.

You might wonder "where do these numbers come from?"

Apache knows about Squid, and Squid knows about Deliverance.  Deliverance is configured with force_port to know what it's "real" port is (80).  Deliverance is configured with the Zope (zope_uri), WP (blog_uri), and TT (tasktracker_uri) ports.  Each of these products knows about their own port (in zope.conf, wordpress-httpd.conf, and tasktracker's .ini file).  They each pick up their public location from information Deliverance sends to them (VHM for Zope, some custom fixups in WP, and some middleware and headers in TT).