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.
--
Craig Small VK2XLZ http://enc.com.au/ csmall at : enc.com.au
Debian GNU/Linux http://www.debian.org/ csmall at : debian.org
GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5
--
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.
