このアカウントはもはや使用されていません。
This account is no longer active.
このアカウントに引っ越しました
We've moved to this account
>>> @JapanAnon <<<
よろしければ、どうぞフォローして下さい。
Feel free to follow.
Further Further Situation Update: I was wrong, also dumb. I can do an in-place update. Also, I've discovered tmux over the course of learning this.
Attempting upgrade today.
Thought Of The Day: Smooth seas do not make skillful sailors.
Further Situation Update: VPS uses LXM, so I'm not sure I can even do an in-place upgrade of the OS...afaik, I wouldn't be able to do a kernel update, and I'd need one for the new version. Rather than risk fucking things up further, I'm waiting for a response from the provider before taking any action. So the instance is forced to stay down for now.
Really wish release notes had mentioned this possibility, I could have just stayed at 2.0.7 until I sorted this out.
Situation Update: Can't roll back, so updating the server OS it is. Which means backing up everything from PeerTube and Pleroma in case it gets fucked during the upgrade.
The positive here is that I've finally been forced to learn how to do a proper backup of each, so at least the Great Crashening of March won't happen again (knock on wood).
For real, though, is there a way to roll an OTP release back to an earlier version? Apparently I need to upgrade the server OS to make this work otherwise.
Or build from source, but I don't know how to transition from OTP to source install.
このアカウントはもはや使用されていません。
This account is no longer active.
このアカウントに引っ越しました
We've moved to this account
>>> @JapanAnon <<<
よろしければ、どうぞフォローして下さい。
Feel free to follow.
知識は自由です
anonymous-japan.org
peertube.anon-kenkai.com
bitchute.com/channel/anonkenkai
youtube.com/user/ChanologyAgent
flote.app/japananon
twitter.com/JapanAnon