That is a good point. I tried to be as close as possible to the original. What are you thoughts on data_dir? I would like to stick with how the original plugin implemented it (as a dir next to views/). One other reason for that is (according to the doc) is that you win a bit on startup as you don't have to recompile the module, although I kind of feel like startup time is a bit of a moot point for an application that technically does not get restarted often.
-Slava On Tue, Oct 1, 2013 at 2:01 AM, Pedro Melo <[email protected]> wrote: > Hi, > > On Mon, Sep 30, 2013 at 8:35 PM, Slavik Goltser <[email protected]> wrote: > >> I agree on the naming (it was a conflict in my mind when I was doing it). >> the data_dir is literally ripped out from the original. any idea where it >> puts things without any data_dir definition? >> > > Yes, on the default place as set by Mason. It's defined here [1] and > currently is set to be a temporary directory that will be deleted when the > process dies. > > [1]: https://metacpan.org/module/Mason::Interp#data_dir > > I'll try your module with some of my sites at work to see if I can detect > further problems. > > Bye, > -- > Pedro Melo > @pedromelo > http://www.simplicidade.org/ > xmpp:[email protected] > mailto:[email protected] > > _______________________________________________ > dancer-users mailing list > [email protected] > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > >
_______________________________________________ dancer-users mailing list [email protected] http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
