Em Wednesday 16 January 2008 01:11:10 Lukasz Szybalski escreveu: > Hello, > As I write new apps in turbogears and then upload them to the server, > I am starting to run into problems like which /static content am I > suppose to be using and how?
Each application has its own /static. You can have a more generic one if you want to share things. Also note that TG's /static (such as to load MochiKit) is shared among all applications. > So right now I have 4 turbogears apps working on my server. The first > app uses apache /static/ which proxies to my some port 8080/static/ . > Well now my second app needs to use /static/ and what I did is to move > the new images/css to my first app > /usr/lib/python2.4/site-packages/myfirstapp-1.0-py2.4.egg/myfirstapp/static All apps on the same domain and same path? If not, you answered your doubt: proxy /path1/static to one app, /path2/static to another and so on. Also I wouldn't recommend giving Apache access to your lib directories like you did above. Install the app's static files somewhere else and map it accordingly or put the whole app on another directory. > Isn't there a bettter way to reuse these parts of the turbogears > project? How are you guys doing it? If they are common, make it a module in itself and just import from it. Or put it in a "standard" repository in your webserver path and that's it. -- Jorge Godoy <[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 -~----------~----~----~----~------~----~------~--~---
