1,035
edits
Tech WG: Difference between revisions
no edit summary
m (Jonny moved page Mastodon/Tech WG to Tech WG: Neuromatch isn't using the wiki!) |
No edit summary |
||
| Line 103: | Line 103: | ||
[[Mastodon/Tech WG#TODO]] | [[Mastodon/Tech WG#TODO]] | ||
|Link=https://discord.com/channels/1049136631065628772/1049184335514828860/1059601450793173042 | |Link=https://discord.com/channels/1049136631065628772/1049184335514828860/1059601450793173042 | ||
}}{{Message | |||
|Author=sneakers.the.rat | |||
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024 | |||
|Date Sent=23-07-04 21:16:38 | |||
|Channel=technical-wg | |||
|Text=yes agreed we should make a wiki guide to updating the instance. | |||
I need to log off for the day bc am visiting friends, but in short it's | |||
- start backup in linode (reminder to also set you up with an account there and add that to [[Tech WG#TODO]] [[Tech WG/Onboarding]] docs | |||
- do all the git work that we're familiar with to prepare the new deploy | |||
- check upgrade notes, usually on base masto release notes, to see if anything out of the ordinary is required | |||
- pull down new changes to server | |||
- potentially recompile yarn assets | |||
- potentially run database migrations | |||
- restart mastodon-* services | |||
and that's usually it. downtime is usually on the order of a few seconds (and we could explore how to make that zero, I think that's how the pros do it with like multiple servers) | |||
|Link=https://discord.com/channels/1049136631065628772/1049184335514828860/1125897989177753600 | |||
}} | }} | ||