Location Manager
manage permanent storage locations
Working with the Location Manager
To create a new location, click on the plus button in the lower left and enter the details (see below). By clicking on a location, you can see and edit the details. To remove a location, click on the desired location and on the minus button in the lower left.
Default storage locations
Click on the settings 
icon in the lower right to configure the default storage locations.
This configures in which locations new files will be stored. Locations marked as read-only cannot be used here.
Already existing files are still used in all locations, not only the default locations.
Details
ID
an unique number for each location
Status
fylr tests the connection to the storage location and displays the result here
Prefix
an optional path preceding each file, for example to separate from other data
Allow Purge
when purging this fylr instance, shall the files also be deleted?
Allow Redirect
whether to hide S3 URLs behind fylr's own URL
Read Only
Prevents changes made by fylr. Can not be set for locations that are currently configured as Default Storage Locations.
Type
Filesystem, S3 Bucket or Azure blob storage
Directory
A path - only for type Filesystem. Either an absolute path on the system visible to fylr (might be in a container); or a path relative to the fylr executable (e.g. in a container, it is relative to /fylr/bin/, which is not recommended, so use an absolute path).
Access Key
Credentials for type S3
Secret Key
Credentials for type S3
Bucket Name
Needed for type S3
Endpoint
URL for type S3
Region
For type S3, defined by your S3 provider
SSL
Whether to use https with S3
Account Name
Credentials for Azure Blob storage
Account Key
Credentials for Azure Blob storage
Endpoint Suffix
For Azure Blob storage
Connection String
For Azure Blob storage, this is an alternative to giving Account Name, Account Key and Endpoint Suffix separately. Do not give both.
Container
For Azure Blob storage
Last updated