12 Nov
2008
12 Nov
'08
6:19 a.m.
Tells how to do what you want I mean, not how to set up apache.
On Wed, Nov 12, 2008 at 6:18 AM, Jason Johnson
<jason.johnson.081(a)gmail.com> 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 <dz0004455(a)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(a)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
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