1 == A vision for fuse-mediawiki 0.2 ==
3 Using regex is very icky. We're switching to the write API built into MediaWiki
4 1.13 and later. This means the wiki that you'll be working on needs to be
5 compatible with what is being done in fuse-mediawiki. fuse-mediawiki will have
6 some internal checks and let you know what can or can't be done.
8 We'll also be getting rid of auth_basic. It's possible that
9 both of these could be added back in a later version, but I don't want to have
10 to deal with them right now.
12 I'm going to completely do away with the instant-write-to-MediaWiki on every
13 write to the "filesystem". Instead, saves will be stored in the filesystem, and
14 a script in the root directory called "push" will be used (which will be a
15 symlink to "scripts/push.py" in whatever directory the fuse-mediawiki.py script
16 is). Theoretically, the end user can run
17 ./push content/Main_Page.wiki -m "edit summary"
18 to push changes back to the wiki. If there's no -m, it'll throw open $EDITOR.
20 There will be an image/ and cat/ directory, alongside the content/ directory.
21 To get the information for an image, or the content part of a category page,
22 you can get the content by touching 'Image:Whatever.png' or 'Category:Whatever'
23 in the content/ directory.
25 We'll have a load.py script to load certain parts of the wiki, like so:
26 ./load prefix Apple # load any page that starts with "Apple"
27 ./load namespace Wikipedia # loads all pages in the Wikipedia: namespace
28 and probably lots of others. Anything the API supports will hopefully be in
29 here. ./load --help will always tell you what you can do.
31 Some scripts that we'll have: