| 1 |
[[!comment format=mdwn |
| 2 |
username="http://smcv.pseudorandom.co.uk/" |
| 3 |
nickname="smcv" |
| 4 |
subject="comment 4" |
| 5 |
date="2013-10-18T16:56:09Z" |
| 6 |
content=""" |
| 7 |
> \[[setup.txt]] - opens the plain text in the same browser window |
| 8 |
|
| 9 |
That's the browser's choice: the web server says \"this is text/plain\" |
| 10 |
and the browser decides to display it in the window. IkiWiki doesn't |
| 11 |
actually serve the file, just provides a link to it; to force it |
| 12 |
to be downloaded rather than opened, you'd have to configure |
| 13 |
your web server to offer it as \"Content-Disposition: attachment\" |
| 14 |
(e.g. <http://www.jtricks.com/bits/content_disposition.html>). |
| 15 |
|
| 16 |
The only way IkiWiki could get involved in this would be to |
| 17 |
have the file download go via the CGI script, which could |
| 18 |
add that header. That isn't currently a feature it has; |
| 19 |
you could maybe add a plugin if you need this? |
| 20 |
|
| 21 |
> \[[settings.xml]] - opens the formatted xml as html |
| 22 |
|
| 23 |
Again, this is between the web server and the browser. |
| 24 |
|
| 25 |
> \[[.gitignore]] - it does not recognise this file |
| 26 |
|
| 27 |
IkiWiki excludes files related to the source code control systems |
| 28 |
it uses, in order to avoid accidentally publishing a `.gitignore` |
| 29 |
that's intended to control ignored files for the git repo |
| 30 |
containing the pages' source. This is controlled by the |
| 31 |
`wiki_file_prune_regexps`, `exclude` and `include` config options. |
| 32 |
You can put `.gitignore` in `include` if you need to publish |
| 33 |
files with that name. |
| 34 |
"""]] |