Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fancyindex_css_href file path #84

Open
kli0rf opened this issue Apr 7, 2018 · 2 comments
Open

fancyindex_css_href file path #84

kli0rf opened this issue Apr 7, 2018 · 2 comments

Comments

@kli0rf
Copy link

kli0rf commented Apr 7, 2018

Extending this directive by adding capability to use custom css using the file path instead of url would be very useful.

@aperezdc
Copy link
Owner

aperezdc commented Jul 3, 2018

My understanding is that the contents of a local CSS file would be included inline inside the generated response, instead of generating a <link ...> element in the response. Is that what you mean? I would like to understand what do you need in order to know what to implement and how. If you can provide an example, that would be great. Thanks!

@kli0rf
Copy link
Author

kli0rf commented Sep 12, 2018

Sorry for such a late reply, i somehow missed your question... What i meant is, e.g.:
fancyindex_css_file "/var/www/example/fancyindex.css"; instead of fancyindex_css_href "https://example.tld/fancyindex.css";

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants