Location of static_content and css directories

[xavierba]

Hi,

My understanding is the static_content name comes from the fact that it is statically served by the http server, while the remaining is served by cgi.
Most of what is installed in static_content directory is indeed data that does not change (fonts, javascripts) and thus can be installed readonly and owned by root user. This seems to fit well to $datadir$.
The only exception is the css subdirectory, which holds content dynamically generated by sympa and thus needs to be writeable by sympa user. As this is a subdirectory of static_content, this gets installed into $datadir$, but would seems to better fit into $localstatedir$.
I would suggest to split location of the css directory from the location of the static_content directory. The css directory could then be installed into $localstatedir$ while the static_content directory is installed into $datadir. This would probably mean the http conf needs to be tweaked to acknowledge for this change.

Does that make sense ?

Regards,
Xavier

[ikedas]

Hi Xavier,
I feel it making sense. Currently, default value of css_path parameter is derived from static_content_path parameter (it's STATICDIR by default). The former would have the default location of its own.

[xavierba]

There is likely a similar issue with the pictures directory, which is located within staticdir too (and is also not created, like the css dir that got fixed with 85a6217)

[ikedas]

Changes look done. I'll close this issue.

[ikedas]

Reopened to fix bug described in PR above.

[ikedas]

Seems fixed. Close.