Docs/Maho: Difference between revisions
m (format) |
(Added *arr updates) |
||
| Line 19: | Line 19: | ||
(Detail about ism's and how to administrate/add media) |
(Detail about ism's and how to administrate/add media) |
||
====*arr==== |
|||
Updates to the *arr suite are simple and should be done under the podman user. First log into the podman user <code>sudo su podman</code> and go to the podman compose directory <code>cd /opt/podman/compose/arr/</code>, then run the following one liner to pull new images (if there are any) and force recreate the stack <code>podman-compose pull && podman-compose up -d --force-recreate</code>. |
|||
<code>-d</code> daemonize's this stack (run in the background) |
|||
<code>--force-recreate</code> forces containers to be recreated with the updated image in case podman has issues taking down containers. |
|||
===Services=== |
===Services=== |
||
Revision as of 19:21, 4 January 2026
Maho holds a number of Graphical Processing Units (GPUs) and services either transcoding video or running Large Language Models (LLM's).
Hardware
Maho is a standalone Dell R730 server (2.5" drive bay variant)
Network daughter card has been swapped out for a Dell 165T0 Broadcom 57800S, a 2 port ethernet and 2 port SFP+ card.
2 GPU's are housed and used for compute workloads, a GTX 1060 6GB and a GTX 1070.
There are 3 open low profile PCIe slots.
Operating System
Mirrors runs Debian 13.
(Additional storage information)
Maintenance
Media is added to /salieri/jellyfin/import
(Detail about ism's and how to administrate/add media)
*arr
Updates to the *arr suite are simple and should be done under the podman user. First log into the podman user sudo su podman and go to the podman compose directory cd /opt/podman/compose/arr/, then run the following one liner to pull new images (if there are any) and force recreate the stack podman-compose pull && podman-compose up -d --force-recreate.
-d daemonize's this stack (run in the background)
--force-recreate forces containers to be recreated with the updated image in case podman has issues taking down containers.
Services
Services are based on this machine but may call remote machines (and therefore remote GPU's) for remote compute via rffmpeg (transcoding) or a OpenAI reverse proxy (LLM)
Jellyfin
Jellyfin is installed to its default location (location) and is reverse proxied via nginx. Media is located in /salieri/jellyfin/media with subfolders spanning into media types. Media inside this ../media folder is managed/renamed by the *arr suite. /salieri/jellyfin/imports is a holding directory for unsorted media. *arr has access to these folders as /download/(subfolder) and can be sorted futher/moved into ../media.
(add more jellyfin service detail)
*arr
The *arr suite is running inside docker containers on maho as a single host. The compose file can be found at /opt/podman/compose/arr/docker-compose.yaml and holds the *arr suite as a single service, allowing for one-liner updates/replaces.
(Detail about *arr setup and how to change settings)
Language Models
Small language models are to be hosted on the two separate GPU's via docker to allow different models running behind the reverse proxy. A user on LUG's Sillytavern (or any front end where an API can be called on) can then select what model to prompt.
(Allen thing)