What is a colophon?
We use the term colophon as a way to tell you something about the website you’re viewing. We do this for 2 reasons:
- To explain exactly how tiaa-forum.org is put together (what technologies and hosting we use in support of what you see on the site).
- If you know better technologies or practices than you see us using here, you might be able to suggest them to us for our consideration. The best way to do that is to post a topic in the forum category “#forum-site-feedback.” If you’re not a member of the forum (please, sign up! 😉 ), you can send email to email@example.com and at least one of our administrators will be happy to consider your suggestions.
The Discourse forum was originally brought up in late 2015 and made public in early 2016 (originally named naatw-forum.org, it was renamed tiaa-forum.org in late 2016).
It was the group conscience of the forum and the forum administrators to only allow forum members to share in the forum. The WordPress front end is used primarily for:
- giving potential new members an interface to request an invitation
- providing a “public” face to the forum:
- allows us to improve search engine optimization to allow others to find the forum easier (with the Discourse software, we had no simple way to improve our visibility on the web without risking forum security)
- provides a platform for publishing technical information that might be useful to non-members
- allowing us to develop tools in a WordPress environment which might be better supported going forward (e.g. – there seems to be more skilled talent available for a PHP/WordPress environment than the ruby/rails ember environment of the Discourse platform)
- supporting an ability for forum members to contribute financially to forum support
As a few attendees of the first couple of the National AA Technical Workshops looked into ways of persisting and extending conversations between annual workshops, several platform options (e.g. phpBB, Vbulletin, etc.) including both hosted services and stand-alone software. Initially, we tried a hosted decision support service, loomio.org , but found it primarily useful toward driving a decision rather than a useful discussion forum.
Some attractive features of setting up an instance of Discourse included (arbitrary – may be more):
- open source
- modern, responsive web interface
- emoji support
- markdown style editing
- scalable to small and large communities (some Discourse communities are in the 100’s of thousands and more members)
- fairly good support community (meta) with folks who are really into communities (developed by the same folks who brought us stackexchange and stackoverflow)
- wide community support and general use (thousands of popular forums)
- fairly simple administration
Discourse is packaged as docker container so it’s simpler to install, admin and keep updated (more in the Plumbing section below).
Front End (WordPress)
We (the forum admins) chose WordPress as a front end because of WordPress’s impressive popularity and market share, both in general and within the tiaa-forum.org member community. As we presume admins will all eventually rotate on or disappear, we felt using WP would give us the broadest talent pool whereby admins could be replaced when needed.
Our current configuration uses a fairly heavily modified TwentySeventeen theme. We wanted to use a standard (WordPress provided) theme for maximum simplicity but, to meet certain design suggestions, we opted to create a WordPress Child Theme to support a different placement of the navigation menu as well as some widgets to allow for calls to action (e.g. sign up, login) in the header area. Since we were using a child theme, we also are doing quite a bit of additional customization to meet design/style tastes (e.g. using the child theme’s styles.css for managing over-all presentation of the site). In the future, we may find a better/simpler way to use a supported non-WordPress provided theme while accomplishing other design priorities using available plugins.
As of 8/15/18, we are still “trying out” various plugins. We are always open to suggestions based on others’ experiences…
- Akismet — a common WP anti-spam filter used primarily for blocking spam in comments (which we have turned off) but we hope it will be useful in protecting us from other vulnerabilities
- Arconix FAQ – allows us to have a FAQ outside our Discourse forum (in public)
- Duplicator – allows us to create backups/images of our WP site easily. Can also automate this using their pro version which we will probably want to do at some point
- WP Mail SMTP – used to work with our mail relay/gateway solution. We had attempted to use Easy WP SMTP – but, even after we handed them a code for a fixing a buf we needed, it wasn’t supported so we moved to this other plugin…
- Formidable Forms – this forms package allows us to do fairly simple forms for sign up, contact and donations. Since their Stripe plugin (Stripe is our is our payment processor for contributions) requires their pro version, we had to upgrade to the paid version. As of ~2/19, we (some members of the forum community) are currently working with them to get some features we need/want into the plugin. Ther
- Gutenberg – we’re trying this new WP provided editor out – probably a blog post coming on this…
- If Menu – allows us to show different navigation/pages based on whether a member is logged in or not
- Popup Maker – allows buttons f(e.g. for signup and login) to bring up forms
- Redirection – works with Discourse login to make sure the WP and Discourse instance maintain the same logged in state
- Simple history – tracks changes to the site so that a number of administrators can share work without stepping on each other as much…
- Widget Logic – allows us to use modal logic (e.g. when a member is logged in or not) with our widgets.
- WP-Discourse – this plugin is provided by the Discourse developers so that we can use Discourse as our login for our site and connect a WordPress environment to the Discourse environment via an API.
The entire site is hosted on a DigitalOcean virtual host. Unlike other hosting companies, you basically rent “raw iron” (the equivalent of a standalone computer) from the hosting company and, as such, one has to do all the basic system administration tasks (software installation, updates, backups, firewall management, etc.) oneself.
We (the initial forum admins) selected DO as a VPN provider because:
- we had some experience with them
- they were fairly competitive in price with other, similar services
- in 2015, they were one of the few providers that assured all disk was SSD based (has much higher performance) which impressed us
- they have a good reputation for support and ability to scale – reliability is assured as better than 99.99% uptime.
- the DO tutorials about setting up Discourse and WordPress droplets as well as the DO specific help on the Discourse support site (meta) and the WordPress support forums seemed to give us all the information we needed to get started with a deployment
Our entire site (all containers as explained below in the “Plumbing” section) is run on a single DO “droplet” (VPN) configured with one processor, 2GB memory, and 50 GB of storage.
We keep one “snapshot” of an image from each time we change something major in the configuration as well as we take automatic live backups weekly.
We also keep an near-equivalent droplet image we can quickly spin up or spin down for testing (both WordPress and Discourse) without impacting the production forum droplet.
When a request comes to the virtual machine (VM) from the web, based on the URL requested, the nginx server running on the VM will pass the transaction to either the container for WordPress (if tiaa-forum.org) or the container for Discourse (if discourse.tiaa-forum.org).
The WordPress environment is run on a Docker-compose container (actually, the WordPress instance and the Database server that supports it are run on two separate containers but managed from a single configuration file) which is running an Apache server supporting a PHP environment.
The forum Discourse environment is run on another Docker container which is running another nginx server supporting a ruby-on-rails environment.
As currently configured, all containers are run on the same virtual machine (VM). This can be changed in the future should the forum grow or should additional resources be required. While this may seem like a complicated configuration, web response per transaction is quite good.
Our outbound email services are currently supported by Sendgrid. As of late 2019, we’re peaking at over 110,000 emails/month from our forum.
Inbound email services (as well as some other administrative/documentation needs ) are served by a basic Google G Suite (using Google for non-profits) account.