[Box-Admins] serving files from box4

[Levente Uzonyi]

On Thu, 20 Mar 2014, Chris Cunnington wrote:

> locator at: (ALPath / 'favicon.ico')
> 		put: (ALFileResource on: (FSLocator imageDirectory / 'squeakfavicon.ico') resolve)
>
> This code is in the current squeak.org 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:
>
> html footer: [ html img src: 'http://www.chriscunnington.com/poweredsqueak.png'].
>
> to something like:
>
> html footer: [ html img src: (ALPath / 'poweredbysqueak.png') ].
>
> 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:
>
> html footer: [ html img src: '/img/foo.jpg' ].
>
> with a locator like:
>
> locator at: (ALPath / 'img' / 'foo.jpg') put: (ALFileResource on: FSReference * 'img' / 'foo.jpg')
>
> where nginx sees the token /img/ and sends the request to wherever the static files are served from.

The goal is to let nginx serve the static files, and let the browsers and 
proxies cache them forever.

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:

/static/*/...

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

/static/v1/img/foo.jpg

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.

If you upload the static files to the server, then I'll configure nginx to 
serve them.


Levente

>
>
> Chris
>
>