Versions Compared
Version | Old Version 2 | New Version Current |
---|---|---|
Changes made by | ||
Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Refer to the Enabling HTTPS on your Zixi Broadcaster guide.
Changing the default root folder location
The root folder is used to store recordings and VOD content. Over time the size of the content in this folder may grow significantly. If this folder is in the same partition as the machine’s operating system and the capacity limit is reached, it may cause risks to the machine itself. It is therefore recommended to change Zixi’s root folder location to a separate partition (not the same partition as the OS). If the partition is filled it will not disrupt or harm the machine’s OS.
To change the default root folder location:
Open the ‘broadcaster-info.xml’ file, which is located in the folder as the Zixi’s executable file (e.g. zixi_broadcaster-1.10.1.24727.exe).
The file includes the following content:
Code Block |
---|
<?xml version="1.0" encoding="utf-8"?>
<ROOT_SETTINGS>
<FOLDER>d:\ts</FOLDER>
<MANAGED>false</MANAGED>
<MANAGEMENT-ENABLED>false</MANAGEMENT-ENABLED>
</ROOT_SETTINGS>
<TUNNEL>
<ALLOW>0</ALLOW>
<MASTER>1</MASTER>
</TUNNEL> |
Defining “non-root user”
Zixi includes some settings that modify the operating system settings on the host machine (e.g. networking settings, etc.). Modifying these settings requires Zixi Broadcaster to have “Root user” (the highest) access privileges on the machine. However, once these settings have been defined, Zixi Broadcaster does not need these high level access privileges anymore and it is recommended to change the access privileges to a non-root user.
The following settings cannot be modified after changing the access privileges. Make sure you do not need to modify any of these settings:
- Settings > Network.
- Settings > SSH Connections
- Settings > ASI
To define non-root user privileges:
Zixi enables secure encrypted communication using HTTPS among the Zixi resources (Feeder, Broadcaster and Receiver) as well as between the resources and oter end-points. In order to enable HTTPS communications, you first need to generate an SSL certificate and Private Key for your secure connections.
Panel | |
---|---|
On this page:
|