"TurboGears requires autoreload.package to be set. It can be an empty
value, which will use CherryPy's default behavior which is to check
every module. Setting an actual package makes the check much faster."

I am using my start script followed by -c config/prod.cfg.

prod.cfg *does* have the autoreload.package set. I've tried it with
the autoreload turned on, as well. So I can't think of what else to
try....

Anybody know something about this issue?

Thanks

Chris

(tgenv)andre...@bananabread.net [~/tgenv/lib/python2.4/site-packages/
pit1-1.0-py2.4.egg]# cat config/prod.cfg
[global]

# pit1/config/app.cfg

# DATABASE

sqlobject.dburi="mysql://andrewbn_tgapp:XXXXPASSXXX@localhost:3306/
andrewbn_PitMusician"

# Auto-Reload after code modification
#autoreload.on = True
# SERVER

server.environment="production"
autoreload.package="pit1"

# Sets the number of threads the server uses
# server.thread_pool = 1

# if this is part of a larger site, you can set the path
# to the TurboGears instance here
# server.webpath=""

# LOGGING
# Logging configuration generally follows the style of the standard
# Python logging module configuration. Note that when specifying
# log format messages, you need to use *() for formatting variables.
# Deployment independent log configuration is in pit1/config/log.cfg
[logging]

[[handlers]]

[[[access_out]]]
# set the filename as the first argument below
args="('server.log',)"
class='FileHandler'
level='INFO'
formatter='message_only'

[[loggers]]
[[[pit1]]]
level='ERROR'
qualname='pit1'
handlers=['error_out']

[[[access]]]
level='INFO'
qualname='turbogears.access'
handlers=['access_out']
propagate=0

No "-c" here.

Chris