By the way, I added Turkish language support to Twill.

@afatmustafa unfortunately the image field is not compatible with the modal yet

that's great!

Thanks ifox, okey then I'll go the old way.

Is there a way to limit a Twill's project media library, so a malicious person can not rack up my AWS bill 😉

Or would the best way to go about that is to use the AWS budgeting tools?

@Klief a malicious person with access to the CMS?

Indeed, say a hacker got access to the CMS.

that would be unfortunate. Twill went through multiple external security audits over the years so you should be realtively safe but you're of course still subject to your users having poor passwords or them sharing their credentials. I'd recommend enabling Twill users 2FA. There are no ways to set limits on the Twill/Laravel side that I can think of right now outside of limiting the max filesize of each uploaded files. I'd recommend setting up CloudWatch alerts on "BucketSizeBytes" if you'd like to be alerted by AWS.

Hey there! I was wondering how do I setup my images in order for them to be served from CDN?

Hey @User, are you considering a specific service (e.g. Amazon S3) or looking for suggestions?

I'm looking for a way to serve stuff directly from CDN instead of it being served locally, because when I 'render' stuff via twill it gets rendered as

mydomain.com/img/hash/name.jpg

by default. How do I serve it as

cdn-mydomain.com/img/hash/name.jpg

instead? Is there a way for me to tell twill to change the default path before showing the image?

@User that's what Imgix is all about. If you're looking to handle that yourself, a custom flysystem disk configuration, or a custom image service class should help you with that

@User out of curiosity, what are you currently using as

MEDIA_LIBRARY_IMAGE_SERVICE

?

most likely glide (I see

img

in the path shared)

@User

A17\\Twill\\Services\\MediaLibrary\\Glide

twill.glide.base_url

might work

Nice, so I guess ideally you would want to keep Glide for image transformation but serve the cached/transformed images from the CDN?

Yes

That's it? I just set it up in my .env?

yeah, by default its using your app url

if you do this any image url generated by twill should use your CDN domain

I'm having second thoughts... I believe this won't take into consideration the link between the Glide URL and the Glide cached image, or am I missing something obvious?

I was wondering, why does twill generate the default

/img/

instead of

/uploads/

part of the path? Even though the local path is set to

/uploads/

in the config of media-library.php, the

MEDIA_LIBRARY_LOCAL_PATH

?

because /img points to a controller where Glide is running the transformations

Furthermore when I try to get images from cdn while using

/img

I get redirected back to

mydomain.com/img/~

instead of leaving it as

cdn-mydomain.com/img/~

While when using the

/uploads/

instead of

/img/

the images get served from cdn

that's Laravel redirecting you

when you point to uploads your get a static file from public folder