On 26-05-16 23:34, K. Frank wrote: > > I am still uncertain how static content, URLs, InternalPath, and > --docroot all work together. >
It's quite straightforward, there's approot: this is where your application runs, so if you open files from within your app, this is where to look. E.g., xml content files are usually found here. docroot: if your wt-app serves static files, they are served from this directory. But you have to tell the application which directories are used for this. By default, this is everything in the resources directory. --docroot=/place/to/static/content;/resources,more statics... A Wt application may run at 'domain.com/', but may also run at 'domain.com/heres/wt'. This is the deployment path of Wt. An internal path of Wt is whatever is beyond the deployment path. A URL is the full combination of scheme, hostname, and path (and maybe some parameters). > For starters, could you tell me the exact command line you use to > launch wthttpd (censored of any sensitive information, of course)? For development, I'm using approot = /path/to/source_tree/approot docroot = /path/to/source_tree/docroot;/static http-address = 0.0.0.0 http-port = 7654 > > Also, what system are you running on. (I am using Wt on windows 7.) > currently, I'm running Debian/Ubuntu. > When you say static content, do you mean ordinary html files (that > could be served by something other than wthttpd, if you so chose)? See above. Usually this is non-html content, although it could indeed include static html. For static html content, I would recommend using a WMessageResourceBundle. > > So, let's say you launch your wthttpd application (in windows notation) > from: > > C:\somelaunchdirectory As you word it, this would be your approot. > > Does this mean you have subdirectories > > C:\somelaunchdirectory\about > C:\somelaunchdirectory\login > C:\somelaunchdirectory\the\rest\is\clean > > and you list these directories in your --docroot command-line > argument? Do these three directories then each contain an index.html > file? I have something like ...\docroot\static\css\... ...\docroot\static\js\... ...\docroot\static\img\... ...\docroot\static\font\... but my mapping of the internal-path (e.g., /about) to a part of the wt application is not related to a file structure. HtH, Cheers, Rutger ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
