On 2/9/06, Scott Kirkwood <[EMAIL PROTECTED]> wrote:
>
> Executive Summary: After running tg_admin quickstart...
> * Add tgheader.png to the static/images folder
> * Use <img src="${std.url('static/images/tgheader.png')" ...> in the
> sample template
> * Use a CSS file and link to it too.
>
> So here's my experience:
> The first thing I wanted to do is to put my image in the template. I
> noticed that the quickstart sample image points directly to the
> turbogears.org site.
> I noticed the images folder and put an image there and then tried to
> link to that, but it didn't work. I quickly discovered that it appears
> that making changes to the master.kid template requires that I restart
> the turbogears' processes. So the turnaround time was a bit longer
> than I would have liked to try out different methods.
> In the end it appeared that the .cfg file was misconfigured (probably
> my fault) and the staticFilter.dir was pointing to a folder that
> doesn't exist (I wrote /home/bla/webapps/tg/static instead of
> /home/bla/webapps/tg/tg/static).
> Now things are working better.
> So here are my issues:
> * I think that the sample image should be installed locally and point
> to the local version.
I agree there.
> * I think it should point to a simple (or empty) css file as well.
In that case an empty.
> * I feel having prod.cfg and dev.cfg is somewhat error prone. I wasn't
> sure which one it used by default and was annoyed that I had to write
> information twice. It would be nice to have a common.cfg and dev.cfg
> or prod.cfg could override some values.
Turbogears 0.9 have an common config file which gets read no matter if
you use dev or prod (or some other configfile).l
>
>
--
cheers
elvelind grandin
