<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 20, 2014, at 3:41 PM, Levente Uzonyi <<a href="mailto:leves@elte.hu">leves@elte.hu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">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><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><br>html footer: [ html img src: '<a href="http://www.chriscunnington.com/poweredsqueak.png']">http://www.chriscunnington.com/poweredsqueak.png']</a>.<br><br>to something like:<br><br>html footer: [ html img src: (ALPath / 'poweredbysqueak.png') ].<br><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><br>html footer: [ html img src: '/img/foo.jpg' ].<br><br>with a locator like:<br><br>locator at: (ALPath / 'img' / 'foo.jpg') put: (ALFileResource on: FSReference * 'img' / 'foo.jpg')<br><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></div></blockquote><br></div><div>OK, that' sounds straightforward. I'll change the absolute links in Altitude that point to my site to the <a href="http://squeak.org">squeak.org</a> domain and the paths you just described once you've made them available. Here are the files <a href="http://squeak.org">squeak.org</a> uses. </div><div><br></div><div><a href="http://www.chriscunnington.com/squeak.org_files.zip">http://www.chriscunnington.com/squeak.org_files.zip</a></div><div><br></div><div>Chris </div></body></html>