Deployment Documentation

[Craig Small]

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

[Michael Pedersen]

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.

Michael J. Pedersen

My Online Resume: http://www.icelus.org/ -- Google+ http://plus.ly/pedersen

Google Talk: m.ped...@icelus.org -- Twitter: pedersentg

[Alessandro Molina]

I agree that the deploy documentation was confusing.

So I ended up rewriting it from scratch, I tried to make it cleaner and easy to copy/paste: https://turbogears-dev.readthedocs.org/en/workshop/cookbook/deploy/mod_wsgi.html

I still need to add documentation for deploy behind something different from mod_wsgi, some kind of proxied server, which is probably going to be mozilla circus + chaussette as it is showing to be a really simple and reliable solution which supports many different backends.

--
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to turbo...@googlegroups.com.
To unsubscribe from this group, send email to turbogears+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.

[Werner]

Alessandro,

On 07/01/2013 13:30, Alessandro Molina wrote:
> I agree that the deploy documentation was confusing.
> So I ended up rewriting it from scratch, I tried to make it cleaner
> and easy to copy/paste:
> https://turbogears-dev.readthedocs.org/en/workshop/cookbook/deploy/mod_wsgi.html

I am really amazed about the amount of work your are getting done in the
TG area. Not yet an active user of it but following it for some time
now and it is one of my New Years resolutions to start working on a TG
application.

>
> I still need to add documentation for deploy behind something
> different from mod_wsgi, some kind of proxied server, which is
> probably going to be mozilla circus + chaussette as it is showing to
> be a really simple and reliable solution which supports many different
> backends.

For a novice like me it would be really great if some "overview" of
deployment options could be given (pros and cons, maybe a rating of
which is more often used then others), or even just some links on good
blogs talking about how to select one over the other.

Werner