This article describes the settings used in server.config for publishing engine.
Server.config settings
Publisher (in Manager) has a few settings located in server.config located in C:\ProgramData\Signifikant\Assert\.
<PublisherSettings>
<!-- Spool area will be cleaned out at each publish. Spool area contains image cache for converted images.
Old log files are not cleaned out due tho this setting. -->
<SpoolImageCleanup>true</SpoolImageCleanup>
<!-- Language fallback when a text translation is looked for, in Pdf publications, where translations are missing -->
<DefaultDataLanguages>sv; en; en-GB</DefaultDataLanguages>
<!--- If upload of files to remote server fails, the publisher will retry a number of times according to this setting. -->
<RemoteUploadTryCount>5</RemoteUploadTryCount>
<!-- Small files are sent through a stream. This is a limit in bytes where larger files are sends in chunks instead. Zero is default: stream upload. -->
<RemoteUploadChunkLimit>0</RemoteUploadChunkLimit>
<!-- From version 5 old log files for publish will be saved in the spool area for the publication. Files are saved
a number of days according to this setting. Default is 60 days. -->
<DaysToSavePublisherLog>60</DaysToSavePublisherLog>
<!-- Version 5 and later: enable the login flag to make Server use Basic authentication when connecting to a remote web server by REST calls -->
<!-- Username and password is matched in the servers api-permission.config file to compute what roles are available to the login -->
<UploadUsername>guest</UploadUsername>
<UploadPassword>guest</UploadPassword>
<UploadLogin>true</UploadLogin>
</PublisherSettings>
Permissions for APIs for publish is by default turned on, see Technical documentation - Signifikant REST API authentication
Also see whitelisting of publisher APIs, see