Discourse house-keeping

This topic will maintain a housekeeping activity log for this Discourse forum (forum.fossunited.org).

I have just made the following changes

2 Likes

Logged into Digital Ocean and updated as much as i could. thanks for adding my ssh key to the machine @mngsh . ref Manually update Discourse and Docker image to latest - Self-Hosting - Discourse Meta

  • update ubuntu to auto apply security patches
  • a number of ubuntu packages were outdated, which were updated
  • update ubuntu to the latest version of the LTS (20.04)
  • update docker server to the latest stable version ← the older version is unsupported by discourse so this had to be done
  • update discourse and discourse docker manager
  • cleanup - remove unused ubuntu packages and stopped, unused docker containers - reclaimed close to 30 GB of disk space

The whole thing took ~ 45 minutes, with frequent breaks and distractions in between for me.

2 Likes

I’ve updated the trust levels of a number of users - it looks like we hadn’t been updating the trust levels based on recent usage and given the incoming spam, it felt like the right time to empower members of the community

the following users are now level 4

the following users are now level 3

@Ganesh_Adimalupu is now level 2

In addition, I have made a number of changes to the “Spam Settings” to curb some of the spam that we have been seeing over the past two days. Much of the advice came from Tips for Preventing Spam - #6 by SaraDev - Site Management - Discourse Meta . Please also note that I have added a few “watched words” that prevent the user from posting if those words are used in the post

Update: I have updated “min first post typing time” to 30 seconds from the default of 3 seconds.

Minimum amount of time in milliseconds a user must type during first post, if threshold is not met post will automatically enter the needs approval queue. Set to 0 to disable (not recommended)

6 Likes

the spam situation is better now than before and “min first post typing time” had the most impact!

1 Like

The following users are now level 4 (highest trust level) - @Bodhish_Thomas , @Nemo , @Shree_Kumar, @Swastik_Baranwal and @Bowrna_Prabhakaran

All of them have also been granted moderation and admin rights. Ref Electing a FOSSUnited Governing Board - #38 by ashlesh

All of a sudden I remembered that the FOSS United mattermost instance runs on a manually run caddy command and not a service. I had the ssh access, so I’ve created a systemd service file /etc/systemd/system/mattermost.service. The command was run manually because the connection was tunneled via Cloudflare and I don’t remember why I did not do this earlier (maybe logical reason or dumb/ignorant behavior).

Whenever you do the next mattermost maintenance (or even informing everyone and doing this now), do this:

  • ps -aelf | grep 'caddy' | awk '{ print $4 }' | sudo xargs kill -9 ← to kill the current caddy instance running

  • sudo systemctl enable mattermost.service && systemctl start mattermost.service ← start the mattermost systemd service.

P.S: idk if it was my network, but the server/console was super slow and connection broke multiple times. Probably linode being pesky as always.

1 Like

thank you very much @mangesh