thanks for the :rubber-duck: @Firesphere
but the whole 4.2.1 -> 4.4 tmp dir perms issue blew away the exisitng cache and flush worked
it was working..
incase im fushing wrong its just
./path/to/sake dev/build flush=1 correct?
yeah thought it was more of a "contact the service" 😄 thanks anyway
its also a shared app server using server pilot so ssh login is via the app user then i think its a general www-data user for the web entry level
which makes sense as its trying to stop exploits on the unix level? i suppose
so i gave this a crack but due to how we handle deployments we ssh and run a string script to handle the devbuild. if i try to su -u i get
su: must be run from a terminal