The seating arrangement is not conducive to dancing on the dancer floor. Here is what I want to do -- set relative paths to directories (aliases, in the world of Apache) when using the built in Dancer server, version 1.3011. Here is why -- One, I am getting a bit sick of Apache. Methinks a lot of my performance problems are tied to Apache, perhaps because I don't know how to tune the heck out of it. Nevertheless, the major problem is, I get very, very poor error messaging with Dancer+Apache combination. An example -- I had a mistake in my script last night that I was accessing via Ajax. All I got was an error popup on the client telling me that "an internal error had occurred." Other than that, nothing in Apache error log, and, funnily I was/am also not getting any development.log output. In sheer frustration, I decided to run the built-in Dancer server, and boom! I got a nice message saying "var prcp not definted at line blah blah" and I also got messages in the development.log. The problem now? Well, none of my aliases, as declared in httpd.conf are available to the built-in server. Here is how I work -- I store all my common JavaScript libraries in ~/<http root>/lib, and all my applications in ~/<http root>/<app dir>. In my vhosts.conf file I define an alias for lib as `/lib ~/<http root>/lib` so I can access all my JS libraries via `<script type="text/javascript" src="/lib/funky/funky.min.js"></script>` and so on. How can I define these kind of aliases for the Dancer's built-in server? Additionally, what am I doing wrong that I always get such poor error reporting? -- Puneet Kishor