https://twill.io logo
Powered by
# ❓questions
  • p
    I wonder if https://github.com/calebporzio/sushi can be useful here. A JSON repeater value is pretty much an array... that we would like to treat as an eloquent collection.
  • p
    Maybe not, haha. It's a fun problem in any case!
  • c
    thanks @User it would be great to have a working exemple ! i'm facing some issues trying to make it work too :/
  • p
    json-repeater-values
  • c
    hi everyone ! thanks to @User i've finaly make Glide and S3 works together. Anyway, I'm still facing a problem, the rendering time of all my images is pretty slow. After uploading a file, croping a file, rendering the image in front end, everything is a bit slow. The url called is 
    /img/{path}
    that is using the GlideController. I'm ok with the fact that the first print of a new generated image can be a bit long. But once the image is generated, it should be render quicker right ? So if anyone here has the same problem or even a solution to this latence issue i will realy appreciate 🙂 have a good day
  • i
    hi @Charton once rendered it is supposed to serve the rendered file immediately so there should be no latency unless you're doing crazy stuff in your Laravel app booting process
  • i
    what else than this did you have to do to make it work? Are you sure it is serving rendered image from its cache?
  • i
    i feel like you're most likely still seeing non rendered images and downloading the original every time
  • c
    hm, in my glide config i've set this :
  • c
    Copy code
    'glide' => [
        'source' => app(A17\Twill\Services\Cloud\Glide::class)->makeCloudSource('s3'),
        'cache' => app(A17\Twill\Services\Cloud\Glide::class)->makeCloudSource('s3'),
        'cache_path_prefix' => env('GLIDE_CACHE_PATH_PREFIX', 'glide_cache'),
        'base_url' => env('GLIDE_BASE_URL', ''),
        'base_path' => env('GLIDE_BASE_PATH', 'img'),
        'use_signed_urls' => env('GLIDE_USE_SIGNED_URLS', false),
        'sign_key' => env('GLIDE_SIGN_KEY'),
        'driver' => env('GLIDE_DRIVER', 'gd'),
        'add_params_to_svgs' => false,
        'default_params' => [
            'fm' => 'jpg',
            'q' => '80',
            'fit' => 'max',
        ],
        'lqip_default_params' => [
            'fm' => 'gif',
            'blur' => 100,
            'dpr' => 1,
        ],
        'social_default_params' => [
            'fm' => 'jpg',
            'w' => 900,
            'h' => 470,
            'fit' => 'crop',
        ],
        'cms_default_params' => [
            'q' => '60',
            'dpr' => '1',
        ],
        'presets' => [],
        'original_media_for_extensions' => [],
    ],
  • c
    and with this config, when i want to make a new crop for exemple; i will face during few seconds a blank image
  • c
    until the image finaly loads
  • c
    and this showing time will appear everytime the image is supposed to be displayed (in mdeia library, in preview, in frontend)
  • i
    It's definitely not rendering images correctly
  • i
    in the media library it's supposed to render 256px images which are obviously very fast to load
  • i
    first thing, and that's true for all Twill config, you do not need to override the whole thing, only what matters to you, everything will be merged by Twill with its default
  • i
    are you seeing a 
    glide_cache
    folder in your S3 bucket @Charton ?
  • c
    yes the glide_cache folder is present
  • c
    and i can also retrieve my cropped files in it
  • i
    does the /img route correctly return those?
  • i
    if it does, it might still be that it's actually not using the cache even though it is writing to it
  • c
    let me check
  • a
    /img returns the correct and manipulated image, and the manipulated image only render once. It does not occur over and over again.
  • a
    I checked again, it shows the manipulated image, but it works like it's re-rendering every time i guess.
  • c
    yes i can confirm this behavior
  • h
    could it be that autoloaded helpers (from a capsule) do not function when optimized?
  • i
    hmm, that's quite possible
  • i
  • i
    @Harings Rob do you mean composer's --optimize-autoloader flag?
  • h
    no php artisan optimize
1...168169170...484Latest