Hi Kevin and list!
On 2005-08-17 01:43:21, Kevin Griffin wrote:
Perfect. You can read minds. I wanted to add a simple start script in the next release. But this one is better.
One thing: In the next release a config file will be read from the current directory.
I think the current directory is a nice place for web application specific configurations. But I could add a parameter to WIKI:START. And you could add a directory for the script to change into.
By the way: I've migrated all of CL-WIKI from Subversion to darcs. A very nice version control for distributed development. In the future there will be a development and a stable repository on CL-WIKI's project page on common-lisp.net Then every "in the next release" statement of mine can be tested at own risk. :-)
Regards, Stefan
Stefan Scholl wrote:
Hi Kevin and list!
On 2005-08-17 01:43:21, Kevin Griffin wrote:
Perfect. You can read minds. I wanted to add a simple start script in the next release. But this one is better.
This script, written by Ian Clelland - was designed for unattended startup, at boot time. Also, the lispworld we are using in that case comes with wiki:*wiki-directory* and wiki:*wiki-template-directory* already set, so that it need not be set by the script.
This is probably not optimal for testing, nor is it the most flexible of solutions.
One thing: In the next release a config file will be read from the current directory.
I'm looking forward to it.
I think the current directory is a nice place for web application specific configurations. But I could add a parameter to WIKI:START. And you could add a directory for the script to change into.
Sure thing.
On 2005-08-25 10:43:45, Kevin Griffin wrote:
Stefan Scholl wrote:
One thing: In the next release a config file will be read from the current directory.
I'm looking forward to it.
I'm sorry you need a little more patience than expected (by myself). It's only a little release but it have to wait for a few days more.
The next few steps are:
1.) Make this small(!) release 2.) Figure out some nice way to store the wiki pages. Some meta data is needed and it should be possible to integrate typical wiki features like versioning and diffs. 3.) Relasee it 4.) Bring up the darcs repositories. One for stable releases and one for development.
The project is alive and will be kicking, I'm sure. :-)
-
Kevin Griffin -
Stefan Scholl