However, if "Deploynaut" no longer uses Capistrino, then this is a little moot 😕
It was my understanding that while
git clone and
composer install are of course run somewhere, that Capistrano kicked-in and transferred those files from some intermediary "build server" to the host server. If that was the case, then by whichever means Capsitrano physcially performs the transport (e.g. rsync), it can leverage
.gitattributes files (See here: https://capistranorb.com/documentation/advanced-features/ignoring/).
AFAIK, CWP is still using "Deploynaut" which back in the day was using Capistrano. If tht's still true, there shouldn't be any reason it couldn't reflect exclusions from
Thanks - and yes, the obvious thing to do would be to remove them from release, but there are always reasons. Capistrano and Fabricdeploy and deployer (and rsync) all ignore files from .gitattributes with
No hits via http://cwp.govt.nz's search feature
Does anyone know if
.gitattributes is supported on CWP?
Just a shot in the dark, seeing as users of other browsers don't see the same thing...
Weird - is your site hosted on >1 webserver by any chance?
@dorsetdigital +1 for use of the word "badger".