Thanks, all. Some thoughts on the suggestions. The apps are all dynamic apps hitting an mssql database through SqlAlchemy so I can't just use plain old Apache or any other server. The apps are currently implemented as Perl cgi scripts and the only real commonality between them is the styling and some javascript bits. I'm looking at switching to Pylons because I like the scalability and flexibility of it.
I've been down the symlink path and it just feels like a kludge to me to do it that way. I was hoping maybe I had missed something in the documentation that would allow for a cleaner method of importing these types of modules. I actually did try the url_for method, but then the whole issue of what context is currently running comes up with regard to where the files are. Thanks again for the quick responses and giving me a couple of other ideas to pursue in more depth. I'll keep poking around and maybe some inspiration will strike. - Eric On May 19, 1:13 am, "Shannon -jj Behrens" <[EMAIL PROTECTED]> wrote: > On 5/18/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > I have been working with Pylons and have developed some standalone > > applications that are part of a larger site. I'm trying to find out > > what the best way is to reference common css/javascript files across > > all of the apps. Here is the setup in a nutshell: > > > I have a home page and 3 sub-apps that all use the same css layout > > files and some of the same script files. I have so far been putting > > these files in each application's public directory. Bad idea, I know, > > but I was in a hurry. Anyway, the 3 apps really are separate apps and > > I therefore don't really want to put all of them in the same project. > > I currently use paste#urlmap to call out to each separate app. > > > Just wondering if anyone has tried to do something similar and found a > > good way to share some of these files across multiple apps. > > I have a project called "lookandfeel" that defines the common look and > feel for all the other Web applications. In each of the other > applications, in their websetup.py, it calls some setup function from > lookandfeel that creates symlinks. I use one symlink for the public > directory, and one symlink for the templates directory. Later, when I > install the apps, I can run "paster setup-app myapp", and it'll create > the symlinks. There's only one gotcha--make sure you create the eggs > from a clean checkout. Otherwise, the egg creation process will > follow the symlinks, which isn't what you want. > > Happy Hacking! > -jj > > --http://jjinux.blogspot.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
