Otherwise, it is considered relative to the baseDataDir.ĭefault: tempA temporary folder under baseDataDir into which files are written for internal use by Artifactory. If the value specified starts with a forward slash (“/”) the value is considered the fully qualified path to the filestore folder. To modify the template so that it stores binaries under $FILESTORE/binaries you could extend it as follows:ĭefault: $JFROG_HOME/artifactory/var/data/artifactoryThe root directory where Artifactory should store data files.ĭefault: filestoreThe root folder of binaries for the filestore. For example, the built-in filesystem chain template stores binaries under the $JFROG_HOME/artifactory/var/data/artifactory/filestore directory. To accommodate any specific requirements you may have for your filestore, you may modify one of the existing chain templates either by extending it with additional binary providers or by overriding one of its attributes. It is based on the sharding and dynamic provider logic that synchronizes the cluster-file-system. This is the setting used for Azure Blob Storage.
This is the setting used for Google Cloud Storage using the JetS3t library.
This is the setting used for S3 Object Storage using the JetS3t library. This is the setting used for Azure Blob Storage as the remote filestore.Ī pure sharding configuration that uses 2 physical mounts with 1 copy (which means each artifact is saved only once).Ī pure sharding configuration that uses 2 physical mounts with 2 copies (which means each shard stores a copy of each artifact).Ī filestore configuration where each node has its own local filestore (just like the file-system chain) and is connected to all other nodes via dynamically allocated Remote Binary Providers using the Sharding-Cluster provider. This is the setting used for Google Cloud Storage as the remote filestore. This is the setting used for S3 Object Storage using JCloud as the underlying framework. This is the setting used for S3 Object Storage using the JetS3t library. Improves performance of instances with high IOPS (I/O Operations) or slow NFS access.Īll the metadata and the binaries are stored as BLOBs in the database with an additional layer of caching.Īll the metadata and the binaries are stored as BLOBs in the database without caching.
Works the same way as filesystem but also caches download requests that are cleaned up using an LRU (Least Recently Used) protocol. The most basic filestore configuration for Artifactory used for a local or mounted filestore. The built-in set of chains available in Artifactory are: Artifactory comes with a built-in set of chains that correspond to the parameter that was used in previous versions of Artifactory.
These pre-defined sets of storage configurations are intended to create a common storage config.īinary providers can be embedded into one another to form chains that represent a coherent filestore. The binarystore.xml file can include a chain with a set of binary providers.
This page will describe how to use one or more of these providers. Review Best Practices For Managing Your Artifactory Filestore before you proceed to configure the filestore.Ī binary provider is a storage element that is based on checksum-based storage system.