Although you can start Instiki on your server by simply running ./instiki from your install directory, your server will then stop once you quit your terminal session or log out of ssh.
Here is how it is done by instiki.org. It should work on any *nix, including Mac OS X:
nohup /full/path/to/ruby/ruby /full/path/to/instiki/instiki
--storage /full/path/to/storage
> /full/path/to/logs/instiki.`date "+%Y%m%d%H%M%S"`.log &
This will start Instiki, run it in the background (that’s the “&”), and write the server output to a file called something like “instiki.20050431120052.log”, where the digits are system time at the time when instiki starts.
You can then run
tail -f instiki.[whatever].out
Note that by default Instiki logs to a STDERR, so depending on which shell you use, you may have a different syntax for stderr redirection to a file.
——
You can also accomplish the same thing (minus the logging) by running the standard startup script with the -- daemon command before the -- storage command.
ruby /Users/username/Sites/instiki/instiki.rb --port 2516 --daemon --storage /Users/username/Sites/instiki/storage/
That does the trick for me on both OS X and at Text Drive (my web host).
—daemon option has some thread-safety issues in Instiki 0.10.0 – 0.10.2. It can be used with Instiki-AR betas and the current SVN trunk.
——
Can anybody say where the log output goes when the server is started with the daemon option? Is there any?
——
If you install from FreeBSD ports, Instiki may hang when you restart it.
When the next new version will be released?