Closed sanderploegsma closed 2 years ago
@ludoch @eamonnmcmanus any ideas?
from @ludoch
I think this is Work as intended. The customer has to put files under the static dir, and then the mapping works this work: for a file under customer
static/foo
, it is served underproject.appspot.com/foo
Right, reading the documentation again it seems I mixed up the file path and the URL path. You're correct, the public-root
is used to denote the folder which contains the static files.
I was trying to do the inverse: prepend something to the URL path of static files, due to migrating an application and having to proxy specific paths from the old application. I therefore wanted to have my static files served under: example.com/some/path/style.css
, without having to create the /some/path
directory structure in my new application. From the looks of it, this isn't currently possible.
close as not planned
According to the appengine-web.xml documentation it should be possible to set a root path for static files like this:
Which should make
src/main/webapp/style.css
available underproject.appspot.com/static/style.css
.However, when I add the
public-root
setting, the resultingapp.yaml
does not have any directives for static files anymore, and thebuild/staged-app/__static__
folder is suddenly empty.Am I missing something?