Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Separate Storage Paths for Different Content Types #20

Open
toutouer opened this issue Jul 14, 2024 · 0 comments
Open

Comments

@toutouer
Copy link

Thank you for your excellent work on the GhoS3 adapter. Building upon your solid foundation, I have a feature request that could further enhance the adapter's flexibility.

Current Behavior
The current GhoS3 adapter uses a single pathPrefix for all types of content (images, media, and files).

Desired Behavior
It would be beneficial to have the ability to specify different storage paths for images, media, and files, similar to Ghost's local storage structure:

  • Images: content/images/
  • Media: content/media/
  • Files: content/files/

Motivation

  • Improved Organization: This structure would allow for better organization of uploaded content, making it easier to manage and locate specific types of files.
  • Consistency with Local Storage: Matching Ghost's local storage structure would provide consistency between local and S3 storage methods.
  • Easier Migration: Having a similar structure to local storage would simplify the process of migrating between storage adapters or backing up specific content types.
  • Flexibility: Users could have more control over how their content is organized in S3 buckets.

Proposed Implementation
Consider adding new configuration options to the S3 adapter:

"s3": {
  ...
  "pathPrefix": {
    "images": "content/images/",
    "media": "content/media/",
    "files": "content/files/"
  }
  ...
}

Thank you for considering this feature request and for your continued efforts to improve the Ghost ecosystem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant