to get dokuiki pages you can access to local filesystem (raw text files) or via xmlrpc api via https to dokuwiki instance
Hey all,
I'm trying to work through a problem and so far haven't found a solution, so wondering if anyone has either of these two challenges figured out. Searched messages a bit to no avail.
Actual problem:
I'd like to get the text of a dokuwiki onto my BBS. I don't like the idea of some sort of automated text export, then updated to text files on the BBS, but I suppose that's the ultimate fallback.
Gopher seemed interesting, but I
don't think there's a good way to do that.
Crappy solution:
So I was thinking, why not just make a browser door? Ended up playing around with adding Links2 as a door, as described in http://wiki.synchro.net/howto:linuxapps . But as I suspected, there are multiple security issues, the worst of which is that Links2 in text mode has File->OS Shell in the menu with no way I can find to disable it.
Anyone solved either of these problems or have any good (or bad) ideas to try?
I think what you want is to run links2 with the -anonymous switch. It does a lot of "kiosk mode" type things that you'd want here, and it appears to remove the "OS Shell" menu option among other things.
ohhhhh just notice this modules.. I see it later! very good
to get dokuiki pages you can access to local filesystem (raw text files) or via xmlrpc api via https to dokuwiki instance
DokiWiki articles are already plain text (stored in your data/pages directory), for example:
"Use the source Luke". :-) As with most things *nix, as a last resort, you could just modify the source code to remove that option/feature and rebuild it.
I've wanted to make my DokuWiki pages available to terminal server users in the past too, but I was thinking more just the individual file route and not following links between pages and such (like an actual browser).
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 60 |
Nodes: | 4 (0 / 4) |
Uptime: | 11:17:57 |
Calls: | 516 |
Files: | 7,037 |
Messages: | 288,522 |