Hi all, I have this simply setup that worked well under 1.2003 config.yml: template: template_toolkit layout: main views/header.tt: <DOCTYPE .... ... <body> views/index.tt <h1>test</h1> views/footer.tt </body> </html> views/layouts/main.tt [% INCLUDE header.tt %] [% content %] [% INCLUDE footer.tt %] lib/myapp.pm ... get '/' => sub { template 'index.tt' }; Request on http://localhost:3000/ gives now the follow error: [1914] core @0.004733> [hit #1]request to / crashed: '/path/to/dancer/myapp/views/' is not a regular file at /usr/local/share/perl/5.10.1/Dancer/Helpers.pm line 39 in /usr/local/share/perl/5.10.1/Dancer/Handler.pm l. 76 Any idea why ? Thanks Thomas
On 30/01/2011 08:02, Thomas Maier wrote:
Hi all,
I have this simply setup that worked well under 1.2003
Just for the record, it's best to report bugs on the GitHub issue tracker, it's easier for us that way: http://github.com/sukria/Dancer/issues If you do so, tag it with "bug-devel-branch". Also, keep in mind that the 1.2 release series is still maintained, actually, it's the stable branch, as explained here:http://perldancer.org/quickstart ("About version numbers"). So upgrading to the 1.3 series might include some bug, this is the development branch, so that can happen. I just wanted to underline that ;) Thanks for the report anyway, we'll try to track this down. Regards, -- Alexis Sukrieh
On Sun, Jan 30, 2011 at 11:40 AM, Alexis Sukrieh <sukria@sukria.net> wrote:
On 30/01/2011 08:02, Thomas Maier wrote:
Hi all,
I have this simply setup that worked well under 1.2003
Just for the record, it's best to report bugs on the GitHub issue tracker, it's easier for us that way: http://github.com/sukria/Dancer/issues
If you do so, tag it with "bug-devel-branch".
Also, keep in mind that the 1.2 release series is still maintained, actually, it's the stable branch, as explained here:http://perldancer.org/quickstart ("About version numbers").
So upgrading to the 1.3 series might include some bug, this is the development branch, so that can happen. If so, maybe the CPAN is not the best place for development branch. In my case it's serious problem. I deploy with my application simple script to install list of CPAN modules (using cpanm) I'm using. Those who use my application doesn't even know that CPAN exists. It's very comfortable for me to install this way the whole environment on the client machines. Thus 1.3 on CPAN is a real trouble for me. And maybe for others as well. Isn't github the right place to keep the development branch? Sorry if I'm missing something here..
I just wanted to underline that ;)
Thanks for the report anyway, we'll try to track this down.
Regards,
-- Alexis Sukrieh _______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
Thomas Maier wrote:
On Sun, Jan 30, 2011 at 11:40 AM, Alexis Sukrieh<sukria@sukria.net> wrote:
On 30/01/2011 08:02, Thomas Maier wrote:
Hi all,
I have this simply setup that worked well under 1.2003 Just for the record, it's best to report bugs on the GitHub issue tracker, it's easier for us that way: http://github.com/sukria/Dancer/issues
If you do so, tag it with "bug-devel-branch".
Also, keep in mind that the 1.2 release series is still maintained, actually, it's the stable branch, as explained here:http://perldancer.org/quickstart ("About version numbers").
So upgrading to the 1.3 series might include some bug, this is the development branch, so that can happen. If so, maybe the CPAN is not the best place for development branch. In my case it's serious problem. I deploy with my application simple script to install list of CPAN modules (using cpanm) I'm using. Those who use my application doesn't even know that CPAN exists. It's very comfortable for me to install this way the whole environment on the client machines. Thus 1.3 on CPAN is a real trouble for me. And maybe for others as well. Isn't github the right place to keep the development branch? Sorry if I'm missing something here..
Another (reinforcing) perspective from a user -- the whole thing seems very messy from a user-point-of-view. There is the perldancer.org web site, there is CPAN, and there is Github. All three are ever so slightly out of sync, and I never know where to go for what. By habit I always go to search.cpan.org and find Dancer from there to look for docs (I never could get my local docs to work reliably). To install, I always use cpanm, and trust it to "do the right thing." For kicks, I go to perldancer.org, or turn new comers to that web site. Wish things were simpler, with one canonical web site for the rest of the world.
I just wanted to underline that ;)
Thanks for the report anyway, we'll try to track this down.
Regards,
..
-- Puneet Kishor
CPAN has a mechanism for marking releases development releases. When they're marked as such, most cpan clients will not install them by default. Whoever is releasing dev versions to cpan should just do that. On Fri, Feb 4, 2011 at 6:19 AM, Puneet Kishor <punk.kish@gmail.com> wrote:
Thomas Maier wrote:
On Sun, Jan 30, 2011 at 11:40 AM, Alexis Sukrieh<sukria@sukria.net> wrote:
On 30/01/2011 08:02, Thomas Maier wrote:
Hi all,
I have this simply setup that worked well under 1.2003
Just for the record, it's best to report bugs on the GitHub issue tracker, it's easier for us that way: http://github.com/sukria/Dancer/issues
If you do so, tag it with "bug-devel-branch".
Also, keep in mind that the 1.2 release series is still maintained, actually, it's the stable branch, as explained here:http://perldancer.org/quickstart ("About version numbers").
So upgrading to the 1.3 series might include some bug, this is the development branch, so that can happen.
If so, maybe the CPAN is not the best place for development branch. In my case it's serious problem. I deploy with my application simple script to install list of CPAN modules (using cpanm) I'm using. Those who use my application doesn't even know that CPAN exists. It's very comfortable for me to install this way the whole environment on the client machines. Thus 1.3 on CPAN is a real trouble for me. And maybe for others as well. Isn't github the right place to keep the development branch? Sorry if I'm missing something here..
Another (reinforcing) perspective from a user -- the whole thing seems very messy from a user-point-of-view. There is the perldancer.org web site, there is CPAN, and there is Github. All three are ever so slightly out of sync, and I never know where to go for what. By habit I always go to search.cpan.org and find Dancer from there to look for docs (I never could get my local docs to work reliably). To install, I always use cpanm, and trust it to "do the right thing." For kicks, I go to perldancer.org, or turn new comers to that web site.
Wish things were simpler, with one canonical web site for the rest of the world.
I just wanted to underline that ;)
Thanks for the report anyway, we'll try to track this down.
Regards,
..
-- Puneet Kishor _______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
The suggested mechanism seems to be the following (perldoc CPAN): Developers may mark their releases as unstable development versions (by inserting an underbar into the module version number which will also be reflected in the distribution name when you run 'make dist'), so the really hottest and newest distribution is not always the default. I see that some distributions are marked as "developer" also in other ways, e.g. DBIx::Class adds a "-TEST" somewhere. Cheers, Flavio. On Fri, Feb 4, 2011 at 5:44 PM, Brian E. Lozier <brian@massassi.com> wrote:
CPAN has a mechanism for marking releases development releases. When they're marked as such, most cpan clients will not install them by default. Whoever is releasing dev versions to cpan should just do that.
On Fri, Feb 4, 2011 at 6:19 AM, Puneet Kishor <punk.kish@gmail.com> wrote:
Thomas Maier wrote:
On Sun, Jan 30, 2011 at 11:40 AM, Alexis Sukrieh<sukria@sukria.net> wrote:
On 30/01/2011 08:02, Thomas Maier wrote:
Hi all,
I have this simply setup that worked well under 1.2003
Just for the record, it's best to report bugs on the GitHub issue tracker, it's easier for us that way: http://github.com/sukria/Dancer/issues
If you do so, tag it with "bug-devel-branch".
Also, keep in mind that the 1.2 release series is still maintained, actually, it's the stable branch, as explained here:http://perldancer.org/quickstart ("About version numbers").
So upgrading to the 1.3 series might include some bug, this is the development branch, so that can happen.
If so, maybe the CPAN is not the best place for development branch. In my case it's serious problem. I deploy with my application simple script to install list of CPAN modules (using cpanm) I'm using. Those who use my application doesn't even know that CPAN exists. It's very comfortable for me to install this way the whole environment on the client machines. Thus 1.3 on CPAN is a real trouble for me. And maybe for others as well. Isn't github the right place to keep the development branch? Sorry if I'm missing something here..
Another (reinforcing) perspective from a user -- the whole thing seems
very
messy from a user-point-of-view. There is the perldancer.org web site, there is CPAN, and there is Github. All three are ever so slightly out of sync, and I never know where to go for what. By habit I always go to search.cpan.org and find Dancer from there to look for docs (I never could get my local docs to work reliably). To install, I always use cpanm, and trust it to "do the right thing." For kicks, I go to perldancer.org, or turn new comers to that web site.
Wish things were simpler, with one canonical web site for the rest of the world.
I just wanted to underline that ;)
Thanks for the report anyway, we'll try to track this down.
Regards,
..
-- Puneet Kishor _______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
_______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
On Fri, 04 Feb 2011 08:19:30 -0600, Puneet Kishor <punk.kish@gmail.com> wrote: [...]
Another (reinforcing) perspective from a user -- the whole thing seems very messy from a user-point-of-view. There is the perldancer.org web site, there is CPAN, and there is Github. All three are ever so slightly
out of sync, and I never know where to go for what. By habit I always go
to search.cpan.org and find Dancer from there to look for docs (I never could get my local docs to work reliably). To install, I always use cpanm, and trust it to "do the right thing." For kicks, I go to perldancer.org, or turn new comers to that web site.
Wish things were simpler, with one canonical web site for the rest of the world.
You're right, and we're aware of that. I'm at FOSDEM the whole weekend, with Sawyer, Franck dans Dams and we're going to think about that issue. It's being working on. We know our release cycle could be improved, and is confusing for CPAN users. We'll work on that and keep you guys in touch. Regards, -- Alexis Sukrieh
Thomas Maier a écrit :
get '/' => sub { template 'index.tt' };
Request on http://localhost:3000/ gives now the follow error: [1914] core @0.004733> [hit #1]request to / crashed: '/path/to/dancer/myapp/views/' is not a regular file at /usr/local/share/perl/5.10.1/Dancer/Helpers.pm line 39 in /usr/local/share/perl/5.10.1/Dancer/Handler.pm l. 76
Any idea why ?
Delete the extension .tt. Dancer automagically add the extension based on the template you use. https://github.com/sukria/Dancer/blob/master/lib/Dancer/Template/Abstract.pm (line 129) Regards. -- Eric
On 1/31/2011 10:22 AM, Eric Guirbal wrote:
Thomas Maier a écrit :
get '/' => sub { template 'index.tt' };
Request on http://localhost:3000/ gives now the follow error: [1914] core @0.004733> [hit #1]request to / crashed: '/path/to/dancer/myapp/views/' is not a regular file at /usr/local/share/perl/5.10.1/Dancer/Helpers.pm line 39 in /usr/local/share/perl/5.10.1/Dancer/Handler.pm l. 76
Any idea why ?
Delete the extension .tt. Dancer automagically add the extension based on the template you use.
https://github.com/sukria/Dancer/blob/master/lib/Dancer/Template/Abstract.pm (line 129)
But 'tt' extension works fine with Dancer 1.2003? Is it really the reason of this crash? Thomas
Thomas Maier a écrit :
But 'tt' extension works fine with Dancer 1.2003? Is it really the reason of this crash?
Sorry, I answered too quickly. In fact, dancer verifies if the view has the extension and if not it adds it. So it shouldn't crash. -- Eric
GitHub recently added http://gist.github.com/: *Gist* is a simple way to *share snippets and pastes* with others. All gists are git repositories, so they are automatically *versioned*, *forkable* and usable as a *git repository*. If you have a workable example you can put it there so that it's easy to reproduce the problem. Cheers, Flavio. On Sun, Jan 30, 2011 at 8:02 AM, Thomas Maier <hayzer@gmail.com> wrote:
Hi all,
I have this simply setup that worked well under 1.2003
config.yml: template: template_toolkit layout: main
views/header.tt: <DOCTYPE .... ... <body>
views/index.tt <h1>test</h1>
views/footer.tt </body> </html>
views/layouts/main.tt [% INCLUDE header.tt %] [% content %] [% INCLUDE footer.tt %]
lib/myapp.pm ... get '/' => sub { template 'index.tt' };
Request on http://localhost:3000/ gives now the follow error: [1914] core @0.004733> [hit #1]request to / crashed: '/path/to/dancer/myapp/views/' is not a regular file at /usr/local/share/perl/5.10.1/Dancer/Helpers.pm line 39 in /usr/local/share/perl/5.10.1/Dancer/Handler.pm l. 76
Any idea why ?
Thanks Thomas _______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
participants (7)
-
Alexis Sukrieh -
Brian E. Lozier -
Eric Guirbal -
Flavio Poletti -
Puneet Kishor -
sukria
-
Thomas Maier