Discourse technicalities: Difference between revisions

From Freegle Wiki
No edit summary
Wiki revamp: restructure & modernise
 
(10 intermediate revisions by one other user not shown)
Line 1: Line 1:
[[Discourse|Discourse overview]]
== About Discourse ==
== About Discourse ==


[[https://www.discourse.org/|Discourse]] is open source software. It is run by a private business currently with a team of 33 staff who earn their keep by hosting Discourse for US$100+ per month. They are committed to keeping Discourse open-source and provide regular updates which are easily installed. Freegle uses the open-source version so there are no fees to pay. We do pay a small amount for our own backups, as well as some paid geek-time.
[https://www.discourse.org/ Discourse] is open source software, first released in 2013. From October 2025, Freegle's Discourse hosting moved to Communiteq; before that, it was self-hosted (see [[Discourse]] for background on the move). Freegle uses the open-source version, so there are no software licence fees, though we pay for hosting, backups, sending emails, and some paid geek time.


Discourse updates are notified to admins. Some updates can be installed by any admin; others will need to be done by geeks. There may be a small amount of down time during upgrades.
Discourse updates are notified to admins. Some can be installed by any admin; others need a geek. There may be a small amount of downtime during upgrades.


Discourse has many many configuration options, controllable by admins. In addition, Discourse can be "programmed". The API was used by the geeks to set up all the user accounts and set the right email choices. The theme appearance of the site has been tweaked.  
Discourse has many configuration options, controllable by admins, and can also be "programmed" via its API - which Freegle's geeks have used to set up user accounts, configure email choices, and tweak the site's appearance.


== Resilience ==
== Resilience ==


It is important that the Freegle Discourse system is resilient and independent of the main Freegle servers, so we can communicate if they are down!
It's important that Freegle's Discourse system is resilient and independent of the main Freegle servers, so volunteers can still communicate if those servers are down.


Discourse runs on a Bytemark server that is separate from the main Freegle servers in a separate data centre. Discourse is configured to back up all its data every day overnight. The data file is then automatically backed up to Google cloud storage. Five backups are kept on the main Discourse server. The Google cloud keeps backups for 90 days. Restoring from a backup has been tested. Note that any discussions or setting changes since the backup will be lost.
Before the move to Communiteq, Discourse ran on a Bytemark server separate from the main Freegle servers, in a separate data centre, with data backed up every night and copied to Google Cloud Storage: five backups kept on the Discourse server itself, and 90 days of daily backups kept in the cloud. Restoring from a backup was tested and worked, though any discussions or setting changes since the last backup would be lost. A standby Discourse instance was also kept on one of the main Freegle servers, ready to be brought into service quickly from the last good backup if needed.


You can still log in to Discourse even if MT is down. This is partly done by Discourse remembering your login in a cookie.  In addition the Discourse server remembers an hourly copy of MT logins to use if someone needs to login.
You can still log in to Discourse even if MT is down, partly because Discourse remembers your login in a cookie, and partly because the Discourse server caches MT logins every 30 minutes for use if someone needs to log in while MT is unavailable.


To cope in the event that the main Discourse server is unavailable for some time, a second Discourse instance has been set up on one of the main Freegle servers. This standby instance can be brought into service by the geeks fairly quickly using the last available good backup, ie the snapshot taken overnight.
== Mail in and out ==


== Mail in and out ==
Discourse can send and receive mail, independently of Freegle's normal email systems.
 
Outgoing mail is sent using a Mailgun account, which costs a little each month. Incoming mail arrives at a Google-hosted mailbox called "discoursereplies", described elsewhere, which is polled every few minutes for mail to process.
 
== To do ==


Discourse sends mail out and can receive receive mail in. Both these processes are independent of the normal Freegle email facilities.
* Update the FAQ, Terms of Service and Privacy pages on Discourse.
* See [https://www.discoursehosting.com/kb/your-discourse-forum-and-the-gdpr/ this guidance on Discourse and GDPR].


Mail is sent using a free Mailgun account.
There's plenty of help and support about Discourse at https://meta.discourse.org/.


Mail is received at a Google hosted mailbox called discoursereplies as described elsewhere. The mailbox is polled every few minutes for mails to process.
[[Category:Members, Discourse & App]]

Latest revision as of 12:00, 17 July 2026

Discourse overview

About Discourse

Discourse is open source software, first released in 2013. From October 2025, Freegle's Discourse hosting moved to Communiteq; before that, it was self-hosted (see Discourse for background on the move). Freegle uses the open-source version, so there are no software licence fees, though we pay for hosting, backups, sending emails, and some paid geek time.

Discourse updates are notified to admins. Some can be installed by any admin; others need a geek. There may be a small amount of downtime during upgrades.

Discourse has many configuration options, controllable by admins, and can also be "programmed" via its API - which Freegle's geeks have used to set up user accounts, configure email choices, and tweak the site's appearance.

Resilience

It's important that Freegle's Discourse system is resilient and independent of the main Freegle servers, so volunteers can still communicate if those servers are down.

Before the move to Communiteq, Discourse ran on a Bytemark server separate from the main Freegle servers, in a separate data centre, with data backed up every night and copied to Google Cloud Storage: five backups kept on the Discourse server itself, and 90 days of daily backups kept in the cloud. Restoring from a backup was tested and worked, though any discussions or setting changes since the last backup would be lost. A standby Discourse instance was also kept on one of the main Freegle servers, ready to be brought into service quickly from the last good backup if needed.

You can still log in to Discourse even if MT is down, partly because Discourse remembers your login in a cookie, and partly because the Discourse server caches MT logins every 30 minutes for use if someone needs to log in while MT is unavailable.

Mail in and out

Discourse can send and receive mail, independently of Freegle's normal email systems.

Outgoing mail is sent using a Mailgun account, which costs a little each month. Incoming mail arrives at a Google-hosted mailbox called "discoursereplies", described elsewhere, which is polled every few minutes for mail to process.

To do

There's plenty of help and support about Discourse at https://meta.discourse.org/.