Tech WG/Ops Diary
22-12-16 Upgrading Linode Ram
Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram Following the instructions to
Tech WG/Ops Diary#22-12-16 Upgrading Linode Ram Mission accomplished. by god we've done it
22-12-24
OK Tech WG/Ops Diary#22-12-24 going to pull in a few upgrades: https://github.com/NeuromatchAcademy/mastodon/pull/7
- Mathjax
- Larger Post Previews
- Default false notifications for new follows
- Autofollow accounts
And also pulling in updates from upstream glitch-soc, which in my test run means that we have to upgrade node from 14 to 16
23-01-20 Installed NTP to sync system clock
Tech WG/Ops Diary#23-01-20 Installed NTP to sync system clock This was done to resolve a 2FA issue involving Authy (a TOTP app) https://discord.com/channels/1049136631065628772/1049184335514828860/1065990577381974067
23-03-29
ok Tech WG/Ops Diary#23-03-29: going to pull in dev branch and deploy to tha server: https://github.com/NeuromatchAcademy/mastodon/pull/13
I thought this had fetch all replies in it but i need to rebase it and also now that we know how to write them i want to write some tests....
It does have Better Code Blocks in it from <@485848481995423755> : https://github.com/NeuromatchAcademy/mastodon/pull/9
wish e luck
23-04-25
Tech WG/Ops Diary#23-04-25: restarted systems services as we were hitting swap limits https://neuromatch.social/@manisha/110259466647197417
23-05-19
Tech WG/Ops Diary#23-05-19: We are attempting to Upgrade Mastodon to 4.1.2 and also merge in Exclusive Lists, wish us luck.
We begin with what is probably the worst way to do it based on the conversation in <#1049184335514828860> , specifically:
- main -> dev,
- upstream -> dev,
- dev -> pr,
- pr -> dev,
- dev -> main
https://discord.com/channels/1049136631065628772/1049184335514828860/1109355378178789396
Tech WG/Ops Diary#23-05-19: TODO check out how user-specific settings were reformatted re: config/settings.yml. See also https://discord.com/channels/1049136631065628772/1049184335514828860/1109359788602707988 and https://discord.com/channels/1049136631065628772/1049184335514828860/1109360742433558548
ok Tech_WG/Ops_Diary#23-05-19: We conclude this evening having gotten all the way to the last stage where we pull back to main and then deploy. see preceding chat logs for history and also for the millionth time WikiBot#TODO implement archiving ranges of posts
23-05-22
Tech WG/Ops Diary#23-05-22: What up it's me and we're about to deploy Exclusive Lists and update to 4.1.2. starting by making a linode backup and then following instructions on https://github.com/mastodon/mastodon/releases/tag/v4.1.2
23-06-27
Tech WG/Ops Diary#23-06-27: restarted systems services as we were hitting swap limits https://neuromatch.social/@manisha/110616054514875151 This time I remembered to take a screenshot before and after
23-07-07
Tech WG/Ops Diary#23-07-07: masto 4.1.3 update -- security patch. Jonny's on the road so Lina and Manisha are going to give this a try. If we muck something up, please be kind đ„ș starting by making a linode backup and then following instructions on ...
oh wait! dang they already released 4.1.4 just an hour ago https://github.com/mastodon/mastodon/releases/tag/v4.1.4
4.1.3 from yesterday: https://github.com/mastodon/mastodon/releases/tag/v4.1.3
23-07-09
Tech WG/Ops Diary#23-07-09: Updating reverse proxy config to the recommended one as root
cd /etc/nginx cd sites-enabled vim mastodon
search for "system" added the following two headers in that block as per the release notes:
`add_header X-Content-Type-Options nosniff;
add_header Content-Security-Policy "default-src 'none'; form-action 'none'";`
save test nginx configs are valid or not (w/o running)
`nginx -t`
all looked good
`nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful`
Reload nginx `nginx reload`
23-09-19
Tech WG/Ops Diary#23-09-19 - Upgrading to 4.2-RC2 while trying to write the Upgrade Mastodon docs. currently doing the merge from upstream and noticing db migrations for exclusive lists failing, but not fixing now because that would put the fixes in the `glitch-soc-main` branch which is a local mirror of upstream which gets force pushed. Seems like that should happen in the `merge-upstream` branch after upstream is merged
23-10-01
Tech WG/Ops Diary#23-10-01 I am ready to deploy v4.2 but I encountered a few issues while following the process mentioned in Upgrade_Mastodon. I'll update the wiki with the steps I took.
24-02-01
Tech WG/Ops Diary#24-02-01 - Patching some mysterious critical security vuln thread
(The vulnerability in question) https://github.com/mastodon/mastodon/security/advisories/GHSA-3fjr-858r-92rw
24-02-14
Tech WG/Ops Diary#24-02-14 - Patching two more security bugs thread!
24-04-17
Manisha: Saw a warning in the admin panel:
Could not connect to Elasticsearch. Please check that it is running, or disable full-text search
Checked ES status via root
service elasticsearch status
It showed status Failed.
Restarted ES
service elasticsearch restart
Status returned to active.
Had to wait a tiny bit before the warning in the admin panel disappeared.