Hi Koen! On Thu, Jul 23, 2015 at 5:41 PM, Koen Deforche <k...@emweb.be> wrote: > Hey, > > 2015-07-23 21:03 GMT+02:00 K. Frank <kfrank2...@gmail.com>: >> Is it possible to support both link1, an app-rendered internal >> path, and page1.html, a plain, external html page, in the same >> "folder"? That is >> >> http://localhost/links/link >> http://localhost/links/page1.html >> >> (where "--deploy-path=/links")? > > Yes. But you have to explain to the wthttpd which 'paths' to consider > as static files to be fetched from the docroot. There's a special > syntax to do this when specifying the docroot, e.g.: > > --docroot="docroot;/resources,/links/page1.html,/links/page2.html"
Thanks. This does accomplish my goal of putting both internal and static links in the same "folder." > This configures the wthttpd to consider only the paths > /resources,/links/page1.html,/links/page2.html to be served as static > files, fetched > from the 'docroot' folder in the current working directory (thus > docroot/links/page1.html for example). > > If you do not specify this additional information, then Wt will assume > that everything under the deployment path is dynamic, and everything > else is static. As a side note, I did find this bit of documentation: http://www.webtoolkit.eu:3080/wt/doc/reference/html/overview.html#wthttpd specifically, this example: $ ../../build/examples/wt-homepage/Home.wt --docroot=".;/favicon.ico,/css,/resources,/style,/icons" ... which looks like is saying the same thing you just said. I had tried it and couldn't get it to work, I'm sure, in hindsight, because of some simple error like getting a path wrong. (Anyway, things work now.) > Regards, > koen Thanks again for your help getting started with Wt. K. Frank ------------------------------------------------------------------------------ _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
