Skip to content

Commit 3f71984

Browse files
committed
wip
1 parent a707964 commit 3f71984

File tree

14 files changed

+195
-202
lines changed

14 files changed

+195
-202
lines changed

packages/documentation/docs/user-guide/configuration/settings-view.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -167,7 +167,7 @@ Clicking on the action and filter pills allows you to edit the action parameters
167167

168168
##### Shift Registers
169169

170-
Shift Register modification actions are a special type of an Action, that modifies an internal state memory of the [Input Gateway](../installation/installing-input-gateway.md) and allows combination triggers, pagination, etc. on devices that don't natively support them or combining multiple devices into a single Control Surface. Refer to _Input Gateway_ documentation for more information on Shift Registers.
170+
Shift Register modification actions are a special type of an Action, that modifies an internal state memory of the [Input Gateway](../installation/installing-a-gateway/installing-input-gateway.md) and allows combination triggers, pagination, etc. on devices that don't natively support them or combining multiple devices into a single Control Surface. Refer to _Input Gateway_ documentation for more information on Shift Registers.
171171

172172
Shift Register actions have no effect in the browser, triggered from a _Hotkey_.
173173

packages/documentation/docs/user-guide/installation/initial-sofie-core-setup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
sidebar_position: 3
2+
sidebar_position: 35
33
---
44

55
# Initial Sofie Core Setup
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
11
{
22
"label": "Installing a Gateway",
3-
"position": 5
3+
"position": 50
44
}

packages/documentation/docs/user-guide/installation/installing-input-gateway.md renamed to packages/documentation/docs/user-guide/installation/installing-a-gateway/installing-input-gateway.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,7 @@
1+
---
2+
sidebar_position: 40
3+
---
4+
15
# Input Gateway
26

37
The Input Gateway handles control devices that are not capable of running a Web Browser. This allows Sofie to integrate directly with devices such as: Hardware Panels, GPI input, MIDI devices and external systems being able to send an HTTP Request.
@@ -31,14 +35,18 @@ Currently, input gateway supports:
3135

3236
### Shift Registers
3337

34-
Input Gateway supports the concept of _Shift Registers_. A Shift Register is an internal variable/state that can be modified using Actions, from within [Action Triggers](../configuration/settings-view.md#actions). This allows for things such as pagination, _Hold Shift + Another Button_ scenarios, and others on input devices that don't support these features natively. _Shift Registers_ are also global for all devices attached to a single Input Gateway. This allows combining multiple Input devices into a single Control Surface.
38+
Input Gateway supports the concept of _Shift Registers_. A Shift Register is an internal variable/state that can be modified using Actions, from within [Action Triggers](../../configuration/settings-view.md#actions). This allows for things such as pagination, _Hold Shift + Another Button_ scenarios, and others on input devices that don't support these features natively. _Shift Registers_ are also global for all devices attached to a single Input Gateway. This allows combining multiple Input devices into a single Control Surface.
3539

3640
When one of the _Shift Registers_ is set to a value other than `0` (their default state), all triggers sent from that Input Gateway become prefixed with a serialized state of the state registers, making the combination of a _Shift Registers_ state and a trigger unique.
3741

3842
If you would like to have the same trigger cause the same action in various Shift Register states, add multiple Triggers to the same Action, with different Shift Register combinations.
3943

4044
Input Gateway supports an unlimited number of Shift Registers, Shift Register numbering starts at 0.
4145

46+
### AdLib Tally
47+
48+
49+
4250
### Further Reading
4351

4452
- [Input Gateway Releases on GitHub](https://github.com/Sofie-Automation/sofie-input-gateway/releases)

packages/documentation/docs/user-guide/installation/installing-a-gateway/intro.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
sidebar_label: Introduction
3-
sidebar_position: 1
3+
sidebar_position: 10
44
---
55
# Introduction: Installing a Gateway
66

packages/documentation/docs/user-guide/installation/installing-a-gateway/playout-gateway.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
sidebar_position: 3
2+
sidebar_position: 30
33
---
44
# Playout Gateway
55

packages/documentation/docs/user-guide/installation/installing-blueprints.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
sidebar_position: 4
2+
sidebar_position: 40
33
---
44

55
# Installing Blueprints
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
11
{
22
"label": "Installing Connections and Additional Hardware",
3-
"position": 6
3+
"position": 60
44
}

packages/documentation/docs/user-guide/installation/installing-package-manager.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
sidebar_position: 7
2+
sidebar_position: 70
33
---
44

55
# Installing Package Manager
Lines changed: 2 additions & 169 deletions
Original file line numberDiff line numberDiff line change
@@ -1,172 +1,5 @@
11
---
2-
sidebar_position: 2
2+
sidebar_position: 30
33
---
44

5-
# Quick install
6-
7-
## Installing for testing \(or production\)
8-
9-
### **Prerequisites**
10-
11-
* **Linux**: Install [Docker](https://docs.docker.com/install/linux/docker-ce/ubuntu/) and [docker-compose](https://www.digitalocean.com/community/tutorials/how-to-install-docker-compose-on-ubuntu-18-04).
12-
* **Windows**: Install [Docker for Windows](https://hub.docker.com/editions/community/docker-ce-desktop-windows).
13-
14-
### Installation
15-
16-
This docker-compose file automates the basic setup of the [Sofie-Core application](../../for-developers/libraries.md#main-application), the backend database and different Gateway options.
17-
18-
```yaml
19-
# This is NOT recommended to be used for a production deployment.
20-
# It aims to quickly get an evaluation version of Sofie running and serve as a basis for how to set up a production deployment.
21-
services:
22-
db:
23-
hostname: mongo
24-
image: mongo:6.0
25-
restart: always
26-
entrypoint: ['/usr/bin/mongod', '--replSet', 'rs0', '--bind_ip_all']
27-
# the healthcheck avoids the need to initiate the replica set
28-
healthcheck:
29-
test: test $$(mongosh --quiet --eval "try {rs.initiate()} catch(e) {rs.status().ok}") -eq 1
30-
interval: 10s
31-
start_period: 30s
32-
ports:
33-
- '27017:27017'
34-
volumes:
35-
- db-data:/data/db
36-
networks:
37-
- sofie
38-
39-
# Fix Ownership Snapshots mount
40-
# Because docker volumes are owned by root by default
41-
# And our images follow best-practise and don't run as root
42-
change-vol-ownerships:
43-
image: node:22-alpine
44-
user: 'root'
45-
volumes:
46-
- sofie-store:/mnt/sofie-store
47-
entrypoint: ['sh', '-c', 'chown -R node:node /mnt/sofie-store']
48-
49-
core:
50-
hostname: core
51-
image: sofietv/tv-automation-server-core:release52
52-
restart: always
53-
ports:
54-
- '3000:3000' # Same port as meteor uses by default
55-
environment:
56-
PORT: '3000'
57-
MONGO_URL: 'mongodb://db:27017/meteor'
58-
MONGO_OPLOG_URL: 'mongodb://db:27017/local'
59-
ROOT_URL: 'http://localhost:3000'
60-
SOFIE_STORE_PATH: '/mnt/sofie-store'
61-
networks:
62-
- sofie
63-
volumes:
64-
- sofie-store:/mnt/sofie-store
65-
depends_on:
66-
change-vol-ownerships:
67-
condition: service_completed_successfully
68-
db:
69-
condition: service_healthy
70-
71-
playout-gateway:
72-
image: sofietv/tv-automation-playout-gateway:release52
73-
restart: always
74-
environment:
75-
DEVICE_ID: playoutGateway0
76-
CORE_HOST: core
77-
CORE_PORT: '3000'
78-
networks:
79-
- sofie
80-
- lan_access
81-
depends_on:
82-
- core
83-
84-
# Choose one of the following images, depending on which type of ingest gateway is wanted.
85-
86-
# spreadsheet-gateway:
87-
# image: superflytv/sofie-spreadsheet-gateway:latest
88-
# restart: always
89-
# environment:
90-
# DEVICE_ID: spreadsheetGateway0
91-
# CORE_HOST: core
92-
# CORE_PORT: '3000'
93-
# networks:
94-
# - sofie
95-
# depends_on:
96-
# - core
97-
98-
# mos-gateway:
99-
# image: sofietv/tv-automation-mos-gateway:release52
100-
# restart: always
101-
# ports:
102-
# - "10540:10540" # MOS Lower port
103-
# - "10541:10541" # MOS Upper port
104-
# # - "10542:10542" # MOS query port - not used
105-
# environment:
106-
# DEVICE_ID: mosGateway0
107-
# CORE_HOST: core
108-
# CORE_PORT: '3000'
109-
# networks:
110-
# - sofie
111-
# depends_on:
112-
# - core
113-
114-
# inews-gateway:
115-
# image: tv2media/inews-ftp-gateway:1.37.0-in-testing.20
116-
# restart: always
117-
# command: yarn start -host core -port 3000 -id inewsGateway0
118-
# networks:
119-
# - sofie
120-
# depends_on:
121-
# - core
122-
123-
# rundown-editor:
124-
# image: ghcr.io/superflytv/sofie-automation-rundown-editor:v2.2.4
125-
# restart: always
126-
# ports:
127-
# - '3010:3010'
128-
# environment:
129-
# PORT: '3010'
130-
# networks:
131-
# - sofie
132-
# depends_on:
133-
# - core
134-
135-
networks:
136-
sofie:
137-
lan_access:
138-
driver: bridge
139-
140-
volumes:
141-
db-data:
142-
sofie-store:
143-
```
144-
145-
Create a `Sofie` folder, copy the above content, and save it as `docker-compose.yaml` within the `Sofie` folder.
146-
147-
Visit [Rundowns & Newsroom Systems](installing-a-gateway/rundown-or-newsroom-system-connection/intro.md) to see which _Ingest Gateway_ can be used in your specific production environment. If you don't have an NRCS that you would like to integrate with, you can use the [Rundown Editor](rundown-editor) as a simple Rundown creation utility. Navigate to the _ingest-gateway_ section of `docker-compose.yaml` and select which type of _ingest-gateway_ you'd like installed by uncommenting it. Save your changes.
148-
149-
Open a terminal, execute `cd Sofie` and `sudo docker-compose up` \(or just `docker-compose up` on Windows\). This will download MongoDB and Sofie components' container images and start them up. The installation will be done when your terminal window will be filled with messages coming from `playout-gateway_1` and `core_1`.
150-
151-
Once the installation is done, Sofie should be running on [http://localhost:3000](http://localhost:3000). Next, you need to make sure that the Playout Gateway and Ingest Gateway are connected to the default Studio that has been automatically created. Open the Sofie User Interface with [Configuration Access level](../features/access-levels#browser-based) by opening [http://localhost:3000/?admin=1](http://localhost:3000/?admin=1) in your Web Browser and navigate to _Settings_ 🡒 _Studios_ 🡒 _Default Studio_ 🡒 _Peripheral Devices_. In the _Parent Devices_ section, create a new Device using the **+** button, rename the device to _Playout Gateway_ and select _Playout gateway_ from the _Peripheral Device_ drop down menu. Repeat this process for your _Ingest Gateway_ or _Sofie Rundown Editor_.
152-
153-
:::note
154-
Starting with Sofie version 1.52.0, `sofietv` container images will run as UID 1000.
155-
:::
156-
157-
### Tips for running in production
158-
159-
There are some things not covered in this guide needed to run _Sofie_ in a production environment:
160-
161-
- Logging: Collect, store and track error messages. [Kibana](https://www.elastic.co/kibana) and [logstash](https://www.elastic.co/logstash) is one way to do it.
162-
- NGINX: It is customary to put a load-balancer in front of _Sofie Core_.
163-
- Memory and CPU usage monitoring.
164-
165-
## Installing for Development
166-
167-
Installation instructions for installing Sofie-Core or the various gateways are available in the README file in their respective github repos.
168-
169-
Common prerequisites are [Node.js](https://nodejs.org/) and [Yarn](https://yarnpkg.com/).
170-
Links to the repos are listed at [Applications & Libraries](../../for-developers/libraries.md).
171-
172-
[_Sofie Core_ GitHub Page for Developers](https://github.com/Sofie-Automation/sofie-core)
5+
# Installing Sofie Core

0 commit comments

Comments
 (0)