Of cause, dancerctl is more important than buggy behavior of Dancer1 with plack + mount. Ok. Starts scripts of buggy soft is more important than buggy soft is run by them. But may be you are losing users of Dancer while discuss about dancerctl? I suggest easy solution - the single option on config file. It works in my project. You forward me to raw project Dancer2. Thanks. 29.11.2011 1:50 пользователь "Perlover" <perlover@perlover.com> написал:
Hello, Thanks for reply. But I will use my own patched version of Dancer-1 (i don't have a time for adaptation for Dancer2) If you don't want patch - it's your choose of cause as of authors. Ok, lets your users will have a problems with multi apps... Bye 28.11.2011 17:42 пользователь "Alexis Sukrieh" <sukria@sukria.net> написал:
This kind of patches are actually not really what we watn to do since we have dancer2 on the way which is going to solve these collisions.
A better way to help the project is to test an upgrade of your app to Dancer 2. Thanks.
2011/11/23 Perlover <perlover@perlover.com>:
Hello All,
I made a changes for Dancer1! Please to see pull request of https://github.com/sukria/Dancer/pull/703
I added new option to config: routes_per_app
If it is true in config routes will be work only for applications where i its defined. If not true - it works as worked before (backward compatible) I wrote a test for it All tests are passed
Now i will test it in my real project If i will find a some bugs i will notice you
Best regards, Perlover
P.S. And dear author(s) - please approve & merge other commit too - it fix bug with request->header() - https://github.com/sukria/Dancer/pull/702 _______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users