file-system binary provider template configuration

If you choose to use the file-system template, configure the binarystore.xml configuration as follows.

<config version="v1">
        <chain template="file-system"/>
</config>

What's in the template?

While you don't need to configure anything else in your binarystore.xml, this is what the file-system template looks like under the hood.

<chain> <!-- template="file-system" -->
    <provider id="file-system" type="file-system"/>
</chain>

In this example, the filestore and temp folder are located under the root directory of the machine.

<config version="v1">
        <chain template="file-system"/>
        <provider id="file-system" type="file-system">
                <baseDataDir>/var/opt/jfrog/data</baseDataDir>
        <fileStoreDir>/filestore</fileStoreDir>   
                <tempDir>/temp</tempDir>
        </provider>
</config>

Where:

Parameter	Description
temp	file-system
baseDataDir	Default: `$JFROG_HOME/artifactory/var/data/artifactory` The root directory where Artifactory should store data files.
fileStoreDir	Default: `filestore` The root folder of binaries for the filestore. If the value specified starts with a forward slash (“/”) the value is considered the fully qualified path to the filestore folder. Otherwise, it is considered relative to the baseDataDir.
tempDir	Default: `temp` A temporary folder into which files are written for internal use by Artifactory. If the value specified starts with a forward slash ("/") the value is considered the full path to the temporary folder. Otherwise, it is considered relative to fileStoreDir under baseDataDir. 📘 Note Prior to Artifactory 7.98.2, tempDir was always relative to baseDataDir, and if tempDir had an absolute path in binarystore.xml (for example: /tmp), tempDir was set to $BASEDATADIR/filestore/tmp.