<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Timothy, <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">still not sure I understand. You want
to deploy files but serve them from the image?</div>
<div class="moz-cite-prefix"> Isn't the whole idea of #deployFiles
not to serve them from the image and use those CPU-Cycles in the
Smalltalk image for something with more value...?</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Joachim</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Am 21.11.18 um 15:50 schrieb
gettimothy:<br>
</div>
<blockquote type="cite"
cite="mid:16736c079ad.d80d1f7036562.1208944003225826659@zoho.com">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<div
style="font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;color:#00000;">
<div>Hi Joachim<br>
</div>
<div><br>
</div>
<div>Thanks for the response. That what I was doing , but its a
big job as I will be loading JQuery-ui, JQuery, Bootstrap,
MaterialDesign, Seaside.... from the apps menu in SeasideDoc.<br>
</div>
<div><br>
</div>
<div>However!!!! I found an acceptable work-around that bypasses
NGINX completely.<br>
</div>
<div><br>
</div>
<div>The base SeasideDoc files are referenced like: </div>
<blockquote style="border: 1px solid rgb(204, 204, 204);
padding: 7px; background-color: rgb(245, 245, 245);">
<div>SeasideDocLibrary baseUrl,'jquery-ui.js' ->'<a
href="http://192.168.1.102/jquery-ui.js" target="_blank"
moz-do-not-send="true">http://192.168.1.102/jquery-ui.js</a>'<br>
</div>
</blockquote>
<div>and are handled via Nginx.<br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>I figured out I could bypass NGINX completely by tacking on
an :8080 to the url...<br>
</div>
<div><br>
</div>
<div>
<blockquote style="border: 1px solid rgb(204, 204, 204);
padding: 7px; background-color: rgb(245, 245, 245);">
<div>(SeasideDocLibrary alternatePort: (SeasideDocLibrary
baseUrl)) ,'bootstrap' --> '<a target="_blank"
href="http://192.168.1.102:8080/bootstrap"
moz-do-not-send="true">http://192.168.1.102:8080/bootstrap</a>'<br>
</div>
</blockquote>
This means the Show/Call stuff for apps will not be in the
cards for the apps, but I think this is an acceptable
tradeoff.<br>
<br>
cheers,<br>
t</div>
<div class="zmail_extra">
<div id="Zm-_Id_-Sgn1">
<div><br>
</div>
<div>---- On Wed, 21 Nov 2018 02:41:07 -0500 <b><a class="moz-txt-link-rfc2396E" href="mailto:jtuchel@objektfabrik.de"><jtuchel@objektfabrik.de></a></b>
wrote ----<br>
</div>
</div>
<div><br>
</div>
<blockquote style="border-left: 1px solid #cccccc;
padding-left: 6px; margin:0 0 0 5px">
<div>
<div>Timothy,<br>
</div>
<div><br>
</div>
<div>not sure I am answering the right question here, but
the idea of deploying files to the file system in a
production system is that requests coming in for files
never reach your smalltalk image, thus keeping load off
your image.<br>
</div>
<div><br>
</div>
<div>So what is needed is a definition for nginx that
"catches" requests to /files/ and redirect them to files
onyour filesystem, namely the path you deployed your
files to.<br>
</div>
<div><br>
</div>
<div>I am using Apache, so I cannot say what exactly needs
to be done in nginx, <br>
</div>
<div><br>
</div>
<div>Here's what's in my apache conf for this purpose:<br>
</div>
<div><br>
</div>
<div> <span> Alias /files /var/www/app.kontolino<br>
ProxyPass /files !<br>
<br>
Alias /favicon.ico
/var/www/app.kontolino/OfBuchhaltungFileLibrary/favicon.ico<br>
ProxyPass /favicon.ico !<br>
<br>
Alias /robots.txt
/var/www/app.kontolino/OfBuchhaltungFileLibrary/robots.txt<br>
ProxyPass /robots.txt !</span></div>
<div><br>
</div>
<div>So all you need to do is to transpile this for nginx
;-)<br>
</div>
<div><br>
</div>
<div>HTH<br>
</div>
<div><br>
</div>
<div>Joachim<br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Am 21.11.18 um 08:32 schrieb gettimothy:<br>
</div>
<div><br>
</div>
<p><br>
</p>
<div>_______________________________________________<br>
</div>
<div>seaside mailing list<br>
</div>
<div><a target="_blank"
href="mailto:seaside@lists.squeakfoundation.org"
moz-do-not-send="true">seaside@lists.squeakfoundation.org</a><br>
</div>
<div><a target="_blank"
href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside"
moz-do-not-send="true">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</div>
</div>
<blockquote>
<div style="font-size: 10pt; font-family: Verdana, Arial,
Helvetica, sans-serif">
<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
href="http://menmachinesmaterials.com/SeasideDoc"
target="_blank" moz-do-not-send="true">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...<br>
</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<br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div><br>
</div>
<div><br>
</div>
<pre>_______________________________________________
seaside mailing list
<a target="_blank" href="mailto:seaside@lists.squeakfoundation.org" moz-do-not-send="true">seaside@lists.squeakfoundation.org</a>
<a target="_blank" href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" moz-do-not-send="true">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a>
</pre>
</blockquote>
</blockquote>
</div>
<div><br>
</div>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
seaside mailing list
<a class="moz-txt-link-abbreviated" href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a>
<a class="moz-txt-link-freetext" href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>