Serving static files
jason.johnson.081 at gmail.com
Wed Nov 12 06:18:54 MET 2008
This site tells how to do it:
On Tue, Nov 11, 2008 at 5:16 AM, David Zmick <dz0004455 at gmail.com> 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 <rdrvr.biz at gmail.com> 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
>> 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?
>> SmallWiki, Magritte, Pier and Related Tools ...
> David Zmick
> SmallWiki, Magritte, Pier and Related Tools ...
More information about the smallwiki