Todd Blanchard schrieb:
On Jan 5, 2010, at 1:16 AM, Diez B. Roggisch wrote:
Todd Blanchard schrieb:
I followed the directions of this:
http://toscawidgets.org/documentation/ToscaWidgets/deploy.html#configuring-your-web-server
which purports to explain how to run a script that gathers all the tw static
resources and places them in a directory.
It sort of works - but only for tw.core resources. I also have tw.dojo
installed and the resources for that framework are not extracted and copied.
This has my production server dying horribly. The documentation is pretty quiet on what
the "build" directory is actually for.
What build directory?
The one at myproject/build that is created by running 'python setup.py deploy'
Never used that. No idea what it does.
Anyhow - any hints for how to extract the tw.dojo resources for static
deployment would be most welcome.
tw.dojo tries something clever to allow deliverance of specific
versions. To do so, it overrides JSLink & CSSLink in ways that seem to
break the resource collection.
So if I just go to site-packages and nuke the tw.dojo-0.9.8.1-py2.6.egg
directory it will go away and I can get back to using admin? I've tried that
and I cannot get admin to run in a mod_wsgi environment. It dies horribly with
some kind of resource error - even after nuking tw.dojo.
I've switched from crystal balls to Ouija Boards, and have difficulties
with the adaption. All it told me was "need stacktraces, logentries,
sourcecode". Whatever that's supposed to mean.
Diez
--
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.
