Redefine the location of 'static' folder in Pillar and extensions #54052

New Issue

Francesco Siddi · 2018-02-11T20:46:47+01:00

Francesco Siddi commented

2018-02-11 20:46:47 +01:00

Currently we automatically create pillar_static and <extension_name>_static values to be used in url_for() to serve static files. We expect to find a static directory inside the extension package.

Since this is stupid (according to the engineering team) we propose to move static to the root of the repo. This means changing the behavior of register_static_file_endpoint and move the static directory to the new location in all Pillar extensions.

Any comments @dr.sybren?

Currently we automatically create `pillar_static` and `<extension_name>_static` values to be used in `url_for()` to serve static files. We expect to find a `static` directory inside the extension package. Since this is *stupid* (according to the engineering team) we propose to move `static` to the root of the repo. This means changing the behavior of `register_static_file_endpoint` and move the `static` directory to the new location in all Pillar extensions. Any comments @dr.sybren?

Francesco Siddi self-assigned this 2018-02-11 20:46:47 +01:00

Francesco Siddi commented

2018-02-11 20:46:48 +01:00

Added subscribers: @dr.sybren, @fsiddi, @pablovazquez