Hey,
2016-07-11 16:24 GMT+02:00 K. Frank <kfrank2...@gmail.com>:
> Hello List!
>
> I am building my app to be a wthttpd server. When I start it from the
> command line, I pass it the --docroot argument, for example, as:
>
> mixed_links --http-address=0.0.0.0 --http-port=80
> --deploy-path=/mixed_links --docroot=".;/static_links"
>
In this call, --docroot=".;/static_links" is equivalent to --docroot=".".
The ';/path1,/path2,.." syntax is only used to get rid of so-called "ugly
internal path URLs" that are encoded as a query argument
'?_=/internal/path'. This is used in Wt only if you're deploying on a path
that ends itself with a '/', for example --deploy-path=/mixed_links/ or the
default --deploy-path='/'. In that case it is used to be able to use
nice-looking internal paths (/internal/path) while still knowing which
paths ('/static_links') to have handled by the static file server of
wthttpd. If the application is not deployed ending with a '/' then there is
no ambiguity in the first place.
Since you are not having ugly internal paths to start with (you may even
not be using them?), you probably want something different, but from your
explanation I'm not exactly sure what. The docroot directive is really
similar to the 'docroot' as you would configure them in any other webserver
such as apache or nginx.
Admittedly, it's a common, recurring, confusing topic all-together.
Koen
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest
