>> How about some Fink-based instructions for use under Mac OS X/ In
>> fact, why not release the whole thing under Fink?
Hmm. Actually with the advent of 10.2, Fink isn't reall neaded for
PyCS/PyDS, since Python 2.2 is already included with OS X. And so we
only need packages to install the stuff that is installed after Python.
I started with a .pkg installer for PyDS for OS X, but that produced a
24 MB monster, so I dropped that idea. I now switched my machine at
home to OS X 10.2, so I think I will switch to using the builtin python
some time in the future and reevaluate that area.
fink installations should be able to use most of the debian
infrastructure that's in PyDS, and since PyCS needs the same things, it
should be possible to share most packages (only the pycs*.deb and
pyds*.deb are different, all other packages are identical), so if one
is willing to do that, go ahead. I did no fink packages up to now and
don't think I will do some, at least not before I have native OS X
Actually installing stuff with OS X got much simpler with 10.2, it's
mostly python setup.py install now. Only problems left are metakit,
where I still have to send up some build process patches upstream and
PIL, where you need an installed libjpeg development library.
That would be cool, although I don't have a mac, so it would be rather
hard for me ;)
Georg Bauer uses one most of the time, I think, so you might want to
ask him. I'll forward this message to the dev mailing list - let's
see what he has to say.
On Sun, Mar 02, 2003 at 08:39:12PM -0600, Alan Sill wrote:
> How about some Fink-based instructions for use under Mac OS X/ In
> fact, why not release the whole thing under Fink?
> On Friday, February 28, 2003, at 06:27 AM, Phillip Pearson wrote:
> >On Thu, Feb 27, 2003 at 05:47:33AM -0600, Alan Sill wrote:
> >>What sort of security can I use (I know, that's not the idea but ...
> >>;-/ ) to authenticate users and/or limit postings to originate from
> >>certain domains, etc.? The university and lab are pretty paranoid
> >>about this sort of thing, even though everything we do is
> >>public-domain, non-classified, non-military etc.
> >Hmm ... if you run it behind an Apache server, and firewall off port
> >5445, you can use Apache access controls to limit access by IP.
> >PyCS's authentication module lets you restrict access to certain blogs
> >by login name -- I think there are some notes on how it works in
> >(Set the default user to have no access, and then you can create
> >logins, etc...)
> >>Also, I notice you dn't seem to use a backing database (at least I
> >>can't recall being asked to set one up). Your public site must
> >>generate a lot of traffic -- how do you keep that straight?
> >It doesn't generate all that much, actually ;)
> >The data is stored in a MetaKit database, and people's blogs are
> >stored as static HTML in the /var/lib/pycs/www/users/*
> >directories... so it's pretty quick. The updates page doesn't seem as
> >fast as it could be, and I have my doubts about some of the hit count
> >functions, but I'm not having any trouble. You'll probably see more
> >load in your lab than I do on my site, but I really doubt you'll faze
> >the server.
> >(I think it should be able to serve at least 50 hits/second when
> >showing blogs etc, and maybe handle 10-50 writes a second. So until
> >you've got 1000-10000 users, you shouldn't have any trouble!)