Directory assets

[etj]

Allow Assets to handle full directory hierarchies.

Administration

• Add an Assets administration page
• Allow file Assets to be handled (create/update/delete) in the admin page
• Allow creation of Assets on directories

Logic

• Handle cloning of directory Assets

Access / download

• Allow access to every file inside the directory handled by an Asset, honouring the authorization on the Asset

URL handling

Let's say we have a LocalAsset (pk=10) with location /mnt/statics/assets/20240514etcetc/myindex.
We have in /mnt/statics/assets/20240514etcetc the files

• myindex
• file1
• otherdir/file2

The request http://server/api/v2/assets/10/link will return the content of the file myindex.
myindex will have info about the content in the directory, relative to itself, so it will contain as references "file1", "otherdir/file2".
The client will be able to perform calls to:

• http://server/api/v2/assets/10/link/file1
• http://server/api/v2/assets/10/link/otherdir/file2

and in general

• http://server/api/v2/assets/<PK>/link/<PATH>

Note that http://server/api/v2/assets/10/link/myindex will return the same content as http://server/api/v2/assets/10/link

[etj]

Blockers encountered:

• StorageManager renames the handled files, so the names referenced in an index files will no longer match
  • solved: a clone/copy procedure has been implemented within the LocalAssetHandler

Inconsistencies encountered:

• StorageManager uses os.path directly, without relying on the concrete manager to deal with the undelying filesystem