This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
computing:peertube [2024/12/25 01:00] – oemb1905 | computing:peertube [2025/04/19 01:44] (current) – oemb1905 | ||
---|---|---|---|
Line 97: | Line 97: | ||
* GNU/Linux Tube: https:// | * GNU/Linux Tube: https:// | ||
- | So far so good, but so what?! Now, when the physical host crashes and/or any VMs fail, I have two ways to restore | + | Okay, the instances |
- | --- // | + | # upgrade instructions, |
+ | sudo systemctl stop peertube | ||
+ | sudo apt update | ||
+ | curl -sL https:// | ||
+ | sudo apt install -y nodejs | ||
+ | sudo systemctl stop peertube | ||
+ | cd / | ||
+ | sudo -H -u peertube bash -x ./ | ||
+ | sudo chown peertube: | ||
+ | sudo systemctl start peertube | ||
+ | # need to tailor this to each upgrade and use-case, this is an EXAMPLE only of updating yarn and its dependencies | ||
+ | sudo systemctl stop peertube | ||
+ | cd / | ||
+ | #sudo -u peertube yarn add @typescript-eslint/ | ||
+ | #sudo -u peertube yarn remove bare-fs bare-os | ||
+ | sudo -u peertube yarn install --pure-lockfile | ||
+ | cd client | ||
+ | sudo -u peertube yarn install --pure-lockfile | ||
+ | sudo systemctl start peertube | ||
+ | # restore favicon and primary logo | ||
+ | cd / | ||
+ | mv logo.svg logo.svg.original.bak | ||
+ | mv favicon.png favicon.original.bak | ||
+ | cp -ar / | ||
+ | |||
+ | Adjust to your needs of course ;) | ||
+ | |||
+ | --- // |