Difference between revisions of "Configuration Files"
(Новая страница: «There are two configuration files: * main (acestream.conf) * user-defined (acestream_user.conf) Engine reads configuration files on startup. First the main file …») |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
* user-defined (acestream_user.conf) | * user-defined (acestream_user.conf) | ||
| − | Engine reads configuration files on startup. First the main file | + | Engine reads configuration files on startup. First engine loads the main file, then engine reads user-defined file if it exists. |
Options in user-defined file overwrite the same options in the main file. | Options in user-defined file overwrite the same options in the main file. | ||
| − | The reason to have two configuration files is because the auto-update system on Windows prevents main file from being modified. You can change the main file but | + | The reason to have two configuration files is because the auto-update system on Windows prevents main file from being modified. You can change the main file but it will be restored to the original state during the next auto-update. |
On Windows files are located here: | On Windows files are located here: | ||
| − | * main: %APPDATA%/ACEStream/engine/ | + | * main: %APPDATA%/ACEStream/engine/acestream.conf |
* user-defined: %APPDATA%/ACEStream/engine/acestream_user.conf | * user-defined: %APPDATA%/ACEStream/engine/acestream_user.conf | ||
| − | Engine does not check configuration files at runtime, | + | Alternatively, custom user configuration file can be loaded from elsewhere, by using "@" prefix to the file path in the command-line: |
| + | * load custom "ace.conf" file from some directory: ''acestreamengine --client-console @/home/user/ace.conf'' | ||
| + | Works for both Linux and Windows versions. | ||
| + | |||
| + | Engine does not check configuration files at runtime, they loading once during startup. So if you want to update configuration please follow these steps: | ||
* stop engine | * stop engine | ||
* update user-defined configuration file (create it if it doesn't exist) | * update user-defined configuration file (create it if it doesn't exist) | ||
* start engine | * start engine | ||
Latest revision as of 12:02, 27 April 2024
There are two configuration files:
- main (acestream.conf)
- user-defined (acestream_user.conf)
Engine reads configuration files on startup. First engine loads the main file, then engine reads user-defined file if it exists. Options in user-defined file overwrite the same options in the main file.
The reason to have two configuration files is because the auto-update system on Windows prevents main file from being modified. You can change the main file but it will be restored to the original state during the next auto-update.
On Windows files are located here:
- main: %APPDATA%/ACEStream/engine/acestream.conf
- user-defined: %APPDATA%/ACEStream/engine/acestream_user.conf
Alternatively, custom user configuration file can be loaded from elsewhere, by using "@" prefix to the file path in the command-line:
- load custom "ace.conf" file from some directory: acestreamengine --client-console @/home/user/ace.conf
Works for both Linux and Windows versions.
Engine does not check configuration files at runtime, they loading once during startup. So if you want to update configuration please follow these steps:
- stop engine
- update user-defined configuration file (create it if it doesn't exist)
- start engine
