Mailing List Archive: Catalyst: Users

Re: Where to put template files?

Index | Next | Previous | View Threaded

diment at gmail

Jun 7, 2006, 2:02 PM

Post #1 of 13 (2037 views)
Permalink

Re: Where to put template files?

It's a good idea to change the subject of your mail, so that it doesn't get
burried if you're reading the digest. I don't know the answer to your
question, but I'm reposting with a sensible subject for you instead

On 08/06/06, Dr. Jennifer Nussbaum <bg271828 [at] yahoo> wrote:
>
>
>
> You can do something like:
>
>
> SetHandler perl-script
> PerlResponseHandler MyApp
>
> Alias /myapp/static /path/to/myapp/root/static
>
> Order allow,deny
> Allow from all
>
> SetHandler default-handler
>
> Thank you!!!
>
> But one question--where do my templates go? Right now their under, lets
> say, /path/to/myapp/root/. And i dont want to change anything in MyApp.pmso i can
> keep running it with the builtin testing server.
>
> The docs for Catalyst::View::TT talk about adding locations for the
> template root but they dont really say what the default location is. (It
> shows about havng MyApp->config({root => MyApp->path_to('root')}) but right
> now i don't have that and things work fine with the test server.) Where
> should i put it all?
>
> Jen.
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> _______________________________________________
> Catalyst mailing list
> Catalyst [at] lists
> http://lists.rawmode.org/mailman/listinfo/catalyst
>
>
>

mromani at ottotecnica

Jun 7, 2006, 11:38 PM

Post #2 of 13 (1948 views)
Permalink

Re: Where to put template files? [In reply to]

Kieren Diment ha scritto:
> It's a good idea to change the subject of your mail, so that it doesn't
> get burried if you're reading the digest. I don't know the answer to
> your question, but I'm reposting with a sensible subject for you instead
>
> On 08/06/06, *Dr. Jennifer Nussbaum* <bg271828 [at] yahoo
> <mailto:bg271828 [at] yahoo>> wrote:
>
>
>
> You can do something like:
>
>
> SetHandler perl-script
> PerlResponseHandler MyApp
>
> Alias /myapp/static /path/to/myapp/root/static
>
> Order allow,deny
> Allow from all
>
> SetHandler default-handler
>
> Thank you!!!
>
> But one question--where do my templates go? Right now their under,
> lets say, /path/to/myapp/root/. And i dont want to change anything
> in MyApp.pm so i can
> keep running it with the builtin testing server.

If everything is working fine under the test server, then it should Just
Work (tm) under apache. Templates don't have to be moved.

>
> The docs for Catalyst::View::TT talk about adding locations for the
> template root but they dont really say what the default location is.
> (It shows about havng MyApp->config({root =>
> MyApp->path_to('root')}) but right now i don't have that and things
> work fine with the test server.) Where should i put it all?
>
> Jen.
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
> _______________________________________________
> Catalyst mailing list
> Catalyst [at] lists <mailto:Catalyst [at] lists>
> http://lists.rawmode.org/mailman/listinfo/catalyst
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Catalyst mailing list
> Catalyst [at] lists
> http://lists.rawmode.org/mailman/listinfo/catalyst

--
Marcello Romani
Responsabile IT
Ottotecnica s.r.l.
http://www.ottotecnica.com

_______________________________________________
Catalyst mailing list
Catalyst [at] lists
http://lists.rawmode.org/mailman/listinfo/catalyst

jjn1056 at yahoo

Jun 8, 2006, 2:59 AM

Post #3 of 13 (1960 views)
Permalink

Re: Where to put template files? [In reply to]

I'm not sure if you've gotten a good answer for this,
so here is my two cents:

If you just go with the default of not manually
setting the template with $c->stash->{template} = ''
then the TT view will look inside the root directory
(the /root inside your catalyst app, not the OS root)
at a path that is based on your associated catalyst
action.

So if you have a controller called 'test' and an
action inside it called 'hello' you should make a file
called 'hello' inside of the path 'root/test'. That
'hello' file should be your template toolkit template.

If you use a regex or localregex then you use the
subroutine name:

package myapp::Controller::items;

sub item : Regex('/n/n/n/') { ... }

the default path is 'root/items/item'

You can overide the default path in the TT config. I
did that for my first application but decided in the
end it's better to just go with the default and not
make my application 'too much of a individual
snowflake'. Here is how you'd do that if you want to:

package talentspace_portal::View::tt_page;

use strict;
use warnings;

use base 'Catalyst::View::TT';

__PACKAGE__->config(

INCLUDE_PATH => [talentspace_portal->path_to(
'tt_templates' ),],

TEMPLATE_EXTENSION => '.tt',
WRAPPER => 'page_wrapper.tt',
PRE_PROCESS => '_macros/forms.tt',
COMPILE_DIR => '/tmp/template_cache',

);

It's that "INCLUDE_PATH" that is the relevant bit.
That makes the path set to "[myapp_path]/tt_templates"
which is more neat than to throw everything into root.
However if everyone expects to find stuff in root
maybe I'd rather not rock the boat just to make things
look neat to me :)

You might notice that the value of that key is a
reference to an array. You can actually set multiply
paths if you want, although I don't know the potential
performance impact of that. I can see that being
useful if you have several catalyst applications
running as part of the same system and you wanted to
share templates in a global area, as well as having
local templates.

BTW, that "TEMPLATE_EXTENSION" is very useful. It
allows you to add whatever file association you want
to use for your template toolkit templates. If you
have an editor that does color syntax based on the
file extension it could prove useful.

Hope this helps. --john

--- Marcello Romani <mromani [at] ottotecnica> wrote:

> Kieren Diment ha scritto:
> > It's a good idea to change the subject of your
> mail, so that it doesn't
> > get burried if you're reading the digest. I don't
> know the answer to
> > your question, but I'm reposting with a sensible
> subject for you instead
> >
> > On 08/06/06, *Dr. Jennifer Nussbaum*
> <bg271828 [at] yahoo
> > <mailto:bg271828 [at] yahoo>> wrote:
> >
> >
> >
> > You can do something like:
> >
> >
> > SetHandler perl-script
> > PerlResponseHandler MyApp
> >
> > Alias /myapp/static
> /path/to/myapp/root/static
> >
> > Order allow,deny
> > Allow from all
> >
> > SetHandler default-handler
> >
> > Thank you!!!
> >
> > But one question--where do my templates go?
> Right now their under,
> > lets say, /path/to/myapp/root/. And i dont
> want to change anything
> > in MyApp.pm so i can
> > keep running it with the builtin testing
> server.
>
> If everything is working fine under the test server,
> then it should Just
> Work (tm) under apache. Templates don't have to be
> moved.
>
> >
> > The docs for Catalyst::View::TT talk about
> adding locations for the
> > template root but they dont really say what
> the default location is.
> > (It shows about havng MyApp->config({root =>
> > MyApp->path_to('root')}) but right now i don't
> have that and things
> > work fine with the test server.) Where should
> i put it all?
> >
> > Jen.
> >
> >
> __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam
> protection around
> > http://mail.yahoo.com
> >
> >
> >
> _______________________________________________
> > Catalyst mailing list
> > Catalyst [at] lists
> <mailto:Catalyst [at] lists>
> >
> http://lists.rawmode.org/mailman/listinfo/catalyst
> >
> >
> >
> >
> >
>
------------------------------------------------------------------------
> >
> > _______________________________________________
> > Catalyst mailing list
> > Catalyst [at] lists
> > http://lists.rawmode.org/mailman/listinfo/catalyst
>
>
> --
> Marcello Romani
> Responsabile IT
> Ottotecnica s.r.l.
> http://www.ottotecnica.com
>
> _______________________________________________
> Catalyst mailing list
> Catalyst [at] lists
> http://lists.rawmode.org/mailman/listinfo/catalyst
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

_______________________________________________
Catalyst mailing list
Catalyst [at] lists
http://lists.rawmode.org/mailman/listinfo/catalyst

bg271828 at yahoo

Jun 8, 2006, 12:15 PM

Post #4 of 13 (1954 views)
Permalink

Re: Where to put template files? [In reply to]

> On 08/06/06, *Dr. Jennifer Nussbaum*
> > wrote:
>
>
>
> You can do something like:
>
>
> SetHandler perl-script
> PerlResponseHandler MyApp
>
> Alias /myapp/static /path/to/myapp/root/static
>
> Order allow,deny
> Allow from all
>
> SetHandler default-handler
>
> Thank you!!!
>
> But one question--where do my templates go? Right now their under,
> lets say, /path/to/myapp/root/. And i dont want to change anything
> in MyApp.pm so i can
> keep running it with the builtin testing server.

If everything is working fine under the test server, then it should Just
Work (tm) under apache. Templates don't have to be moved.

Thank you for this and thank you to everyone whose responded in detail about setting this up but i think my main question is still out there.

i dont want to change INCLUDE_PATH in Template Toolkit because if i specify a direct path the testserver wont work, right?

And i understand that this will "Just Work" under apache if i leave everything where it is but thats not what im asking. i want to know where to put it if i DO need to move thing. Consider this:

Right now i can create MyApp anywhere, it can be /home/jen/temporary_projects/myapp/lib/MyApp.pm. And then if I run the testserver it will find my templates at /home/jen/temporary_projects/myapp/root/header.tt. But if i run this under apache i DONT want to keep MyApp at /home/jen/temporary_projects, i want to move it to something like /usr/local/web/modules/MyApp.pm where the rest of my webapps are, and apache points to them. But then i cant keep my templates in ~/temporary_projects or they wont be found. BUT if I make something like /usr/local/web/templates/myapp/ and point INCLUDE_PATH to THAT, then the testserver wont find it if im running on the development version in temporary_projects.

im sorry if im not explaining things well but what i really want is way that i can do two things: 1. run a development version with the testserver and run a production version with apache, and 2. do this without changing code between the versions (changing the code to get the production version to point to different directories that is).

is that clearer? Thanks for keeping on reading!!

Jen

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

acid06 at gmail

Jun 8, 2006, 12:34 PM

Post #5 of 13 (1943 views)
Permalink

Re: Where to put template files? [In reply to]

On 6/8/06, Dr. Jennifer Nussbaum <bg271828 [at] yahoo> wrote:
> im sorry if im not explaining things well but what i really want is way that
> i can do two things: 1. run a development version with the testserver and
> run a production version with apache, and 2. do this without changing code
> between the versions (changing the code to get the production version to
> point to different directories that is).

Well, you wouldn't be changing code per se.

You'd be changing configuration files (i.e. myapp.yml) and I think
it's not that unreasonable to have small differences between the
configuration files used with the built-in test server and the ones
used with Apache.

-Nilson Santos F. Jr.

_______________________________________________
Catalyst mailing list
Catalyst [at] lists
http://lists.rawmode.org/mailman/listinfo/catalyst

jjn1056 at yahoo

Jun 8, 2006, 6:29 PM

Post #6 of 13 (1960 views)
Permalink

Re: Where to put template files? [In reply to]

<quote>
i dont want to change INCLUDE_PATH in Template Toolkit
because if i specify a direct path the testserver wont
work, right?
</quote>

Actually Catalyst is pretty smart to help you with
this sort of thing. First of all it almost ways uses
the catalyst application root, not the filesystem
root, so there is no trouble if the development and
production servers use different paths. I have this
issue and I promote to production from the same DVN
tree as is used in development.

I think also there was a comment about using the .yml
file to help with this. As I mentioned it usually
isn't necessary, but it is a great way to consoladate
your configuration. The YAML thing really got me at
first because I was a newb to it and the documentation
was baffling to me. Here's an example from my yml
file where I set some config stuff for a template
toolkit view:

'View::tt_html':
TEMPLATE_EXTENSION: '.tt'
POST_CHOMP: 1
COMPILE_DIR: '/tmp/template_cache'
WRAPPER: '_wrappers/html.tt'
PRE_PROCESS: '_macros/forms.tt'

This is similar to the example I have you before where
I was setting up config in the actual class. I did
that a lot at first.

This is config for a view called
"myapp::View::tt_html" located in the View directory.
As you can see only one of the values is specifying an
absolute path. The rest pick up their root from
catalyst. In development this is
/mnt/hgfs/catalyst/myapp, but in production it's
'/root/catalyst/myapp'.

I know getting used to the yaml syntax can be trouble,
but there is a command line yml compiling you get when
you install yaml which can help you translate perl
structures to yml structures to help get you started.
It's call ysh and you invoke is by typing 'ysh' from
the command prompt (if you've installed YAML, which is
likely true if you are using catalyst!

So the short answer is that you should have no trouble
if your dev and prod use different path prefixes,
assuming everything else is the same regarding the
perl installation and paths, and whatever other
includes you might need.

Hope this helps out, john

--- "Dr. Jennifer Nussbaum" <bg271828 [at] yahoo>
wrote:

>
>
> > On 08/06/06, *Dr. Jennifer Nussbaum*
> > > wrote:
> >
> >
> >
> > You can do something like:
> >
> >
> > SetHandler perl-script
> > PerlResponseHandler MyApp
> >
> > Alias /myapp/static
> /path/to/myapp/root/static
> >
> > Order allow,deny
> > Allow from all
> >
> > SetHandler default-handler
> >
> > Thank you!!!
> >
> > But one question--where do my templates go?
> Right now their under,
> > lets say, /path/to/myapp/root/. And i dont
> want to change anything
> > in MyApp.pm so i can
> > keep running it with the builtin testing
> server.
>
> If everything is working fine under the test server,
> then it should Just
> Work (tm) under apache. Templates don't have to be
> moved.
>
> Thank you for this and thank you to everyone whose
> responded in detail about setting this up but i
> think my main question is still out there.
>
> i dont want to change INCLUDE_PATH in Template
> Toolkit because if i specify a direct path the
> testserver wont work, right?
>
> And i understand that this will "Just Work" under
> apache if i leave everything where it is but thats
> not what im asking. i want to know where to put it
> if i DO need to move thing. Consider this:
>
> Right now i can create MyApp anywhere, it can be
> /home/jen/temporary_projects/myapp/lib/MyApp.pm. And
> then if I run the testserver it will find my
> templates at
> /home/jen/temporary_projects/myapp/root/header.tt.
> But if i run this under apache i DONT want to keep
> MyApp at /home/jen/temporary_projects, i want to
> move it to something like
> /usr/local/web/modules/MyApp.pm where the rest of my
> webapps are, and apache points to them. But then i
> cant keep my templates in ~/temporary_projects or
> they wont be found. BUT if I make something like
> /usr/local/web/templates/myapp/ and point
> INCLUDE_PATH to THAT, then the testserver wont find
> it if im running on the development version in
> temporary_projects.
>
> im sorry if im not explaining things well but what i
> really want is way that i can do two things: 1. run
> a development version with the testserver and run a
> production version with apache, and 2. do this
> without changing code between the versions (changing
> the code to get the production version to point to
> different directories that is).
>
> is that clearer? Thanks for keeping on reading!!
>
> Jen
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam
> protection around
> http://mail.yahoo.com >
_______________________________________________
> Catalyst mailing list
> Catalyst [at] lists
> http://lists.rawmode.org/mailman/listinfo/catalyst
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

_______________________________________________
Catalyst mailing list
Catalyst [at] lists
http://lists.rawmode.org/mailman/listinfo/catalyst

mromani at ottotecnica

Jun 8, 2006, 11:35 PM

Post #7 of 13 (1944 views)
Permalink

Re: [spam] Re: Where to put template files? [In reply to]

Dr. Jennifer Nussbaum ha scritto:
>
>
> > On 08/06/06, *Dr. Jennifer Nussbaum*
> > > wrote:
> >
> >
> >
> > You can do something like:
> >
> >
> > SetHandler perl-script
> > PerlResponseHandler MyApp
> >
> > Alias /myapp/static /path/to/myapp/root/static
> >
> > Order allow,deny
> > Allow from all
> >
> > SetHandler default-handler
> >
> > Thank you!!!
> >
> > But one question--where do my templates go? Right now their under,
> > lets say, /path/to/myapp/root/. And i dont want to change anything
> > in MyApp.pm so i can
> > keep running it with the builtin testing server.
>
> If everything is working fine under the test server, then it should
> Just
> Work (tm) under apache. Templates don't have to be moved.
>
>
> Thank you for this and thank you to everyone whose responded in detail
> about setting this up but i think my main question is still out there.
>
> i dont want to change INCLUDE_PATH in Template Toolkit because if i
> specify a direct path the testserver wont work, right?

IME you don't have to touch that config item even if you move your app
around. Catalyst sets it up so that everything Just Works(tm) wherever
MyApp/ is.

>
> And i understand that this will "Just Work" under apache if i leave
> everything where it is but thats not what im asking. i want to know
> where to put it if i DO need to move thing. Consider this:

Well, just copy MyApp/ in a suitable location and configure apache
accordingly. You don't want code and templates to be in different
places, especially on a production installation, do you ?

>
> Right now i can create MyApp anywhere, it can be
> /home/jen/temporary_projects/myapp/lib/MyApp.pm. And then if I run the
> testserver it will find my templates at
> /home/jen/temporary_projects/myapp/root/header.tt. But if i run this
> under apache i DONT want to keep MyApp at /home/jen/temporary_projects,
> i want to move it to something like /usr/local/web/modules/MyApp.pm

Catalyst applications are structured like perl module distribution. You
don't move MyApp.pm, but the entire MyApp/ directory instead. Since
everything (code, templates, static resources, config files, etc.) is
contained in that dir, and Catalyst knows where it's called from,
there's no need to worry about it not finding templates.

In other words, to move your app from temporary_projects to
/usr/local/web/modules, just cp temporary_projects/MyApp to
/usr/local/web/modules.

To verify that everything Just Works(tm) as expected even in the new
location, try to run it under the test server (i.e. cd
/usr/local/web/modules/MyApp; perl script/myapp_server.pl): if it works
this way, it'll work under apache.

> where the rest of my webapps are, and apache points to them. But then i
> cant keep my templates in ~/temporary_projects or they wont be found.

As I just said, templates are moved together with the application code.

> BUT if I make something like /usr/local/web/templates/myapp/ and point
> INCLUDE_PATH to THAT, then the testserver wont find it if im running on
> the development version in temporary_projects.
>
> im sorry if im not explaining things well but what i really want is way
> that i can do two things: 1. run a development version with the
> testserver and run a production version with apache, and 2. do this
> without changing code between the versions (changing the code to get the
> production version to point to different directories that is).
>
> is that clearer? Thanks for keeping on reading!!
>
> Jen
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Catalyst mailing list
> Catalyst [at] lists
> http://lists.rawmode.org/mailman/listinfo/catalyst

I hope I made it clear enough :-)

Keep asking if needed!

--
Marcello Romani
Responsabile IT
Ottotecnica s.r.l.
http://www.ottotecnica.com

_______________________________________________
Catalyst mailing list
Catalyst [at] lists
http://lists.rawmode.org/mailman/listinfo/catalyst

dbix-class at trout

Jun 9, 2006, 6:58 AM

Post #8 of 13 (1944 views)
Permalink

Re: Where to put template files? [In reply to]

John Napiorkowski wrote:
> I know getting used to the yaml syntax can be trouble,
> but there is a command line yml compiling you get when
> you install yaml which can help you translate perl
> structures to yml structures to help get you started.
> It's call ysh and you invoke is by typing 'ysh' from
> the command prompt (if you've installed YAML, which is
> likely true if you are using catalyst!

YAML drives me batshit. Fortunately ConfigLoader will handle a vast range of
config formats, including JSON and XML. My personal preference is Config::General

<View TT>
INCLUDE_PATH ...
</View>

--
Matt S Trout Offering custom development, consultancy and support
Technical Director contracts for Catalyst, DBIx::Class and BAST. Contact
Shadowcat Systems Ltd. mst (at) shadowcatsystems.co.uk for more information

+ Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +

_______________________________________________
Catalyst mailing list
Catalyst [at] lists
http://lists.rawmode.org/mailman/listinfo/catalyst

A.Ford at ford-mason

Jun 9, 2006, 8:04 AM

Post #9 of 13 (1953 views)
Permalink

Re: Where to put template files? [In reply to]

Matt S Trout wrote:
> John Napiorkowski wrote:
>
>> I know getting used to the yaml syntax can be trouble,
>> but there is a command line yml compiling you get when
>> you install yaml which can help you translate perl
>> structures to yml structures to help get you started.
>> It's call ysh and you invoke is by typing 'ysh' from
>> the command prompt (if you've installed YAML, which is
>> likely true if you are using catalyst!
>>
>
> YAML drives me batshit. Fortunately ConfigLoader will handle a vast range of
> config formats, including JSON and XML. My personal preference is Config::General
>
I totally agree with this. YAML is fine as a serialization format, and
it can be useful that it is (just about) readable, but I find it insane
that it is even considered usable as a configuration file format -- it
is just too easy to break and reinforces the prejudice that perl is just
for hackers. For applications that may need their configurations
tweaking by client's support staff I have generally used Windows-style
.ini files (parsed with Config::IniFiles). I know the format is limited
to groups of keyword/value pairs, but that generally suffices and keeps
things so that they are simple to explain.

Andrew

--
Andrew Ford, Director Pauntley Prints / Ford & Mason Ltd
A.Ford [at] ford-mason South Wing Compton House
pauntley-prints.co.uk Compton Green, Redmarley Tel: +44 1531 829900
ford-mason.co.uk Gloucester GL19 3JB Fax: +44 1531 829901
refcards.com cronolog.org Great Britain Mobile: +44 7785 258278

_______________________________________________
Catalyst mailing list
Catalyst [at] lists
http://lists.rawmode.org/mailman/listinfo/catalyst

moseley at hank

Jun 9, 2006, 8:28 AM

Post #10 of 13 (1950 views)
Permalink

Re: Where to put template files? [In reply to]

On Fri, Jun 09, 2006 at 04:04:09PM +0100, Andrew Ford wrote:
> I totally agree with this. YAML is fine as a serialization format, and
> it can be useful that it is (just about) readable, but I find it insane
> that it is even considered usable as a configuration file format -- it
> is just too easy to break and reinforces the prejudice that perl is just
> for hackers. For applications that may need their configurations
> tweaking by client's support staff I have generally used Windows-style
> .ini files (parsed with Config::IniFiles). I know the format is limited
> to groups of keyword/value pairs, but that generally suffices and keeps
> things so that they are simple to explain.

I put client config options in the database, and application level
config in YAML or sometimes just a perl hash read by do(). If they
can't figure out YAML then they probably shouldn't be in there
tweaking the config in the first place. ;)

--
Bill Moseley
moseley [at] hank

_______________________________________________
Catalyst mailing list
Catalyst [at] lists
http://lists.rawmode.org/mailman/listinfo/catalyst

jjn1056 at yahoo

Jun 9, 2006, 8:32 AM

Post #11 of 13 (1969 views)
Permalink

Re: Where to put template files? [In reply to]

I think my project for tomorrow is to change all my
YAML files to something like this :) --john

--- Matt S Trout <dbix-class [at] trout> wrote:

> John Napiorkowski wrote:
> > I know getting used to the yaml syntax can be
> trouble,
> > but there is a command line yml compiling you get
> when
> > you install yaml which can help you translate perl
> > structures to yml structures to help get you
> started.
> > It's call ysh and you invoke is by typing 'ysh'
> from
> > the command prompt (if you've installed YAML,
> which is
> > likely true if you are using catalyst!
>
> YAML drives me batshit. Fortunately ConfigLoader
> will handle a vast range of
> config formats, including JSON and XML. My personal
> preference is Config::General
>
> <View TT>
> INCLUDE_PATH ...
> </View>
>
> --
> Matt S Trout Offering custom
> development, consultancy and support
> Technical Director contracts for Catalyst,
> DBIx::Class and BAST. Contact
> Shadowcat Systems Ltd. mst (at)
> shadowcatsystems.co.uk for more information
>
> + Help us build a better perl ORM:
> http://dbix-class.shadowcatsystems.co.uk/ +
>
> _______________________________________________
> Catalyst mailing list
> Catalyst [at] lists
> http://lists.rawmode.org/mailman/listinfo/catalyst
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

_______________________________________________
Catalyst mailing list
Catalyst [at] lists
http://lists.rawmode.org/mailman/listinfo/catalyst

dbix-class at trout

Jun 9, 2006, 8:38 AM

Post #12 of 13 (1963 views)
Permalink

Re: Where to put template files? [In reply to]

John Napiorkowski wrote:
> I think my project for tomorrow is to change all my
> YAML files to something like this :) --john

New thread started so we can argue about the One True Config format.

Hey, it's friday afternoon :)

--
Matt S Trout Offering custom development, consultancy and support
Technical Director contracts for Catalyst, DBIx::Class and BAST. Contact
Shadowcat Systems Ltd. mst (at) shadowcatsystems.co.uk for more information

+ Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +

_______________________________________________
Catalyst mailing list
Catalyst [at] lists
http://lists.rawmode.org/mailman/listinfo/catalyst

A.Ford at ford-mason

Jun 9, 2006, 8:54 AM

Post #13 of 13 (1949 views)
Permalink

Re: Where to put template files? [In reply to]

Matt S Trout wrote:
> John Napiorkowski wrote:
>
>> I think my project for tomorrow is to change all my
>> YAML files to something like this :) --john
>>
>
> New thread started so we can argue about the One True Config format.
>
>
No its not about "One True Config Format", but rather about one
goddamnawful format. I actually had a client complain about the YAML
configuration file; they had to change the database username and
password in the file and screwed up the format, hadn't made a backup and
part of their production website was down for several hours until they
contacted me. I changed the application to read a windows .ini file and
they were happy (well they weren't too happy about the time the
application was down).

I don't mind about XML files -- I'm sure the client could have worked
out the pattern -- or other straightforwardly comprehensible formats,
but the clients were totally flumoxed by YAML, and they needed to have
the ability to change some configuration parameters.

To my mind if the users have problems with some aspect of a system then
its a design flaw.

> Hey, it's friday afternoon :)
>
>
Yep.

Andrew

--
Andrew Ford, Director Pauntley Prints / Ford & Mason Ltd
A.Ford [at] ford-mason South Wing Compton House
pauntley-prints.co.uk Compton Green, Redmarley Tel: +44 1531 829900
ford-mason.co.uk Gloucester GL19 3JB Fax: +44 1531 829901
refcards.com cronolog.org Great Britain Mobile: +44 7785 258278

_______________________________________________
Catalyst mailing list
Catalyst [at] lists
http://lists.rawmode.org/mailman/listinfo/catalyst

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads