Thanks Craig. I know that Alessandro has done a major update on TG2.3 documentation, and I've not looked at it yet. If this isn't in there, I'll work to make sure it gets in there soon.
On Tue, Oct 23, 2012 at 7:50 AM, Craig Small <[email protected]> wrote: > I tried a test deployment of moving my test code onto a webserver using > apache and wsgi. I used the documentation on the website at > http://turbogears.org/2.2/docs/main/Deployment/index.html > > I looked at some other deployed projects and it seems looking at how > they are done, there is some confusion out there. > > The good news is, I got there in the end and the project worked ok > through apache. > > The documentation while correct does need some meat on the bones. I > thought I'd write up some suggestions. > > * A list of the directories and what they do and have would help. I > didn't realise there was /usr/local/pythonenv/myapp and > /usr/local/turbogears/myapp for a litle while > * There needs to be a clear distinction between the two names; the > project and package name; most of the time its the project > name that is used. The documents use myapp which implies the > package name is used instead. > * nick some of the stuff in apache/README especially about how > production.ini is made > * I used git, perhaps some tips around using that would be nice > * Using the egg put my project files in the wrong spot, I may of got > my directories mixed up (see first point) > > None of this makes me think the documentation is terrible, but just some > feedback from an admittedly wsgi newbie. > -- Michael J. Pedersen My Online Resume: http://www.icelus.org/ -- Google+ http://plus.ly/pedersen Google Talk: [email protected] -- Twitter: pedersentg -- 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.
