You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/documentation/docs/user-guide/installation/installing-package-manager.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ Although Package Manager can be used to copy any kind of file to/from a wide arr
19
19
:::caution
20
20
21
21
Sofie supports only one package manager running for a Studio. Attaching more at a time will result in weird behaviour due to them fighting over reporting the statuses of packages.
22
-
If you feel like you need multiple, then you likely want to run package manager in the split setup instead.
22
+
If you feel like you need multiple, then you likely want to run package manager in the distributed setup instead.
23
23
24
24
:::
25
25
@@ -60,7 +60,7 @@ This first run is necessary to get the Package Manager device registered with _S
60
60
61
61
Only one package manager can be running for a Sofie Studio. If you reached this point thinking of deploying multiple, you will want to follow the distributed setup.
62
62
63
-
### Simple setup
63
+
### Simple Setup
64
64
65
65
For setups where you only need to interact with CasparCG on one machine, we provide pre-built executables for Windows (x64) systems. These can be found on the [Releases](https://github.com/nrkno/sofie-package-manager/releases) GitHub repository page for Package Manager. For a minimal installation, you'll need the `package-manager-single-app.exe` and `worker.exe`. Put them in a folder of your choice. You can also place `ffmpeg.exe` and `ffprobe.exe` alongside them, if you don't want to make them available in `PATH`.
66
66
@@ -72,15 +72,15 @@ Package Manager can be launched from [CasparCG Launcher](./installing-connection
72
72
73
73
You can see a list of available options by running `package-manager-single-app.exe --help`.
74
74
75
-
In some cases, you will need to run the http proxy server component elsewhere so that it can be accessed from your Sofie UI machines.
75
+
In some cases, you will need to run the HTTP proxy server component elsewhere so that it can be accessed from your Sofie UI machines.
76
76
For this, you can run the `sofietv/package-manager-http-server` docker image, which exposes its service on port 8080 and expects `/data/http-server` to be persistent storage.
77
-
When configuring the http proxy server in sofie, you may need to follow extra configuration steps for this to work as expected.
77
+
When configuring the http proxy server in Sofie, you may need to follow extra configuration steps for this to work as expected.
78
78
79
-
### Distributed setup
79
+
### Distributed Setup
80
80
81
-
For setups where you need to interact with multiple CasparCG machines, or want a more resilient/scalable setup, package manager can be partially deployed in docker, with just the workers running on each CasparCG machine.
81
+
For setups where you need to interact with multiple CasparCG machines, or want a more resilient/scalable setup, package manager can be partially deployed in Docker, with just the workers running on each CasparCG machine.
82
82
83
-
An example docker-compose of the setup is as follows:
83
+
An example `docker-compose` of the setup is as follows:
84
84
85
85
```
86
86
services:
@@ -158,10 +158,10 @@ Note that each appContainer needs to use a different resourceId and will need it
1. If Package Manager `start:single-app` is running, restart it. If not, start it (see the above [Installation instructions](#installation-quick-start) for the relevant command line).
160
160
161
-
### Separate http proxy server
161
+
### Separate HTTP proxy server
162
162
163
-
In some setups, the url of the http proxy server is different when accessing the sofie ui and package manager.
164
-
You can use the 'Network ID' concept in package manager to provide guidance on which to use when.
163
+
In some setups, the URL of the HTTP proxy server is different when accessing the Sofie UI and Package Manager.
164
+
You can use the 'Network ID' concept in Package Manager to provide guidance on which to use when.
165
165
166
166
By adding `--networkIds=pm-net` (a semi colon separated list) when launching the exes on the CasparCG machine, the application will know to prefer certain accessors with matching values.
0 commit comments