You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed in #56, the storage.prefix config should be added to work with both storage types directory and s3, meaning that s3.prefix will be deprecated.
Concerns:
Will storage.directory.path config remain the same or should it be removed to make place to storage.prefix as well?
if so, which will the final storage path given the user configuration defines both?
{{ storage.prefix }} / {{ storage.directory.path }} or
As discussed in #56, the
storage.prefix
config should be added to work with both storage typesdirectory
ands3
, meaning thats3.prefix
will be deprecated.Concerns:
storage.directory.path
config remain the same or should it be removed to make place tostorage.prefix
as well?{{ storage.prefix }} / {{ storage.directory.path }}
or{{ storage.directory.path }} / {{ storage.prefix }}
The text was updated successfully, but these errors were encountered: