when you point to /img Laravel is running

@ifox so it won't work to simply point /img/... URLs to the CDN then?

it should, the /img route is not registered for a specific domain

Makes sense. But I'm thinking that the CDN is not equipped to distinguish between :

/img/.../thumbnail.jpg?fm=jpg&q=90&fit=max&crop=2000%2C1334%2C0%2C0&w=800
/img/.../thumbnail.jpg?fm=jpg&q=90&fit=max&crop=2000%2C1334%2C0%2C0&w=1800

What ends up on the CDN should be the result of the Glide transformation (resize in this case).

Right, how do I stop Laravel from redirecting me if the image already exists on cdn? I probably didn't understand your point there.

Would it be a bad thing to serve all images from

/uploads

folder instead of

/img

folder?

@User not at all. I believe that's what

A17\Twill\Services\MediaLibrary\Local

does. But I don't think it does image transformations.

So in order to keep the image transformation, I'm supposed to create another disk which would be public and would point to glide_cache folder?

That's how I'd avoid the redirect and keep everything as is?

Very interested in this use case, so I did a quick search and it seems like «The way Glide works is that all requests must be handled by PHP» and «It has no special features to work with CDNs». For reference: https://github.com/thephpleague/glide/issues/131#issuecomment-212516499 I think this use case would require at least a custom image service. But if your project is still at a phase where introducing Imgix is possible, it's definitely worth having a look. It does exactly what your custom image service would do in the end.

When I changed my environment from development to production, my content will not load anymore on my Twill CMS dashboard. Did I miss any steps?

Hi @User , do you have any errors in the browser's console?

@User interesting, did you run

php artisan twill:update

on your server after deploying?

I did. Unfortunately no success.. It just shows a blank page. That's all folks.

@User what version of Twill are you on?

"area17/twill": "^2.0",

Also, did you publish the Twill views in your project? (ie. php artisan vendor:publish ... )

that depends on the CDN configuration. On Cloudfront for example, you can enable cache keys varying on query strings

I cannot seem to find that full command in the documentation.

Hi. Please help me find the problem in the installation area17/twill-image (https://github.com/area17/twill-image) When i try to execute:

php artisan vendor:publish --provider="A17\Twill\Image\ImageServiceProvider" --tag=config

get a reply

No publishable resources for tag [config].
Publishing complete.

Well, the project itself is at least 2 years old, I just hopped in 3 months ago and I'm trying to get used to twill altogether, there's gigabytes of pictures already saved.

glide-cdn

i found the correct command .

php artisan vendor:publish --provider="Croustille\Image\ImageServiceProvider" --tag=config

the documentation says otherwise

@User it isn't tagged yet but the latest and greatest (for docs too) is in the

develop

branch

thanks

@User how to properly disable the default attributes /props ?

can i override blade templates somehow?

@User I think you can pass

['imgStyle' => [ ... ]]

in your image

$args