You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a number of docker containers running with a volume bound to the public/assets directory, when using sspak load it tries to move the assets to assets-old but since the directory is a volume it fails.
I've had success by commenting out
Since raising this issue I 1. forgot I raised this issue and 2. changed our setup to not bind the assets to a docker volume. The point of the volume was to persist data between deployments but now our ci task will just create an sspak before taking down the old container and then use that to initialize the new container. As far as I'm concerned I no longer need this.
Additionally, I'm not sure that just optionally disabling this line is sufficient as just extracting the assets from the sspak would not remove any assets that are already there. (though in my case this was only used for fresh installs so it wouldn't matter anyway)
I have a number of docker containers running with a volume bound to the
public/assets
directory, when usingsspak load
it tries to move theassets
toassets-old
but since the directory is a volume it fails.I've had success by commenting out
sspak/src/Webroot.php
Line 159 in 1d1ffff
but it's a manual step I have to do every time as sspak is baked into the image and the containers are frequently rebuilt.
The text was updated successfully, but these errors were encountered: