Collision of multiple Dancer apps using Plack::Handler::Apache2
Hi, I have just discovered a problem with a couple of Dancer apps that we have deployed onto the same Apache using Plack::Handler::Apache2. The apps are configured in separate virtual hosts but the routes and other configuration is getting confused between the two apps. I checked the mailing list archive and found this message from September of last year which seems to be the problem we have encountered. Unfortunately, there doesn¹t appear to have been any response to the message: http://lists.perldancer.org/pipermail/dancer-users/2010-September/000344.htm l Is this something that has been fixed? Or has a workaround? In the meantime we have had to switch one of our apps back to using CGI but we can¹t take this performance hit for too long. Other than this issue we are loving Dancer :) Thanks, Matt
Hi Matt! Happy to hear you're loving Dancer. :) The mailing list certainly does not get the appropriate attention it deserves. Sometimes you get your reply, sometimes it slips between the chairs. The best way to get a reply for a possible bug is to open a Github issue. It will either be worked on and resolved, or explained and closed. When it's an issue, we take it more seriously. Also, it's possible to get replies in our friendly IRC channel (#dancer on irc.perl.org). Considering this sounds like a bug, I'd opt for opening a bug. We would really appreciate it. Thanks, and have a great day! Sawyer. On Mon, May 9, 2011 at 7:18 AM, Matthew Robinson < matt.robinson@curtin.edu.au> wrote:
Hi,
I have just discovered a problem with a couple of Dancer apps that we have deployed onto the same Apache using Plack::Handler::Apache2. The apps are configured in separate virtual hosts but the routes and other configuration is getting confused between the two apps. I checked the mailing list archive and found this message from September of last year which seems to be the problem we have encountered. Unfortunately, there doesn’t appear to have been any response to the message: http://lists.perldancer.org/pipermail/dancer-users/2010-September/000344.htm...
Is this something that has been fixed? Or has a workaround?
In the meantime we have had to switch one of our apps back to using CGI but we can’t take this performance hit for too long.
Other than this issue we are loving Dancer :)
Thanks,
Matt
_______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
participants (2)
-
Matthew Robinson -
sawyer x