Serving static files

> if you run apache on your own local computer it really isnt much of a
> hassle, then, once you get it running, you don't have to mess with it later,
> and you wont have any trouble switching from your dev. environment to your
> deployment environment.  I would use apache :)
>
> On Tue, Nov 11, 2008 at 8:26 PM, David <[hidden email]> wrote:
>>
>> OK, I know that this question (in various forms) has been asked many times
>> and I've seen all the discussions that google would show me but I still
>> don't know how to get what I want.
>> What I want is to be able to serve static files from seaside (or pier or
>> Comanche or whatever) when I am *developing*.  When I push the site to
>> production, I will be using Apache to serve the static files.  But while I
>> am developing, it would be nice not to have to run Apace and just run
>> Squeak.
>> I have seen the instructions to make Comanche serve static files (e.g. in
>> Brian Chapados' Pier Design Tutorial) and that does work.  My problem is
>> that I have set setName, defaultName and ServerPath so that seaside/pier is
>> *not* in the url.  But I don't know how to get Comanche to serve static
>> files with those changes.
>> Can anyone help?
>> Thanks,
>> David
>>
>> _______________________________________________
>> SmallWiki, Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
>
>
> --
> David Zmick
> /dz0004455\
> http://dz0004455.googlepages.com
> http://dz0004455.blogspot.com
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

> This site tells how to do it:
> http://www.shaffer-consulting.com/david/Seaside/GettingSoftware/index.html
>
>
> On Tue, Nov 11, 2008 at 5:16 AM, David Zmick <[hidden email]> wrote:
>> if you run apache on your own local computer it really isnt much of a
>> hassle, then, once you get it running, you don't have to mess with it later,
>> and you wont have any trouble switching from your dev. environment to your
>> deployment environment.  I would use apache :)
>>
>> On Tue, Nov 11, 2008 at 8:26 PM, David <[hidden email]> wrote:
>>>
>>> OK, I know that this question (in various forms) has been asked many times
>>> and I've seen all the discussions that google would show me but I still
>>> don't know how to get what I want.
>>> What I want is to be able to serve static files from seaside (or pier or
>>> Comanche or whatever) when I am *developing*.  When I push the site to
>>> production, I will be using Apache to serve the static files.  But while I
>>> am developing, it would be nice not to have to run Apace and just run
>>> Squeak.
>>> I have seen the instructions to make Comanche serve static files (e.g. in
>>> Brian Chapados' Pier Design Tutorial) and that does work.  My problem is
>>> that I have set setName, defaultName and ServerPath so that seaside/pier is
>>> *not* in the url.  But I don't know how to get Comanche to serve static
>>> files with those changes.
>>> Can anyone help?
>>> Thanks,
>>> David
>>>
>>> _______________________________________________
>>> SmallWiki, Magritte, Pier and Related Tools ...
>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>>
>>
>> --
>> David Zmick
>> /dz0004455\
>> http://dz0004455.googlepages.com
>> http://dz0004455.blogspot.com
>>
>>
>> _______________________________________________
>> SmallWiki, Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>

> This site tells how to do it:
> http://www.shaffer-consulting.com/david/Seaside/GettingSoftware/index.html
>
>
> On Tue, Nov 11, 2008 at 5:16 AM, David Zmick <[hidden email]>  
> wrote:
>> if you run apache on your own local computer it really isnt much of a
>> hassle, then, once you get it running, you don't have to mess with  
>> it later,
>> and you wont have any trouble switching from your dev. environment  
>> to your
>> deployment environment.  I would use apache :)
>>
>> On Tue, Nov 11, 2008 at 8:26 PM, David <[hidden email]> wrote:
>>>
>>> OK, I know that this question (in various forms) has been asked  
>>> many times
>>> and I've seen all the discussions that google would show me but I  
>>> still
>>> don't know how to get what I want.
>>> What I want is to be able to serve static files from seaside (or  
>>> pier or
>>> Comanche or whatever) when I am *developing*.  When I push the  
>>> site to
>>> production, I will be using Apache to serve the static files.  But  
>>> while I
>>> am developing, it would be nice not to have to run Apace and just  
>>> run
>>> Squeak.
>>> I have seen the instructions to make Comanche serve static files  
>>> (e.g. in
>>> Brian Chapados' Pier Design Tutorial) and that does work.  My  
>>> problem is
>>> that I have set setName, defaultName and ServerPath so that  
>>> seaside/pier is
>>> *not* in the url.  But I don't know how to get Comanche to serve  
>>> static
>>> files with those changes.
>>> Can anyone help?
>>> Thanks,
>>> David
>>>
>>> _______________________________________________
>>> SmallWiki, Magritte, Pier and Related Tools ...
>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>>
>>
>> --
>> David Zmick
>> /dz0004455\
>> http://dz0004455.googlepages.com
>> http://dz0004455.blogspot.com
>>
>>
>> _______________________________________________
>> SmallWiki, Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

> On Nov 11, 2008, at 10:18 PM, Jason Johnson wrote:
>
>> This site tells how to do it:
>> http://www.shaffer-consulting.com/david/Seaside/GettingSoftware/index.html
>>
>>
>> On Tue, Nov 11, 2008 at 5:16 AM, David Zmick <[hidden email]>
>> wrote:
>>> if you run apache on your own local computer it really isnt much of a
>>> hassle, then, once you get it running, you don't have to mess with
>>> it later,
>>> and you wont have any trouble switching from your dev. environment
>>> to your
>>> deployment environment.  I would use apache :)
>>>
>>> On Tue, Nov 11, 2008 at 8:26 PM, David <[hidden email]> wrote:
>>>>
>>>> OK, I know that this question (in various forms) has been asked
>>>> many times
>>>> and I've seen all the discussions that google would show me but I
>>>> still
>>>> don't know how to get what I want.
>>>> What I want is to be able to serve static files from seaside (or
>>>> pier or
>>>> Comanche or whatever) when I am *developing*.  When I push the
>>>> site to
>>>> production, I will be using Apache to serve the static files.  But
>>>> while I
>>>> am developing, it would be nice not to have to run Apace and just
>>>> run
>>>> Squeak.
>>>> I have seen the instructions to make Comanche serve static files
>>>> (e.g. in
>>>> Brian Chapados' Pier Design Tutorial) and that does work.  My
>>>> problem is
>>>> that I have set setName, defaultName and ServerPath so that
>>>> seaside/pier is
>>>> *not* in the url.  But I don't know how to get Comanche to serve
>>>> static
>>>> files with those changes.
>>>> Can anyone help?
>>>> Thanks,
>>>> David
>>>>
>>>> _______________________________________________
>>>> SmallWiki, Magritte, Pier and Related Tools ...
>>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>>
>>>
>>>
>>> --
>>> David Zmick
>>> /dz0004455\
>>> http://dz0004455.googlepages.com
>>> http://dz0004455.blogspot.com
>>>
>>>
>>> _______________________________________________
>>> SmallWiki, Magritte, Pier and Related Tools ...
>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>>
>>
>> _______________________________________________
>> SmallWiki, Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

> On Wed, Nov 12, 2008 at 4:46 PM, David Farber <[hidden email]>  
> wrote:
>> Thanks Jason.  I've already seen these instructions.  The problem is
>> that they don't work if you are running pier from / instead of /
>> seaside/pier.
>
> Did you try installing pier at the root of Kom ? (i.e. I guess
> something like the ma alias: line, but with / instead of /seaside, and
> pier selected as the default application in the seaside dispatcher ?
>
> I don't know for sure that it should work, maybe having an application
> at the root of Kom conflicts with serving files, but it's worth a try…

> On Wed, Nov 12, 2008 at 4:46 PM, David Farber <[hidden email]>  
> wrote:
>> Thanks Jason.  I've already seen these instructions.  The problem is
>> that they don't work if you are running pier from / instead of /
>> seaside/pier.
>>
>> David
>
> Ok, so you set the first MA module (or whatever it's called) to / and
> pier?  Then you set something like   /images to static service?  I
> would expect that to work because I think I have the opposite (/ is
> static, /pier is pier) and it works.  But I would have to check, maybe
> if you set anything to / then nothing else works?  I think the author
> of Komm is on the list.

>
> Here is what I did:
>
> | ma seaside |
>     seaside := WAKom default.
>     ma := ModuleAssembly core.
>     ma serverRoot: (FileDirectory default directoryNamed: 'static')
> fullName.
>     ma alias: '/' to: [ma addPlug: [:request | seaside process:
>   request]].
>     ma documentRoot: (FileDirectory default directoryNamed: 'static')
> fullName.
>     ma serveFiles.
>     (HttpService startOn: 8080 named: 'httpd') plug: ma rootModule
>
> This serves static files and serves the root pier page (i.e localhost:
> 8080/), but I get Not Found for any interior pier pages (i.e.
> localhost:8080/blog).
>
> David

> On Wed, Nov 12, 2008 at 9:42 PM, David Farber <[hidden email]> wrote:
>  
>> Here is what I did:
>>
>> | ma seaside |
>>     seaside := WAKom default.
>>     ma := ModuleAssembly core.
>>     ma serverRoot: (FileDirectory default directoryNamed: 'static')
>> fullName.
>>     ma alias: '/' to: [ma addPlug: [:request | seaside process:
>>   request]].
>>     ma documentRoot: (FileDirectory default directoryNamed: 'static')
>> fullName.
>>     ma serveFiles.
>>     (HttpService startOn: 8080 named: 'httpd') plug: ma rootModule
>>
>> This serves static files and serves the root pier page (i.e localhost:
>> 8080/), but I get Not Found for any interior pier pages (i.e.
>> localhost:8080/blog).
>>
>> David
>>    
>
> I'm not sure, but I think you would need another alias for the static
> folder.  Because normally (at least in other servers, which Komm seems
> to be based loosely on) DocumentRoot is what / will point to, but
> since you have used an alias to point that somewhere else I think you
> would need another alias (e.g. /images) to point to the file system.
> Also, do you have an actual directory called "static" somewhere on the
> filesystem?
>
>  

> On Wed, Nov 12, 2008 at 9:42 PM, David Farber <[hidden email]>  
> wrote:
>>
>> Here is what I did:
>>
>> | ma seaside |
>>    seaside := WAKom default.
>>    ma := ModuleAssembly core.
>>    ma serverRoot: (FileDirectory default directoryNamed: 'static')
>> fullName.
>>    ma alias: '/' to: [ma addPlug: [:request | seaside process:
>>  request]].
>>    ma documentRoot: (FileDirectory default directoryNamed: 'static')
>> fullName.
>>    ma serveFiles.
>>    (HttpService startOn: 8080 named: 'httpd') plug: ma rootModule
>>
>> This serves static files and serves the root pier page (i.e  
>> localhost:
>> 8080/), but I get Not Found for any interior pier pages (i.e.
>> localhost:8080/blog).
>>
>> David
>
> I'm not sure, but I think you would need another alias for the static
> folder.  Because normally (at least in other servers, which Komm seems
> to be based loosely on) DocumentRoot is what / will point to, but
> since you have used an alias to point that somewhere else I think you
> would need another alias (e.g. /images) to point to the file system.
> Also, do you have an actual directory called "static" somewhere on the
> filesystem?