Directory structure for content #8

Open
opened 2024-11-15 04:08:36 +00:00 by PedoDeveloper · 1 comment

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:

autoshare/content/vicky
autoshare/content/vicky/archives
autoshare/content/vicky/video_previews
autoshare/content/vicky/image_previews
autoshare/content/vicky/data
autoshare/content/vicky/post_templates
autoshare/content/vicky/logs

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.

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: ``` autoshare/content/vicky autoshare/content/vicky/archives autoshare/content/vicky/video_previews autoshare/content/vicky/image_previews autoshare/content/vicky/data autoshare/content/vicky/post_templates autoshare/content/vicky/logs ``` 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.
Collaborator

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.

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.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
PedoDeveloper/autoshare#8
No description provided.