On 1/31/07, jemminger <[EMAIL PROTECTED]> wrote: > > > using TG 1.0 on windows > > in projectname/projectname/config, i have three environment config > files: > dev.cfg > staging.cfg > prod.cfg > > however, when i start the server e.g. "start-projectname.py dev.cfg", > it doesn't matter what i specify as the config file, it always chooses > the next "higher" environment up from dev... i.e. if all three > environment cfg files are present, no matter what i specify as the > config file it will always start in staging mode. if i move the > staging file away, it will start in production mode. the only way to > have it start in dev mode is to have dev.cfg be the only environment > file present in the config dir.
take a look of what start_project does, it's internal logic is what's making you fail. It is coded based on the assumption that you only have dev/prod.cfg but you can edit it to work as you wish. as long as update_config is call TG is happy if it matters, this project was created on TG 0.9.4 or so, though i > did try to replace the relevant bits in the start-projectname.py file > with code created by TG1.0 quickstart, and got the same results. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
