Hi!

--- David Farber <[EMAIL PROTECTED]> wrote:
[SNIP]
> so i'd still like a way to run swiki headless under Linux.

Well, I do that (running Debian with Squeak .deb packages), works like a charm - like 
this:

/home/stsq/squeak -headless -memory 32m Squeak3.0-campaigner.imagew

BTWE - "squeak -?" gives this info:

Usage: squeak [<option>...] [<imageName> [<argument>...]]
       squeak [<option>...] -- [<argument>...]

<option> can be:
  -align <n>           align functions at n-bytes (jit)
  -browserWindow <id>  run as Netscape plugin in window <id>
  -display <dpy>       display on <dpy> (default: $DISPLAY)
  -fullscreen          occupy the entire screen
  -headless            run in headless (no window) mode
  -help                print this help message, then exit
  -jit                 enable the dynamic (runtime) compiler
  -lazy                go to sleep when main window unmapped
  -memory <size>[mk]   set initial memory size (default: 20m)
  -noevents            disable event-driven input support
  -notitle             disable the Squeak window title bar
  -secure              enable file sandbox
  -spy                 enable the system spy (jit)
  -version             print version information, then exit
  -xasync              don't serialize display updates
  -xshm                use X shared memory extension

Notes:
  <imageName> defaults to `Squeak3.0.image'.
  Using `unix:0' for <dpy> may improve local display performance.
  -xshm only works when Squeak is running on the X server host.
  <argument>s are ignored, but are processed by the Squeak image.
  The first <argument> normally names a Squeak `script' to execute.
  Precede <arguments> by `--' to use default image.

 
> (i'd also like:
>  1) to have a seperate configuration file

For the Swiki? Not really following you here.

>  2) the ability to listen on a specific IP address so i could run a swiki
> along side an Apache server doing virtual hosting.)

Well, a simple thing to do is putting the Swiki on a nonstandard port, like 8080 or 
whatever and
then use Apache's proxy-mechanisms to "pass through" a certain domain-name to that 
port. I do that
too - it works swell apart from the fact that the Swiki always insists on that it was 
"localhost"
that edited the page! :-) A tail from my httpd.conf follows:
---------
NameVirtualHost 195.43.243.112

<VirtualHost 195.43.243.112>
ServerName www.svinninge.com
RewriteEngine on
UseCanonicalName off
ProxyRequests on
NoCache *
ProxyPass /files http://195.43.243.112:8000/files
RewriteRule ^/Svinninge(.*)$  http://195.43.243.112:8000/Svinninge$1 [proxy]
RewriteRule ^/(.*)$ http://195.43.243.112:8000/Svinninge/$1 [proxy]
ProxyPassReverse / http://195.43.243.112:8000/Svinninge/
</VirtualHost>
-----

I have probably made it more complex than it needs to be, I am using a combination of
ProxyPass/ProxyPassReverse (which is the simple instrument to use) and rules for the 
RewriteEngine
(which is the advanced instrument to use) in order to map "www.svinninge.com" directly 
to the
Swiki top page. Oh, almost forgot - you need to enable the "LoadModule"-line to load
"proxy_module" and "rewrite_module" earlier in httpd.conf.

Well, it works anyway! Do note thought that if you want to see this in action on my 
site you need
to create your local hosts-file and map www.svinninge.com to the ip above - it has not 
been mapped
yet.

regards, G�ran


=====
G�ran Hultgren, [EMAIL PROTECTED]
GSM: +46 70 3933950, http://www.bluefish.se
"Department of Redundancy department." -- ThinkGeek

__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/

Reply via email to