Skip to content
This repository
Newer
Older
100644 512 lines (376 sloc) 18.524 kb
45a9c7fb »
2008-11-07 Reformatted README using standard markdown.
1 Gitit
2 =====
89725fd9 »
2008-11-06 Initial commit.
3
f8ab67e6 »
2009-04-27 Reformatting (line lengths) of README.
4 Gitit is a wiki program written in Haskell. It uses [Happstack][]
5 for the web server and [pandoc][] for markup processing. Pages and
6 uploaded files are stored in a [git][] or [darcs][] repository and may
7 be modified either by using the VCS's command-line tools or through the
8 wiki's web interface. By default, pandoc's extended version of markdown
0f4f9c6e »
2009-06-05 Indicate in README that LaTeX or HTML formats can be used.
9 is used as a markup language, but reStructuredText, LaTeX, or HTML
10 can also be used. Pages can be exported in a number of different
11 formats, including LaTeX, RTF, OpenOffice ODT, and MediaWiki markup.
ff6f3b95 »
2009-08-23 Updated math part of README.
12 Gitit can be configured to display TeX math (using [texmath][]) and
0f4f9c6e »
2009-06-05 Indicate in README that LaTeX or HTML formats can be used.
13 highlighted source code (using [highlighting-kate][]).
89725fd9 »
2008-11-06 Initial commit.
14
f22d5c4a »
2009-08-14 Changed default config to use-cache: no.
15 [git]: http://git.or.cz
d9c8cd8b »
2009-01-24 Modified description slightly, mentioning darcs as well as git.
16 [darcs]: http://darcs.net
89725fd9 »
2008-11-06 Initial commit.
17 [pandoc]: http://johnmacfarlane.net/pandoc
fd9eed57 »
2009-03-10 Changed mentions of HAppS to Happstack.
18 [Happstack]: http://happstack.com
f22d5c4a »
2009-08-14 Changed default config to use-cache: no.
19 [highlighting-kate]: http://johnmacfarlane.net/highlighting-kate/
ff6f3b95 »
2009-08-23 Updated math part of README.
20 [texmath]: http://github.com/jgm/texmath/tree/master
89725fd9 »
2008-11-06 Initial commit.
21
45a9c7fb »
2008-11-07 Reformatted README using standard markdown.
22 Getting started
23 ===============
89725fd9 »
2008-11-06 Initial commit.
24
45a9c7fb »
2008-11-07 Reformatted README using standard markdown.
25 Compiling and installing gitit
26 ------------------------------
89725fd9 »
2008-11-06 Initial commit.
27
45a9c7fb »
2008-11-07 Reformatted README using standard markdown.
28 You'll need the [GHC][] compiler and the [cabal-install][] tool. GHC can
98adca8b »
2009-01-28 Note the GHC 6.10 requirement in README.
29 be downloaded [here][]. Note that, starting with release 0.5, GHC 6.10
30 or higher is required. For [cabal-install][] on *nix, follow the [quick
45a9c7fb »
2008-11-07 Reformatted README using standard markdown.
31 install][] instructions.
89725fd9 »
2008-11-06 Initial commit.
32
33 [GHC]: http://www.haskell.org/ghc/
34 [here]: http://www.haskell.org/ghc/
35 [cabal-install]: http://hackage.haskell.org/trac/hackage/wiki/CabalInstall
36 [quick install]: http://hackage.haskell.org/trac/hackage/wiki/CabalInstall#Quick Installation on Unix
37
97e00433 » John MacFarlane
2009-04-18 Improved README.
38 Once you've got cabal-install, installing gitit is trivial:
89725fd9 »
2008-11-06 Initial commit.
39
a7c11fe8 »
2008-11-30 Simplified installation instructions.
40 cabal update
89725fd9 »
2008-11-06 Initial commit.
41 cabal install gitit
42
a7c11fe8 »
2008-11-30 Simplified installation instructions.
43 These commands will install the latest released version of gitit.
89725fd9 »
2008-11-06 Initial commit.
44 To install a version of gitit checked out from the repository,
45 change to the gitit directory and type:
46
47 cabal install
48
49 The `cabal` tool will automatically install all of the required haskell
50 libraries. If all goes well, by the end of this process, the latest
51 release of gitit will be installed in your local `.cabal` directory. You
52 can check this by trying:
53
54 gitit --version
55
56 If that doesn't work, check to see that `gitit` is in your local
57 cabal-install executable directory (usually `~/.cabal/bin`). And make
58 sure `~/.cabal/bin` is in your system path.
59
97e00433 » John MacFarlane
2009-04-18 Improved README.
60 Optional syntax highlighting support
61 ------------------------------------
62
63 If pandoc was compiled with optional syntax highlighting support,
64 this will be available in gitit too. This feature is recommended
65 if you plan to display source code on your wiki.
66
67 Highlighting support requires the [pcre][] library, so make sure that
68 is installed before continuing.
69
70 [pcre]: http://www.pcre.org/
71
72 To install gitit with highlighting support, first ensure that pandoc
73 is compiled with highlighting support, then install gitit as above:
74
75 cabal install pandoc -fhighlighting --reinstall
76 cabal install gitit
77
45a9c7fb »
2008-11-07 Reformatted README using standard markdown.
78 Running gitit
79 -------------
89725fd9 »
2008-11-06 Initial commit.
80
97e00433 » John MacFarlane
2009-04-18 Improved README.
81 To run gitit, you'll need [git][] in your system path. (Or
82 [darcs][], if you're using darcs to store the wiki data.)
89725fd9 »
2008-11-06 Initial commit.
83
97e00433 » John MacFarlane
2009-04-18 Improved README.
84 Gitit assumes that the page files (stored in the git repository) are
85 encoded as UTF-8. Even page names may be UTF-8 if the file system
86 supports this. So you should make sure that you are using a UTF-8 locale
87 when running gitit. (To check this, type `locale`.)
73db5a1f »
2009-01-28 Noted need for UTF-8 locale in README.
88
f8ab67e6 »
2009-04-27 Reformatting (line lengths) of README.
89 Switch to the directory where you want to run gitit. This should be a
f1f023a5 »
2009-07-09 Use nested templates in templates/ directory rather than template.html.
90 directory where you have write access, since three directories, `static`,
91 `templates`, and `wikidata`, and two files, `gitit-users` and `gitit.log`,
92 will be created here. To start gitit, just type:
89725fd9 »
2008-11-06 Initial commit.
93
94 gitit
95
96 If all goes well, gitit will do the following:
97
98 1. Create a git repository, `wikidata`, and add a default front page.
d77f5663 »
2009-08-22 Updated README.markdown for changes to static and templates.
99 2. Create a `static` directory containing files to be treated as
100 static files by gitit.
f1f023a5 »
2009-07-09 Use nested templates in templates/ directory rather than template.html.
101 3. Create a `templates` directory containing HStringTemplate templates
f498fc6d »
2008-11-26 Use HStringTemplate template for pages.
102 for wiki pages.
103 4. Start a web server on port 5001.
89725fd9 »
2008-11-06 Initial commit.
104
f8ab67e6 »
2009-04-27 Reformatting (line lengths) of README.
105 Check that it worked: open a web browser and go to
106 <http://localhost:5001>.
97e00433 » John MacFarlane
2009-04-18 Improved README.
107
7fa73832 »
2009-06-28 Updated README with information about metadata block.
108 Using gitit
109 ===========
110
97e00433 » John MacFarlane
2009-04-18 Improved README.
111 Wiki links and formatting
112 -------------------------
113
114 For instructions on editing pages and creating links, see the "Help" page.
115
f8ab67e6 »
2009-04-27 Reformatting (line lengths) of README.
116 Gitit interprets links with empty URLs as wikilinks. Thus, in markdown
117 pages, `[Front Page]()` creates an internal wikilink to the page `Front
118 Page`. In reStructuredText pages, `` `Front Page <>`_ `` has the same
119 effect.
89725fd9 »
2008-11-06 Initial commit.
120
c332b942 »
2009-05-10 Documentation changes for new index link format.
121 If you want to link to a directory listing for a subdirectory, use a
122 trailing slash: `[foo/bar/]()` creates a link to the directory for
123 `foo/bar`.
124
7fa73832 »
2009-06-28 Updated README with information about metadata block.
125 Page metadata
126 -------------
127
128 Pages may optionally begin with a metadata block. Here is an example:
129
38209d92 »
2009-07-03 Updated README with new metadata format.
130 ---
131 format: latex+lhs
132 categories: haskell math
133 toc: no
134 title: Haskell and
7fa73832 »
2009-06-28 Updated README with information about metadata block.
135 Category Theory
38209d92 »
2009-07-03 Updated README with new metadata format.
136 ...
7fa73832 »
2009-06-28 Updated README with information about metadata block.
137
138 \section{Why Category Theory?}
139
d89590a6 »
2009-08-17 Don't require blank line after metadata block.
140 The metadata block consists of a list of key-value pairs, each on a
141 separate line. If needed, the value can be continued on one or more
142 additional line, which must begin with a space. (This is illustrated by
143 the "title" example above.) The metadata block must begin with a line
144 `---` and end with a line `...` optionally followed by one or more blank
145 lines. (The metadata block is a valid YAML document, though not all YAML
146 documents will be valid metadata blocks.)
7fa73832 »
2009-06-28 Updated README with information about metadata block.
147
148 Currently the following keys are supported:
149
150 format
151 : Overrides the default page type as specified in the configuration file.
152 Possible values are `markdown`, `rst`, `latex`, `html`, `markdown+lhs`,
153 `rst+lhs`, `latex+lhs`. (Capitalization is ignored, so you can also
154 use `LaTeX`, `HTML`, etc.) The `+lhs` variants indicate that the page
155 is to be interpreted as literate Haskell. If this field is missing,
156 the default page type will be used.
157
158 categories
159 : A space or comma separated list of categories to which the page belongs.
160
161 toc
162 : Overrides default setting for table-of-contents in the configuration file.
163 Values can be `yes`, `no`, `true`, or `false` (capitalization is ignored).
164
165 title
166 : By default the displayed page title is the page name. This metadata element
167 overrides that default.
168
e9ac5c2b »
2009-08-15 Make plugins flag enabled by default.
169 Highlighted source code
170 -----------------------
171
172 If gitit was compiled against a version of pandoc that has highlighting
173 support (see above), you can get highlighted source code by using
174 [delimited code blocks][]:
175
176 ~~~ {.haskell .numberLines}
177 qsort [] = []
178 qsort (x:xs) = qsort (filter (< x) xs) ++ [x] ++
179 qsort (filter (>= x) xs)
180 ~~~
181
182 To see what languages are available:
183
184 pandoc -v
185
186 [delimited code blocks]: http://johnmacfarlane.net/pandoc/README.html#delimited-code-blocks
187
d77f5663 »
2009-08-22 Updated README.markdown for changes to static and templates.
188 Configuring and customizing gitit
189 =================================
488e6bbc » John MacFarlane
2009-04-18 README: Added instructions for proxying with apache.
190
45a9c7fb »
2008-11-07 Reformatted README using standard markdown.
191 Configuration options
192 ---------------------
89725fd9 »
2008-11-06 Initial commit.
193
194 You can set some configuration options when starting gitit, using the
ce07825b »
2009-04-12 Added data/default.conf, which defines default config file values.
195 option `-f [filename]`. To get a copy of the default configuration file,
196 which you can customize, just type:
197
198 gitit --print-default-config > default.conf
199
200 The default configuration file is documented with comments throughout.
2859d1b4 »
2009-02-10 Document --print-default-config.
201
45a9c7fb »
2008-11-07 Reformatted README using standard markdown.
202 The `static` directory
203 ----------------------
89725fd9 »
2008-11-06 Initial commit.
204
d77f5663 »
2009-08-22 Updated README.markdown for changes to static and templates.
205 On receiving a request, gitit always looks first in the `static`
206 directory (or in whatever directory is specified for `static-dir` in
207 the configuration file). If a file corresponding to the request is
208 found there, it is served immediately. If the file is not found in
209 `static`, gitit next looks in the `static` subdirectory of gitit's data
210 file (`$CABALDIR/share/gitit-x.y.z/data`). This is where default css,
211 images, and javascripts are stored. If the file is not found there
212 either, gitit treats the request as a request for a wiki page or wiki
213 command.
214
215 So, you can throw anything you want to be served statically (for
216 example, a `robots.txt` file or `favicon.ico`) in the `static`
217 directory. You can override any of gitit's default css, javascript, or
218 image files by putting a file with the same relative path in `static`.
2473f078 »
2009-08-22 Added robots.txt to static.
219 Note that gitit has a default `robots.txt` file that excludes all
220 URLs beginning with `/_`.
89725fd9 »
2008-11-06 Initial commit.
221
77d20a35 »
2009-04-27 README changes: running with darcs, updated some refs to config options.
222 Note: if you set `static-dir` to be a subdirectory of `repository-path`,
89e0a04b »
2009-01-16 Added note about possibility of putting static inside repository.
223 and then add the files in the static directory to your repository, you
224 can ensure that others who clone your wiki repository get these files
225 as well. It will not be possible to modify these files using the web
226 interface, but they will be modifiable via git.
227
77d20a35 »
2009-04-27 README changes: running with darcs, updated some refs to config options.
228 Using darcs instead of git
229 --------------------------
230
231 By default, gitit will store wiki pages in a git repository in the
232 `wikidata` directory. If you'd prefer to use darcs instead of git,
233 you need to add the following field to the configuration file:
234
235 repository-type: Darcs
236
237 This program may be called "darcsit" instead of "gitit" when a darcs
238 backend is used.
239
99d1199f »
2009-08-15 Added comments on filestore/maxcount to darcs sec of README.
240 Note: we recommend that you use gitit/darcsit with darcs version
241 2.3.0 or greater. If you must use an older version of darcs, then
242 you need to compile the filestore library without the (default)
243 maxcount flag, before (re)installing gitit:
244
245 cabal install --reinstall filestore -f-maxcount
246 cabal install --reinstall gitit
247
248 Otherwise you will get an error when you attempt to access your
249 repository.
250
45a9c7fb »
2008-11-07 Reformatted README using standard markdown.
251 Changing the theme
252 ------------------
89725fd9 »
2008-11-06 Initial commit.
253
d77f5663 »
2009-08-22 Updated README.markdown for changes to static and templates.
254 To change the look of the wiki, you can modify `custom.css` in
255 `static/css`.
97e00433 » John MacFarlane
2009-04-18 Improved README.
256
d77f5663 »
2009-08-22 Updated README.markdown for changes to static and templates.
257 To change the look of printed pages, copy gitit's default `print.css`
258 to `static/css` and modify it.
97e00433 » John MacFarlane
2009-04-18 Improved README.
259
f498fc6d »
2008-11-26 Use HStringTemplate template for pages.
260 The logo picture can be changed by copying a new PNG file to
97e00433 » John MacFarlane
2009-04-18 Improved README.
261 `static/img/logo.png`.
262
d77f5663 »
2009-08-22 Updated README.markdown for changes to static and templates.
263 To change the footer, modify `templates/footer.st`.
264
265 For more radical changes, you can override any of the default
266 templates in `$CABALDIR/share/gitit-x.y.z/templates` by copying
267 the file into `templates` and modifying it. The `page.st` template is
268 the master template; it includes the others. Interpolated variables are
269 surrounded by `$`s, so `literal $` must be backslash-escaped.
89725fd9 »
2008-11-06 Initial commit.
270
45a9c7fb »
2008-11-07 Reformatted README using standard markdown.
271 Adding support for math
272 -----------------------
89725fd9 »
2008-11-06 Initial commit.
273
7fa73832 »
2009-06-28 Updated README with information about metadata block.
274 To write math on a markdown-formatted wiki page, just enclose it
275 in dollar signs, as in LaTeX:
89725fd9 »
2008-11-06 Initial commit.
276
277 Here is a formula: $\frac{1}{\sqrt{c^2}}$
278
279 You can write display math by enclosing it in double dollar signs:
280
281 $$\frac{1}{\sqrt{c^2}}$$
282
ff6f3b95 »
2009-08-23 Updated math part of README.
283 Gitit can display TeX math in three different ways, depending on the
284 setting of `math` in the configuration file:
285
286 1. `mathml` (default): Math will be converted to MathML using
287 [texmath][]. This method works with IE+mathplayer, Firefox, and
288 Opera, but not Safari.
289
290 2. `jsMath`: Math will be rendered using the [jsMath][] javascript.
291 If you want to use this method, download `jsMath` and `jsMath
292 Image Fonts` from the [jsMath download page][]. You'll have two
293 `.zip` archives. Unzip them both in the `static/js` directory (a new
294 subdirectory, `jsMath`, will be created). This works with all
295 browsers, but is slower and not as nice looking as MathML.
296
297 3. `raw`: Math will be rendered as raw LaTeX codes.
298
89725fd9 »
2008-11-06 Initial commit.
299 [jsMath download page]: http://sourceforge.net/project/showfiles.php?group_id=172663
300
e9ac5c2b »
2009-08-15 Make plugins flag enabled by default.
301 Plugins
302 =======
89725fd9 »
2008-11-06 Initial commit.
303
e9ac5c2b »
2009-08-15 Make plugins flag enabled by default.
304 Plugins are small Haskell programs that transform a wiki page after it
305 has been converted from Markdown or RST. See the example plugins in the
306 `plugins` directory. To enable a plugin, include the path to the plugin
307 (or its module name) in the `plugins` field of the configuration file.
308 (If the plugin name starts with `Network.Gitit.Plugin.`, gitit will assume that
309 the plugin is an installed module and will not look for a source file.)
89725fd9 »
2008-11-06 Initial commit.
310
e9ac5c2b »
2009-08-15 Make plugins flag enabled by default.
311 Plugin support is enabled by default. However, plugin support makes
312 the gitit executable considerably larger and more memory-hungry.
313 If you don't need plugins, you may want to compile gitit without plugin
314 support. To do this, unset the `plugins` Cabal flag:
89725fd9 »
2008-11-06 Initial commit.
315
e9ac5c2b »
2009-08-15 Make plugins flag enabled by default.
316 cabal install --reinstall gitit -f-plugins
89725fd9 »
2008-11-06 Initial commit.
317
e9ac5c2b »
2009-08-15 Make plugins flag enabled by default.
318 Note also that if you compile gitit for executable profiling, attempts
319 to load plugins will result in "internal error: PAP object entered!"
89725fd9 »
2008-11-06 Initial commit.
320
77d20a35 »
2009-04-27 README changes: running with darcs, updated some refs to config options.
321 Accessing the wiki via git or darcs
322 ===================================
89725fd9 »
2008-11-06 Initial commit.
323
77d20a35 »
2009-04-27 README changes: running with darcs, updated some refs to config options.
324 All the pages and uploaded files are stored in a git or darcs
325 repository. By default, this lives in the `wikidata` directory (though
326 this can be changed through configuration options). So you can interact
327 with the wiki using git command line tools:
89725fd9 »
2008-11-06 Initial commit.
328
329 git clone ssh://my.server.edu/path/of/wiki/wikidata
330 cd wikidata
331 vim Front\ Page.page # edit the page
332 git commit -m "Added message about wiki etiquette" Front\ Page.page
333 git push
334
335 If you now look at the Front Page on the wiki, you should see your changes
336 reflected there. Note that the pages all have the extension `.page`.
337
f22d5c4a »
2009-08-14 Changed default config to use-cache: no.
338 Caching
339 =======
340
341 By default, gitit does not cache content. If your wiki receives a lot of
342 traffic or contains pages that are slow to render, you may want to activate
343 caching. To do this, set the configuration option `use-cache` to `yes`.
344 By default, rendered pages and highlighted source files will be cached
345 in the `cache` directory. (Another directory can be specified by setting
346 the `cache-dir` configuration option.)
347
348 Cached pages are updated when pages are modified using the web
349 interface. They are not updated when pages are modified directly through
350 git or darcs. However, the cache can be refreshed manually by pressing
351 Ctrl-R when viewing a page, or by sending an HTTP GET or POST request to
352 `/_expire/path/to/page`, where `path/to/page` is the name of the page to
353 be expired.
354
355 Users who frequently update pages using git or darcs may wish to add a
356 hook to the repository that makes the appropriate HTTP request to expire
357 pages when they are updated. To facilitate such hooks, the gitit cabal
358 package includes an executable `expireGititCache`. Assuming you are
359 running gitit at port 5001 on localhost, and the environment variable
360 `CHANGED_FILES` contains a list of the files that have changed, you can
361 expire their cached versions using
362
363 expireGititCache http://localhost:5001 $CHANGED_FILES
364
365 Or you can specify the files directly:
366
367 expireGititCache http://localhost:5001 "Front Page.page" foo/bar/baz.c
368
369 This program will return a success status (0) if the page has been
370 successfully expired (or if it was never cached in the first place),
371 and a failure status (> 0) otherwise.
372
373 The cache is persistent through restarts of gitit. To expire all cached
374 pages, simply remove the `cache` directory.
375
488e6bbc » John MacFarlane
2009-04-18 README: Added instructions for proxying with apache.
376 Using gitit with apache
377 =======================
378
379 Most users who run a public-facing gitit will want gitit to appear
380 at a nice URL like `http://wiki.mysite.com` or
381 `http://mysite.com/wiki` rather than `http://mysite.com:5001`.
382 This can be achieved using apache's `mod_proxy`.
383
384 Proxying to `http://wiki.mysite.com`
385 ------------------------------------
386
387 Set up your DNS so that `http://wiki.mysite.com` maps to
388 your server's IP address. Make sure that the `mod_proxy` module is
389 loaded, and set up a virtual host with the following configuration:
390
391 <VirtualHost *>
392 ServerName wiki.mysite.com
393 DocumentRoot /var/www/
394 RewriteEngine On
395 ProxyPreserveHost On
396 ProxyRequests Off
397
398 <Proxy *>
399 Order deny,allow
400 Allow from all
401 </Proxy>
402
403 ProxyPassReverse / http://127.0.0.1:5001
404 RewriteRule ^(.*) http://127.0.0.1:5001$1 [P]
405
406 ErrorLog /var/log/apache2/error.log
407 LogLevel warn
408
409 CustomLog /var/log/apache2/access.log combined
410 ServerSignature On
411
412 </VirtualHost>
413
414 Reload your apache configuration and you should be all set.
415
416 Proxying to `http://mysite.com/wiki`
417 ------------------------------------
418
419 Make sure the `mod_proxy`, `mod_headers`, `mod_proxy_http`,
420 and `mod_proxy_html` modules are loaded. `mod_proxy_html`
421 is an external module, which can be obtained [here]
422 (http://apache.webthing.com/mod_proxy_html/). It rewrites URLs that
423 occur in web pages. Here we will use it to rewrite gitit's links so that
424 they all begin with `/wiki/`.
425
f8ab67e6 »
2009-04-27 Reformatting (line lengths) of README.
426 First, tell gitit not to compress pages, since `mod_proxy_html` needs
427 uncompressed pages to parse. You can do this by setting the gitit
428 configuration option
488e6bbc » John MacFarlane
2009-04-18 README: Added instructions for proxying with apache.
429
77d20a35 »
2009-04-27 README changes: running with darcs, updated some refs to config options.
430 compress-responses: no
431
432 Second, modify the link in the `reset-password-message` in the
433 configuration file: instead of
434
435 http://$hostname$:$port$$resetlink$
436
437 set it to
438
439 http://$hostname$/wiki$resetlink$
488e6bbc » John MacFarlane
2009-04-18 README: Added instructions for proxying with apache.
440
441 Restart gitit.
442
443 Now add the following lines to the apache configuration file for the
444 `mysite.com` server:
445
446 # These commands will proxy /wiki/ to port 5001
447
448 ProxyRequests Off
449
450 <Proxy *>
451 Order deny,allow
452 Allow from all
453 </Proxy>
454
455 ProxyPass /wiki/ http://127.0.0.1:5001/
456
457 <Location /wiki/>
458 SetOutputFilter proxy-html
459 ProxyPassReverse /
460 ProxyHTMLURLMap / /wiki/
461 RequestHeader unset Accept-Encoding
462 </Location>
463
464 Reload your apache configuration and you should be set.
465
466 For further information on the use of `mod_proxy_http` to rewrite URLs,
467 see the [`mod_proxy_html` guide].
468
469 [`mod_proxy_html` guide]: http://apache.webthing.com/mod_proxy_html/guide.html
470
e86d3dce »
2009-06-24 Added note on using gitit as a library to README.
471 Using gitit as a library
472 ========================
473
474 By importing the module `Network.Gitit`, you can include a gitit wiki
475 (or several of them) in another happstack application. There are some
476 simple examples in the haddock documentation for `Network.Gitit`.
477
45a9c7fb »
2008-11-07 Reformatted README using standard markdown.
478 Reporting bugs
479 ==============
89725fd9 »
2008-11-06 Initial commit.
480
a49ba22c »
2008-12-07 Added link to bug tracker on googlecode.
481 Bugs may be reported (and feature requests filed) at
482 <http://code.google.com/p/gitit/issues/list>.
89725fd9 »
2008-11-06 Initial commit.
483
41595eea »
2009-07-12 Added notice of mailing list to README.
484 There is a mailing list for users and developers at
485 <http://groups.google.com/group/gitit-discuss>.
486
45a9c7fb »
2008-11-07 Reformatted README using standard markdown.
487 Acknowledgements
488 ================
89725fd9 »
2008-11-06 Initial commit.
489
bb8abc3a »
2009-04-27 Improved acknowledgements, bringing list of contributors up to date.
490 A number of people have contributed patches:
491
8500b29a »
2009-04-27 More contributors.
492 - Gwern Branwen helped to optimize gitit and wrote the
f22d5c4a »
2009-08-14 Changed default config to use-cache: no.
493 InterwikiPlugin. He also helped with the Feed module.
bb8abc3a »
2009-04-27 Improved acknowledgements, bringing list of contributors up to date.
494 - Simon Michael contributed the patch adding RST support.
495 - Henry Laxen added support for password resets and helped with
496 the apache proxy instructions.
497 - Anton van Straaten made the process of page generation
498 more modular by adding Gitit.ContentTransformer.
058ce025 »
2009-07-09 Acknowledge Robin Green's patch in README.
499 - Robin Green helped improve the plugin API and interface, and
500 fixed a security problem with the reset password code.
edeca79e » John MacFarlane
2009-04-27 More acknowledgements.
501 - Thomas Hartman helped improve the index page, making directory
502 browsing persistent.
bb8abc3a »
2009-04-27 Improved acknowledgements, bringing list of contributors up to date.
503 - Justin Bogner improved the appearance of the preview button.
8500b29a »
2009-04-27 More contributors.
504 - Kohei Ozaki contributed the ImgTexPlugin.
cf6e15e1 »
2009-06-24 Added acknowledgement for mightybyte.
505 - mightybyte suggested making gitit available as a library,
506 and contributed a patch to ifLoggedIn that was needed to
507 make gitit usable with a custom authentication scheme.
bb8abc3a »
2009-04-27 Improved acknowledgements, bringing list of contributors up to date.
508
509 Gitit's default visual layout is shamelessly borrowed from Wikipedia.
5c5c3374 »
2008-11-22 Updated README.
510 The stylesheets are influenced by Wikipedia's stylesheets and by the
511 bluetrip CSS framework (see BLUETRIP-LICENSE). Some of the icons in
512 `img/icons` come from bluetrip as well.
513
Something went wrong with that request. Please try again.