<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Mar 28, 2014, at 11:50 PM, Levente Uzonyi <<a href="mailto:leves@elte.hu">leves@elte.hu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Thu, 20 Mar 2014, Levente Uzonyi wrote:<br><br><blockquote type="cite">On Thu, 20 Mar 2014, Chris Cunnington wrote:<br><br><blockquote type="cite">locator at: (ALPath / 'favicon.ico')<br><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>put: (ALFileResource on: (FSLocator imageDirectory / 'squeakfavicon.ico') resolve)<br>This code is in the current <a href="http://squeak.org">squeak.org</a> image for the favicon, which is a file in the imageDirectory. The simplest thing is for Altitude to be fed a path to wherever Levente wants to put the files for the homepage. The files currently served from my webpage could then be dropped into that directory. Then I can change the absolute references to my site to the disk from:<br>html footer: [ html img src: '<a href="http://www.chriscunnington.com/poweredsqueak.png']">http://www.chriscunnington.com/poweredsqueak.png']</a>.<br>to something like:<br>html footer: [ html img src: (ALPath / 'poweredbysqueak.png') ].<br>That is if the image will handle it's own files. If we are separating static and dynamic requests in nginx for speed and such, then I think I need to change the links to something in Altitude like:<br>html footer: [ html img src: '/img/foo.jpg' ].<br>with a locator like:<br>locator at: (ALPath / 'img' / 'foo.jpg') put: (ALFileResource on: FSReference * 'img' / 'foo.jpg')<br>where nginx sees the token /img/ and sends the request to wherever the static files are served from.<br></blockquote><br>The goal is to let nginx serve the static files, and let the browsers and proxies cache them forever.<br><br>I wanted to use a separate subdomain (or a set of subdomains) for the static files, but it's easier for now to use a path prefix with the following pattern:<br><br>/static/*/...<br><br>Where * is the version label - a sequence of alphanumeric characters, and ... is the actual path to the resource. For example for /img/foo.jpg the actual path is<br><br>/static/v1/img/foo.jpg<br><br>If there's a new version of the resource with the same name, then all you have to do is to replace v1 with v2, then v3, etc.<br><br>If you upload the static files to the server, then I'll configure nginx to serve them.<br></blockquote><br>More than a week has passed since my mail, so I decided to fetch the files myself. </blockquote><div><br></div><div><a href="http://lists.squeakfoundation.org/pipermail/box-admins/2014-March/001823.html">http://lists.squeakfoundation.org/pipermail/box-admins/2014-March/001823.html</a></div><br><blockquote type="cite">I extracted the names of the static files from the source code, and downloaded them to the server to the /var/www/<a href="http://www.squeak.org">www.squeak.org</a> directory. I've configured nginx to serve these files as I described before. Please check if all of them are there.<br></blockquote><div><br></div><div>I'll do so. </div><br><blockquote type="cite"><br>The next step is to change the source code in the image to use these files. </blockquote><div><br></div><div>I'll add it to the <a href="http://squeak.org">squeak.org</a> issues list, which is on public display on the webteam list. I think I've posted it five times so far. </div><br><blockquote type="cite">I saw that the css and js files are not minified, so that's another thing to do.</blockquote><div><br></div>On the list. </div><div><br><blockquote type="cite"> I also think that the source code of the web site should be versionned by MC, and probably stored on <a href="http://source.squeak.org">source.squeak.org</a> to let others modify it.<br></blockquote><div><br></div><div>Added to the list. </div><br><blockquote type="cite"><br>The image serving the <a href="http://www.squeak.org">www.squeak.org</a> site is constantly using ~50%</blockquote><blockquote type="cite">CPU for some reason (even when it's not serving any requests). </blockquote><div><br></div><div>How do you know it's not serving any requests? You're looking at top and the logs simultaneously? </div><br><blockquote type="cite">It's also being ran by root, which is really bad from security POV.</blockquote><div><br></div>It's on the list. </div><div><br></div><div>Chris <br><br><blockquote type="cite">Levente<br><br><blockquote type="cite"><br><br>Levente<br><br><blockquote type="cite">Chris<br></blockquote><br></blockquote></blockquote></div><br></body></html>