X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/c06adfafef8b8e462bf9ceb2856aae9de6d2f3a4..5577564a68b413218444f7db6295cede42a54944:/doc/index/discussion.mdwn?ds=inline diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn index 0d29853f9..d5db8ee01 100644 --- a/doc/index/discussion.mdwn +++ b/doc/index/discussion.mdwn @@ -95,28 +95,7 @@ I just figured I'd edit something on the page with my OpenID, since you've imple # ACL -How about adding ACL? So that you can control which users are allowed -to read, write certain pages. The moinmoin wiki has that, and it is -something, that I think is very valuable. - -> ikiwiki currently has only the most rudimentary access controls: pages -> can be locked, or unlocked and only the admin can edit locked pages. That -> could certianly be expanded on, although it's not an area that I have an -> overwhelming desire to work on myself right now. Patches appreciated and -> I'll be happy to point you in the right directions.. --[[Joey]] - ->> I'm really curious how you'd suggest implementing ACLs on reading a page. ->> It seems to me the only way you could do it is .htaccess DenyAll or something, ->> and then route all page views through ikiwiki.cgi. Am I missing something? ->> --[[Ethan]] - ->>> Or you could just use apache or whatever and set up the access controls ->>> there. Of course, that wouldn't integrate very well with the wiki, ->>> unless perhaps you decided to use http basic authentication and the ->>> httpauth plugin for ikiwiki that integrates with that.. --[[Joey]] - ->>>> Which would rule out openid, or other fun forms of auth. And routing all access ->>>> through the CGI sort of defeats the purpose of ikiwiki. --[[Ethan]] +> Moved to [[todo/ACL]] --[[Joey]] ---- @@ -136,20 +115,7 @@ the template. -- Ethan # Canonical feed location? -Any way to use `inline` but point the feed links to a different feed on the -same site? I have news in news/*, a news archive in news.mdwn, and the -first few news items on index.mdwn, but I don't really want two separate -feeds, one with all news and one with the latest few articles; I'd rather -point the RSS feed links of both to the same feed. (Which one, the one -with all news or the one with the latest news only, I don't know yet.) - -> Not currently. It could be implemented, or you could just turn off the -> rss feed for the index page, and manually put in a wikilink to the news -> page and rss feed. --[[Joey]] - ->> That wouldn't use the same style for the RSS and Atom links, and it ->> wouldn't embed the feed link into `` so that browsers can automatically ->> find it. +Moved to [[todo/canonical_feed_location]] --[[Joey]] ---- @@ -180,34 +146,6 @@ Any plugins or support for exporting to LaTeX? ---- -# Using with RCS? - -Any examples of using co(1), ci(1) and other RCS related tools with ikiwiki? - -> I don't belive that RCS offers enough SCM features to be useable as a -> fullfledged backend to ikiwiki. For one thing, there's no way to have -> hook scripts run when changes are ci'd, is there? So you'd have to ci and -> then manually run ikiwiki. It should be possible to do an RCS backend -> that supports web commits with ci, and history (parsing the rcs files by -> hand?). If you're a masochist. :-) --[[Joey]] - ->> It does have history using rlog(1) which is similar format to "cvs log". ->> I don't think it has any possible hooks. What would happen if I call ->> ikiwiki directly from rcs_commit? (I didn't try yet.) On that note, ->> I don't see any way for ikiwiki to generate a single file, but I guess ->> that doesn't matter as --refresh should be fast enough. ->> I made a Rcs/rcs.pm plugin from Stub. I have been testing it some. ->> ->> --JeremyReed - ->> I made a working rcs plugin. And I made a RCS-to-web CGI. Details ->> at [[patchqueue/rcs_(third-party_plugin)]] ->> --[[JeremyReed]] ->> ->> (Moved to patchqueue --[[Joey]]) - ----- - # Using with CVS? Any examples of using ikiwiki with cvs? @@ -233,3 +171,48 @@ Any setting for limiting how many kilobytes can be submitted via the "edit" form -- [[JeremyReed]] > Not currently. Worried about abuse? --[[Joey]] + +>> I didn't want it abused accidently or with malice. I was thinking that Perl's CGI.pm would handle this, but I don't see that. +>> I read that textarea max bytes may be 500 lines or 28000 characters or 30000 characters or 64kB. It seems like it +>> varies and I didn't test myself, because I guess it may depend on different clients and different HTTP servers. +>> This could be checked using javascript on the client side (before submitting) and by checking size on server side (before saving). --[[JeremyReed]] + +>>> The absolute limit varies by browser. If there are web servers that +>>> also limit it, I don't know of them. --[[Joey]] + +---- + +# Disable sub-discussion pages? + +Moved to [[bugs]] -- [[Joey]] + +---- + +# wiki\_file\_regexp and RCS ,v files + +I have RCS ,v files in my source directory. But get many "skipping bad filename" warnings. + +Also I don't see wiki\_file\_regexp documented. Because it is used with $config{wiki\_file\_regexp} I assume it can be set in the ikiwiki.setup. +I added a comma to it in my IkiWiki.pm in the defaultconfig(). But that was wrong (so I reverted back), because then the ,v files were copied to my www tree. + +What is the correct way to include ,v RCS revision files in my source tree without receiving the "bad" messages and without copying over to www tree? + +-- [[JeremyReed]] + +> Add the ,v to the $config{wiki_file_prune_regexps} array. This is how we +> skip equivilant files from other revision control systems too. +> --[[Joey]]] + +---- + +# Textile Plugin + +It was trivial, but I put together a plugin that uses the Textile markup +language, which I find to be the most superior of the various options for +that sort of thing. Where or how do I submit it for inclusion? + +> You can post it to [[plugins/contrib]]. --[[Joey]] + +>> Thanks. I tried using the "Add new post" form there, but apparently made a [mess of things somehow](http://ikiwiki.kitenet.net/contrib/textile___40__third-party_plugin__41__.html). Sorry about that. + +How does one go about making a markup language added by means of a plugin, the default markup language. In other words, I would like the index page to be written in Textile. If I include a index.txtl (where txtl is the extension I have assigned to be handled by the textile plugin), ikiwiki will ignore it and make a new index.mdwn. \ No newline at end of file