I'm not going to address the points individually. I've still got a bigger email to write that will be on its way within the next 30 minutes.
I will say this: Your points are in the planning to be addressed. In fact, I've even done some prototypes for the docs that do pretty much what you've suggested. Once we complete our migration to sf.net, I'll bring them back out for debate. On Sat, Feb 5, 2011 at 9:04 AM, bvdb <[email protected]> wrote: > On Feb 1, 6:22 pm, Lukasz Szybalski <[email protected]> wrote: >> Since I wrote the original modwsgideploy script I should defend it >> here.. >> >> 1. The location /usr/local/turbogears is used as a reference, you can >> place your project anywhere you want .. >> .. "myapp" is again one of these prefillers, that I think >> gets replaced by your project name. > > For a new user it is not always possible to tell which names are > examples that he is supposed to replace with his OR what is a term > that needs to be there in order for other steps to work. > >> What kind of "organization _inside_ >> virtual environments" do you mean? > > There are "virtual environments", "projects" and "apps" as far as I > understood. How do these fit together? Is it always neccessary to use > a virtual env (no)? > Before using these notions there should be one paragraph or page, for > example "architecture", that explains these structures and their > dependencies. > And there should be a (shorter) paragraph "What you really need to get > started." > >> The whole purpose of the initial development was to get you the >> "settings" , update the paths and you are good to go. I guess I can >> take it to next level and also update the paths for you. > > And for every other TG newbie. > But actually I'd rather propose to leave modwsgideploy away > completely: > - I had some fuss with installing the script at all ("'NoneType' > object has no attribute 'rfind'") > - The script adds another level of complication that is not > neccessary. > I mentioned the django approach before: One page with all the steps to > get going - and a link at the very end if someone really craves to > read more: > http://docs.djangoproject.com/en/dev/howto/deployment/modwsgi/ > > Turbogears I propose should do it the same way: Explain the basic > steps that work out of the box - instead of linking to various > overlapping explanations here and there, including modwsgideploy. > > -- > 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. > > -- Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] -- 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.
