-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forum Operator #19
Comments
@alexej996, I've just assigned you to this role, reflecting the fact that you're actually doing this work. Could you please do a monthly update comment here for December, per #57 (comment). Specifically, could you please address the two recent outages of the forum, and what you plan to do to prevent these in the future? I think there are a couple major issues here:
Thanks! |
2017.12 updateDiscourse forum was upgraded at least once this month during the second forum outage on 27th of December to the current latest version 1.9.0.beta17. There were two outages of the forum for still unknown reasons. First one was on 7th of December and second was on 27th of December. Both happened during work days while I wasn't available until the evening. In future I will try making a bash script to automate restarts of Discourse in case forum is down. This month we had increase in users and user visits as well as posts and topics. |
@alexej996 Great thanks for the update. |
Yes I'm available as backup for the forum. |
Thanks, @Emzy. @alexej996, could you work out with @Emzy what being a "backup" means and add it to the role spec? Doesn't have to be elaborate. Should just make it clear what the responsibility of the backup is, when and to what they are expected to respond, etc. @Emzy, I've added you as an assignee here to indicate that you're the 'backup' or 'secondary' role owner here (we can figure out that terminology as we go here). Thanks, both. |
2018.1 updateDiscourse forum was updated once this month to the currently latest version 2.0.0.beta1 on 5th of January. The forum experienced no issues or down time this month and seems to be running as intended. We had an increase in user visits this month and a decrease in new users, topics and posts, as well as a decrease in total page views. |
2018.2 updateDiscourse forum was updated twice this month, on 3rd of February to version 2.0.0.beta2 and to version 2.0.0.beta3 on 16th. On 9th of February SSL certificates for the old forum domain (forum.bisq.io) were manually renewed. On 19th of February there was a temporary issue with the SSL certificates for the new domain, as they weren't renewed before expiry. These SSL certificates were automatically installed by Discourse software, there were no warnings of their expiry nor did the software renew them automatically. Operating system was updated on 19th of February after SSL certificates were renewed. There was an increase in response time to topics in the last month, but decrease in overall activity on the forum. |
2018.3 updateDiscourse forum was updated once this month, on 8th of March to version 2.0.0.beta4. There were some issues with forum sending emails this month. Gmail seems to be suspicious of SMTP logins from the forum. On 26th of Match forum was migrated to the new bigger server. There was a decrease in forum activity this month as well. This month we had: |
2018.4 updateDiscourse forum has been updated twice this month. First time on 13th from version v2.0.0.beta4 to v2.0.0.beta6 and second time on 27th to currently latest version v2.0.0.beta7. We had more issues with emails this month, although not quite as severe. On 5th of April forum was reconfigured to use Mailjet for sending emails, instead of Gmail. This month activity on the forum decreased. We had: |
Cycle 53 reportForum activity is the same as last cycle. |
Cycle 54 reportForum activity is less than half of what it was last cycle. |
Cycle 55 reportForum activity further decreased from last cycle by about 30%. |
Cycle 56 reportForum activity tripled from last cycle. |
Attention @bisq-network/forum-operators: https://bisq.community is down and has been for at least the last two hours. |
No developments since the above? |
Cycle 58 reportThere was a huge problem with the VPS that was hosting the forum and unfortunately all data since the last backup was lost. Last backup that was stored offline on my personal computer was long time ago, from last year. The forum is now restored to that last backup and is back online. |
For Cycle 59Forum activity seems to have increased this cycle. |
For Cycle 60Forum activity slightly decreased from last cycle. |
Hi @alexej996, could you comment on the current state of backups for the Forum? I may have missed it, but I don't believe this was ever followed up on after the outage in April. Thanks. |
Sure, backups are done regularly every month now. I plan to do backup at the end of every cycle. |
For Cycle 61Forum activity was about the same as last cycle. |
For Cycle 62Forum activity has decreased in the total number of new posts, but the number of new topics and new contributors is about the same as last cycle. |
For Cycle 63Forum activity has increased by around 20% from last cycle. |
For Cycle 64Forum activity decreased about 25% from the last cycle. |
For Cycle 65Forum activity has doubled since the last cycle. |
This role is about operating and administering the Discourse forum at https://bisq.community.
Spec: https://github.com/bisq-network/roles/blob/master/forum-operator.adoc
The text was updated successfully, but these errors were encountered: