2022/11/16: Difference between revisions

From MeW
Jump to navigation Jump to search
Created page with "{{page/date|nav=Nov. 14 .. today .. (nothing newer yet) }}"
 
mNo edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{page/date|nav=[[../14|Nov. 14]] .. [[../16|today]] .. (nothing newer yet) }}
{{page/date|nav=[[../14|prev]] .. [[../16|today]] .. [[../17|next]] }}
==Upgrade Plan==
There's a bit of time-pressure to get the upgrade working because of a [https://portswigger.net/research/stealing-passwords-from-infosec-mastodon-without-bypassing-csp security vulnerability] in the RC version that just happened to be what we upgraded to, but I also don't want to crash the server again (as happened yesterday).
 
The team agrees that we need a test-deployment process. The broad outlines I've worked out:
* live image the TC server
* spin up a copy, and reconfig it to be dev.toot.cat
* make sure it's running ok as-is (data might have gotten munged by being live-imaged; if so, can do a pg data export/import)
* reconfig Nix to target dev.TC
* run the upgrade
* look at dev.TC and see if everything runs ok
 
Preparation needed before this can work:
* modify Nix scripts so they can switch target servers easily
* figure out what changes need to be made to the server image in order to run properly as dev.TC instead of TC
* write a subscript to automate those changes
 
Meanwhile, I need to do a little research to figure out how to nicely ask {{l/htyp|Git}} to compare two existing commits for me. (All of the relevant commits are {{l/htyp|Git/tag|tagged}}, fortunately.)

Latest revision as of 15:54, 18 November 2022

2026-05-30 Everything ok (as far as we know! 😅)
The wiki was successfully migrated this morning, yay! 🎉

Wednesday, November 16, 2022 (#320)
Tuesday Wednesday Thursday

prev .. today .. next

Upgrade Plan

There's a bit of time-pressure to get the upgrade working because of a security vulnerability in the RC version that just happened to be what we upgraded to, but I also don't want to crash the server again (as happened yesterday).

The team agrees that we need a test-deployment process. The broad outlines I've worked out:

  • live image the TC server
  • spin up a copy, and reconfig it to be dev.toot.cat
  • make sure it's running ok as-is (data might have gotten munged by being live-imaged; if so, can do a pg data export/import)
  • reconfig Nix to target dev.TC
  • run the upgrade
  • look at dev.TC and see if everything runs ok

Preparation needed before this can work:

  • modify Nix scripts so they can switch target servers easily
  • figure out what changes need to be made to the server image in order to run properly as dev.TC instead of TC
  • write a subscript to automate those changes

Meanwhile, I need to do a little research to figure out how to nicely ask Git to compare two existing commits for me. (All of the relevant commits are tagged, fortunately.)