Directory structure for content #8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently the archives are stored in an archives directory, previews in a previews directory, and such. This was only a temporary solution, but I suggest a better solution in the long term.
First there will be a content directory, and inside this directory each content will have its own directory that contains the archives, previews, logs, etc. So the directory structure for a collection named 'Vicky' will be something like:
Obviously it makes more sense to have all the files from a particular collection in the same place, rather than having them scattered across multiple directories.
Yes, this is good. Let's make sure the content directory location can be configured, I wouldn't want to store potentially 100GB+ of data in the same directory as the executable.