<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;color:#00000;'><div>After you deploy the files, does Seaside have a "pass thru" to access those files automatically? or do I have to build one by hand?<br></div><div><br></div><div>Here is the background/motivation.<br></div><div><br></div><div>At <a target="_blank" href="http://menmachinesmaterials.com/SeasideDoc">http://menmachinesmaterials.com/SeasideDoc</a> on left menu, under "apps" you will see that the css/javascript access for 'Zurb Foundation' works and neither work for the Twitter Bootstrap or Jquery apps.<br></div><div><br></div><div>The reason is that I use NGinx locations to tell where to look for resources.<br></div><div><br></div><div>My SeasideDoc and Zurb File ibraries all access their files relative to the nginx defintions. So, 'ZurbExamplesLibrary foundation.css' will resolve to the correct path for Nginx to handle.<br></div><div><br></div><div>The TBS and JQuery FileLibraries are 'self contained' and the css and js is not delivered via Nginx.<br></div><div><br></div><div>I am in the process of creating an additional library for TBS that uses my convention...but...</div><div><br></div><div>I just discovered the "deployFiles' method and it does do a nice dump of the files I need...but then what?<br></div><div><br></div><div>Does Seaside standard dev practice include "switching to another library" that automatically routes to those urls that I am missing? <br></div><div><br></div><div>thx in advance.<br></div><div><br></div><div>t</div><div><br></div><div><br></div><div><br></div></div><br></body></html>