X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/e8b41583718247119b8e8469f22c3ef7e8f48fb6..378c2696d958cc4d51b79dca786c077374bba55a:/doc/index/discussion.mdwn?ds=inline diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn index 23c49f968..dedcdffa2 100644 --- a/doc/index/discussion.mdwn +++ b/doc/index/discussion.mdwn @@ -25,6 +25,72 @@ of via syslog? > > The reason is that I'm not logged in on the web server regularly to > > check the log files. I'll see whether I can install a logwatch instance. +I'm trying to install from scratch on a CentOS 4.6 system. I installed perl 5.8.8 from source and then added all the required modules via CPAN. When I build ikiwiki from the tarball, I get this message: + + rendering todo/calendar_--_archive_browsing_via_a_calendar_frontend.mdwn + *** glibc detected *** double free or corruption (!prev): 0x0922e478 *** + make: *** [extra_build] Aborted + +I'm kind of at a loss how to track this down or work around it. Any suggestions? --Monty + +> All I can tell you is that it looks like a problem with your C library or +> perl. Little perl programs like ikiwiki should only be able to trigger +> such bugs, not contain them. :-) Sorry I can't be of more help. +> --[[Joey]] + +> I had a similar problem after upgrading to the latest version of +> Text::Markdown from CPAN. You might try either looking for a Markdown +> package for CentOS or using the latest version of John Gruber's +> Markdown.pl: +> +> --[[JasonBlevins]], April 1, 2008 18:22 EDT + +>> Unfortunately I couldn't find a CentOS package for markdown, and I +>> couldn't quite figure out how to use John Gruber's version instead. +>> I tried copying it to site_perl, etc., but the build doesn't pick +>> it up. For now I can just play with it on my Ubuntu laptop for which +>> the debian package installed flawlessly. I'll probably wait for an +>> updated version of Markdown to see if this is fixed in the future. +>> --Monty + +---- + +# Installation of selected docs (html) + +The latest release has around 560 files (over 2MB) in html. + +Any suggestions or ideas on limiting what html is installed? + +For example, I don't see value in every ikiwiki install out there to also install personal "users" ikiwiki pages. + +For now I copy ikiwiki.setup. And then use pax with -L switch to copy the targets of the symlinks of the basewiki. + +I was thinking of making a list of desired documents from the html directory to install. + +--JeremyReed + +> You don't need any of them, unless you want to read ikiwiki's docs locally. +> +> I don't understand why you're installing the basewiki files manually; +> ikiwiki has a Makefile that will do this for you. --[[Joey]] + +>> The Makefile's install doesn't do what I want so I use different installer for it. +>> It assumes wrong location for man pages for me. (And it should consider using INSTALLVENDORMAN1DIR and +>> MAN1EXT but I don't know about section 8 since I don't know of perl value for that.) +>> I don't want w3m cgi installed; it is optional for my package. +>> I will just patch for that instead of using my own installer. +>> Note: I am working on the pkgsrc package build specification for this. This is for creating +>> packages for NetBSD, DragonFly and other systems that use pkgsrc package system. +>> --JeremyReed + +# Installation as non-root user + +I'd like to install ikiwiki as a non-root user. I can plow through getting all the +perl dependencies installed because that's well documented in the perl world, +but I don't know how to tell ikiwiki to install somewhere other than / --BrianWilson + +> Checkout the tips section for [SharedHosting](tips/SharedHosting). It should do the trick. --MattReynolds + ---- # Upgrade steps @@ -166,6 +232,11 @@ And ikiwiki CGI started working for me. The Ikiwiki docs about this requirement got removed in Revision 4367. There should be a page that lists the requirements. (I guess I could have used the debian/control file.) +> There is a page, [[install]] documents that 3.05 is needed. + +>> Sorry, I missed that. With hundreds of wikipages it is hard to read all of them. +>> I am updating the download page now to link to it. + I am now using ikiwiki 2.6.1 on my testing system. --JeremyReed @@ -199,6 +270,17 @@ easily, perl is possible (but I'm not strong in perl). >> Thanks for an excellent Xmas present, I will appreciate the additional >> users this will help switch to ikiwiki! --[[Joey]] + +>> Sounds great indeed. Learning from [here](http://www.bddebian.com/~wiki/AboutTheTWikiToIkiwikiConversion/) that HTML::WikiConverter needed for your conversion was not up-to-date on Debian I have now done an unofficial package, including your proposed Markdown patches, apt-get'able at 
deb http://debian.jones.dk/ sid wikitools
+>> -- [[JonasSmedegaard]] + + +>>I see the "We will post the scripts ...." was committed about a year ago. A current site search for "Moin" does not turn them up. Any chance of an appearance in the near (end of year) future? +>> +>> -- [[MichaelRasmussen]] + +>>> It appears the scripts were never posted? I recently imported my Mediawiki site into Iki. If it helps, my notes are here: --[[sabr]] + ---- # LaTeX support? @@ -228,24 +310,6 @@ Any setting for limiting how many kilobytes can be submitted via the "edit" form ---- -# Access Keys - -Would anyone else find this a valuable addition. In oddmuse and instiki (the only other -wiki engines I am currently using, the edit, home, and submit link tags have an -accesskey attribute. I find it nice not to have to resort to the mouse for those -actions. However, it may not be something everyone appreciates. Any thoughts? ---[Mazirian](http://mazirian.com) - -> Maybe, although it would need to take the critisism at -> into account. - ->> Thank you for that link. Given that the edit link is the first thing you tab to ->> in the current layout, I guess it isn't all that necessary. I have had a ->> a user complaint recently that Alt-e in oddmuse was overriding his access ->> to the browser menu. - ----- - # Editing the style sheet. It would be nice to be able to edit the stylesheet by means of the cgi. Or is this possible? I wasn't able to achieve it. @@ -285,32 +349,6 @@ Clicking on an old "?" or going to a create link but new Markdown content exists ---- -# User database tools? - -Any tool to view user database? - -Any tool to edit the user database? - -> No, but it's fairly easy to write such tools in perl. For example, to -> list all users in the user database: - - joey@kodama:~/src/joeywiki/.ikiwiki>perl -le 'use Storable; my $userinfo=Storable::retrieve("userdb"); print $_ foreach keys %$userinfo' - http://joey.kitenet.net/ - foo - -> To list each user's email address: - - joey@kodama:~/src/joeywiki/.ikiwiki>perl -le 'use Storable; my $userinfo=Storable::retrieve("userdb"); print $userinfo->{$_}->{email} foreach keys %$userinfo' - - joey@kitenet.net - -> Editing is simply a matter of changing values and calling Storable::store(). -> I've not written actual utilities to do this yet because I've only needed -> to do it rarely, and the data I've wanted has been different each time. -> --[[Joey]] - ----- - # Spaces in WikiLinks? Hello Joey, @@ -321,7 +359,7 @@ aren't allowed in WikiLinks now? My best regards, ---[[Paweł|ptecza]] +--[[PaweB|ptecza]] > See [[bugs/Spaces_in_link_text_for_ikiwiki_links]] @@ -345,6 +383,9 @@ I'm playing around with various ways that I can use subversion with ikiwiki. > away without running the post-commit wrapper on commit, and all you lose > is the ability to send commit notification emails. +> (And now that [[recentchanges]] includes rss, you can just subscribe to +> that, no need to worry about commit notification emails anymore.) + * Is it possible / sensible to have ikiwiki share a subversion repository with other data (either completely unrelated files or another ikiwiki instance)? This works in part but again the post-commit hook seems problematic. --[[AdamShand]] @@ -353,3 +394,36 @@ I'm playing around with various ways that I can use subversion with ikiwiki. > in the same repo. If you have two wikis in one repository, you will need > to write a post-commit script that calls the post-commit wrappers for each > wiki. + +---- + +# Regex for Valid Characters in Filenames + +I'm sure that this is documented somewhere but I've ransacked the wiki and I can't find it. :-( What are the allowed characters in an ikiwiki page name? I'm writing a simple script to make updating my blog easier and need to filter invalid characters (so far I've found that # and , aren't allowed ;-)). Thanks for any pointers. -- [[AdamShand]] + +> The default `wiki_file_regexp` matches filenames containing only +> `[-[:alnum:]_.:/+]` +> +> The IkiWiki::titlepage() function will convert freeform text to a valid +> page name. See [[todo/should_use_a_standard_encoding_for_utf_chars_in_filenames]] +> for an example. --[[Joey]] + +>> Perfect, thanks! +>> +>> In the end I decided that I didn't need any special characters in filenames and replaced everything but alphanumeric characters with underscores. In addition to replacing bad characters I also collapse multiple underscores into a single one, and strip off trailing and leading underscores to make tidy filenames. If it's useful to anybody else here's a sed example: +>> +>> # echo "++ Bad: ~@#$%^&*()_=}{[];,? Iki: +_-:./ Num: 65.5 ++" | sed -e 's/[^A-Za-z0-9_]/_/g' -e 's/__*/_/g' -e 's/^_//g' -e 's/_$//g' +>> Bad_Iki_Num_65_5 +>> +>>--[[AdamShand]] + +# Upgrade steps from RecentChanges CGI to static page? + +Where are the upgrade steps for RecentChanges change from CGI to static feed? +I run multiple ikiwiki-powered sites on multiple servers, but today I just upgraded one to 2.32.3. +Please have a look at + +Any suggestions? + +> There are no upgrade steps required. It does look like you need to enable +> the meta plugin to get a good recentchanges page though.. --[[Joey]]