From Issue #144April 2006
I would like to appreciate your efforts in for writing this useful article. I am sure it will make the difference You are truly my inspiration. You, see when i first log in to google to i did not think that i could find such a interesting direction, which would really help me in a positive manner. May God bless you that you will keep doing the nice work always.
The company I work for uses MediaWiki as an internal know-how database.
I had problems with graphics showing up using NatSkin, but I suspect it would be in all ather skins as well.
Long story short:
I looked in /var/log/httpd/ssl_error_log and found errors
Edited /etc/httpd/conf/httpd.conf and changed
Alias /wiki "/var/www/localhost/wiki"
Alias /wiki "/var/www/wiki"
Restarted httpd and it worked....
The "localhost" seems to cause things not to work, at least for me.
There is an article on twiki performance tuning in the April 2006 issue of Sysadmin Magazine: http://www.samag.com/current/
The author is able to boost twiki installations by factor 20 for read access.
The method presented can be used for other wikis too.
The article title suggests that it will discuss using Wiki's and Blog's for documentation. It does start out with a short "why" on Wiki's, it does not addresses "why blogs" at all. I would have liked more information on why and how. Examples are key for me, personally.
My companies documentation is a bit of a mess. We are using a UML tool to document everything which means:
1) It was a lot of work work to put togther and just as much work to maintain (which means that a week later, it was already out of date).
2) Impossible to get a report out of it. I'm no expert in the tool, but I should not have to be to extract information I put in.
3) As pointed out above, too much overhead to learn. I spend enough of my free time reading articles and books on subjects that I am paid to do (and enjoy doing). I'm not going to spend an evening reading the manual of a tool I don't think fits the job.
Sorry - a little off track but I got a little frustrated reading an article on how to install software when I expected to read why I would want to.
Those examples above won't work. Instead of
(space)(space)(space)Set BLAHBLAH = something
you need a TWiki bullet point:
(space)(space)(space)*(space)Set BLAHBLAH = something.
URL for help with SpeedyCGI:
I have two blogs at work. One is called "The life of the machines" where each machine has it's own category. All entries are short descriptions about things that I or someone else inside the company have done to the machines.
Another one is called "The laboratory" and it is personal but mostly open to anybody inside our company. I use it to document things I have experimented with, things I have done during the day and things that are still open for the next day or for the near future. It also serves as a store for ideas to experiment with etc. I have categories for several projects and also use the blog to track time spent in projects with a plugin I have written for the task. I even use tracked time as basis of intra corporation billing. I have also integrated my blog as a datasource for the company reporting system. I can run reports against my blog and see where my time has gone in a nice pie chart.
Of course I write official documentation based on my blog entries to the company wiki. ;-)
It's working like a charm.
A friend of me is also using MediaWiki as an external database. I think it's a great idea and hope to have the time to test it on my own soon.
Actually, TWiki-4.0 (codename dakar) has been released on 1 Feb 2006 already. There's even a first maintenance release, TWiki-4.0.1 available. The patch described above isn't necessary anymore.
The previous release (TWiki20040904) was available on 28 Feb 2005.
I recommend to run TWiki by using SpeedyCGI, not FastCGI or mod_perl.
Michael, any tips on setting it up with SpeedyCGI?
easiest speedy setup is to use the cgi, not the apache mod, and just replace the perl shebang line with the path to speedy e.g. "#!/path/to/speedy". Don't accelerate all the scripts, just bin/view is sufficient. more at http://twiki.org/cgi-bin/view/Codev/SpeedyCGI