…value is ‘${application.dir}shared‘ server.shared.path = ${application.dir}shared Path to a directory intended to hold (customized) technology models shared by all SPE users. Defaults to shared subdirectory of SPE application directory and exists only in SPE 3.41 or newer. For additional details about shared models directory, see Understanding SPE directory structure article. NOTE: If you change the server.shared.path, you might also want…
Search: share files between users
5 results
…hold (customized) technology models shared by all SPE users. Historically, customizations are registered for particular SPE user only (e.g. when registering LID language pack using phxadmin –add-language-pack). Putting the customized technology model in shared directory makes it available for all users. The shared directory should contain bsapi subdirectory with the same structure as the main directory in root of SPE…
…# The value specifies the maximum number of archived log files. If the number is exceeded, # archived log files are deleted, starting with the oldest. # server.logging.file.purge_count = 5 The following directive is important mainly for tuning and initiation of the SPE. Turn it on when the system is prepared to go live. # Use separate thread for logging….
…and ‘server.logging.file.purge_count’) Added support for FLAC and OPUS files – it is possible to upload and process these files, but requests which produce new files always produces WAV files Added request GET /admin/roles to list user roles Added VBS (Voice Biometry Server) plugin Added result of GET /server/info contains information about plugins 32-bit architecture (i386) is not supported anymore Updated…
…if different user accounts should have access to each other’s data, you might want to use some filesystem trickery like a symlink to some shared directory, like in the following example: ├── user_1/ │ ├── data/ │ └── storage/ │ └── audio -> /shared_recordings/ ├── user_2/ │ ├── data/ │ └── storage/ │ └── audio -> /shared_recordings/ └── administrator/ ├──…