assets:generate-presets on every deploy?

[carstenjaksch]

I use Ploi with Zero Downtime Deployment. My images are stored in a shared and symlinked storage folder.

Is it necessary to call assets:generate-presets on every deployment? That takes a long time for 500+ files.

It seems that presets are being generated in the storage folder (which is shared) and I don't see any generated files in a public/img folder. So I assume I could ditch that command from my deploy script?

Ploi works a bit different with deployments. It first copies the current live folder including the Git repository and merges the newest commits from origin (instead of just cloning the whole thing every time). Since I do not track images in the repo, I think the command is useless for my use case.

Am I right?

[edalzell]

What if you add new images or change your presets? You'd have to run that manually then, right?

[carstenjaksch]

According to docs, the presets of newly uploaded images will be automatically generated. The settings thing is a good point however. Easy to forget that I think.

Well I can live with a longer build time. Shopware 6 needs much longer. 😄

[jasonvarga]

Can you make the glide directory a shared one too? Then it won't have to regenerate all the images every deployment.

[carstenjaksch]

I believe they are? I see them in storage/statamic/glide/containers/images. The folder public/img doesn't even exist. I assume it is "virtual"?