@jkersu that does the dev/build but doesn’t do the flush bit.
@nightjarnz your latest method did something but gave many errors. Ill see if I can figure tehm out
Probably complaints about no base path info Hels - you can set that in the
.env also somehow
@jkersu that's basically what sake does - just does a bit of figuring out the setup first :)
its pages & pages of errors. but most of them seem to be about chmod() no permission
ah, flush tries to write
.htaccess files for
assets - it winds me up to no end.
I get around that by
sudo -u $WEB_USER vendor/bin/sake
on my dev setup WEB_USER is
http, but on may e.g. Debian (based) systems it's often
Long and short of it is @Hels - try to verify that your
.env file is even being read before getting too stressed about why it's not working :)
that .htaccess in public/assets I changed the owner to apache to allow flush to work normally. If I change the owner back to my login user will that allow the flush to work