Generate these presets either on demand or with cron job
Choose disk and folder for each schema
Choose presets for each schema
Thumbnail Problem
Locally stored presets are accessible without hitting the php server. If the file doesn't exist then it does hit the server
to generate it.
But when using an s3 storage this is not possible!
I want to support the following features options:
- Store files locally
- Store files in s3 compatible
- Store files publicly available
- Store files locally available (secure)
- Create custom presets
- Generate these presets either on demand or with cron job
- Choose disk and folder for each schema
- Choose presets for each schema
# Thumbnail Problem
Locally stored presets are accessible without hitting the php server. If the file doesn't exist then it does hit the server
to generate it.
But when using an s3 storage this is not possible!
lexx
self-assigned this 2024-09-13 21:02:49 +00:00
Generate all new thumbnails when a new filter presents itself
I should also create a cleanup operation for deleted files or thumbnail presets
The current only possible solutions is to:
- Build all available thumbnails on upload
- Generate all new thumbnails when a new filter presents itself
I should also create a cleanup operation for deleted files or thumbnail presets
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I want to support the following features options:
Thumbnail Problem
Locally stored presets are accessible without hitting the php server. If the file doesn't exist then it does hit the server
to generate it.
But when using an s3 storage this is not possible!
The current only possible solutions is to:
I should also create a cleanup operation for deleted files or thumbnail presets
For command aliases:
https://tomgrohl.medium.com/how-to-add-aliases-to-your-laravel-console-commands-487eafd43f34
https://www.youtube.com/watch?v=yj_G9pJtUhU