Publishing Methods
Publishing can be done in different ways:
- Direct Connection (Default): Communication occurs directly over the local IP network. For this, it must be ensured that the PCs running the FrontFace Assistant and the FrontFace Player App are on the same network. If necessary, the required ports (default: 4545 and 4646) must also be opened in the firewall.
- All-in-One: The FrontFace Assistant and the FrontFace Player App are installed on the same PC. To make and publish changes, the Player App must be closed and the FrontFace Assistant opened. This publishing method can only be used in conjunction with the Windows version of the FrontFace Player App and is intended for offline or highly isolated scenarios.
- Folder: A directory or an SMB network share is used to enable publishing from the FrontFace Assistant to the FrontFace Player App. The same publishing directory is then specified at both ends. With this publishing method, data can also be transferred via alternative, custom transport methods, e.g., via a cloud storage service (Dropbox, OneDrive, etc.) or via FTP/SCP.
- FrontFace Cloud: When publishing via FrontFace Cloud, the FrontFace Assistant and FrontFace Player App only require internet access. The data is then transferred via the FrontFace Cloud and mirabyte’s servers. A FrontFace Cloud license is required to use this publishing method.
Additionally, for larger installations with many players, there is an option for a distributed installation: In this process, an additional FrontFace Server is used to supply the FrontFace Player app(s) with content and receive published content from the FrontFace Assistant. With this installation type, in addition to the above-mentioned operating systems, the FrontFace Player App can also be operated as a WASM (Web Assembly) app and thus run in standard browsers. The FrontFace Player Apps then can only display content with an active network connection to the FrontFace Server.