studio/blender-studio-tools
13
32
Fork 19
Code Issues 22 Pull Requests 4 Projects Releases 1 Activity

Docs: Improve Workstation Section #95

Merged
Nick Alberelli merged 11 commits from docs/td-maintence-guide into main 2023-06-27 19:04:40 +02:00
Conversation 0 Commits 11 Files Changed 2 +5 -5
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 462605b183 - Show all commits

10
docs/td-guide/workstations/maintaince.md
View File

@ -1,7 +1,7 @@
# Workstation System Maintenance # Workstation System Maintenance
## How to Update Build Server & Clients ## How to Update Build Server & Clients
The script will pull all of the latest changes from the main gentoo repository and initiate a system update. When done, it will ask if you want to push out the changes to the clients. The clients checks for updates every five minutes. If the server signals that there are updates, they will perform a sync with the build server and download and install all updated packages. To update Client Workstations; the Build Server will pull all of the latest changes from the [main gentoo repository](https://wiki.gentoo.org/wiki/Ebuild_repository#:~:text=The%20Gentoo%20ebuild%20repository%20is%20the%20main%20ebuild%20repository%20for,to%20be%20available%20to%20Portage.) and compile a system update. When done, it will ask if you want to push out the compiled changes to the clients. The clients checks for updates every five minutes. If the build server signals that there are updates, the clients will perform a sync, downloading the compiled packages from the build server and installing all updated packages.
1. `ssh user@build-server-addr` connect to your build server via ssh 1. `ssh user@build-server-addr` connect to your build server via ssh
2. Use `su` to Login as root or login as root directly 2. Use `su` to Login as root or login as root directly
@ -9,19 +9,19 @@ The script will pull all of the latest changes from the main gentoo repository a
4. Run `update_build_server.sh` 4. Run `update_build_server.sh`
## Update addons on `/shared/software/addons` ## Update Add-ons in `/shared/software/Add-ons`
The software inside the `shared/software/addons` directory are the [Blender Studio Pipeline addons](https://studio.blender.org/pipeline/addons/overview). These addons are considered Live Packages. Live Packages are packages that track the source-code repository directly and are not tied to a specific release. The software inside the `shared/software/addons` directory are the [Blender Studio Pipeline Add-ons](https://studio.blender.org/pipeline/Add-ons/overview). These Add-ons are considered Live Packages. Live Packages are packages that track the source repository directly and are not tied to a specific release.
::: warning Temporary Solution ::: warning Temporary Solution
This is a temporary solution that will be depreciated and replaced with project based addons. This is a temporary solution that will be depreciated and replaced with project based Add-ons.
::: :::
1. `ssh user@build-server-addr` connect to your build server via ssh 1. `ssh user@build-server-addr` connect to your build server via ssh
2. Use `su` to Login as root or login as root directly 2. Use `su` to Login as root or login as root directly
3. Run `emerge -1 {package-name}` to update a live package. 3. Run `emerge -1 {package-name}` to update a live package.
- Run `emerge -1 flamenco` to update the [Flamenco](https://flamenco.blender.org/) manager/add-on - Run `emerge -1 flamenco` to update the [Flamenco](https://flamenco.blender.org/) manager/add-on
- Run `emerge -1 blender-studio-tools` to update the studio addons - Run `emerge -1 blender-studio-tools` to update the studio Add-ons
4. Run `date -R > /var/cache/update_info/timestamp.chk` to mark this update as the latest 4. Run `date -R > /var/cache/update_info/timestamp.chk` to mark this update as the latest
## Wake on LAN ## Wake on LAN