[webdev] Re: evolution

["John Alexander" <wicjra0@xxxxxxxxxxx>]

Generating the key, certificate, and signing the certificate amount to one
command line entry and answering a bunch of question from the script. It's
perfectly acceptable to sign your own certificates, and yes, that's wat
companies like Thawte and Verisign charge at least $149 to do for you. They
don't even sell you a key, you typically have to provide that yourself, they
just sign the key, and then send you the certificate file.

I agree with your assertion that maybe the mod-aolserver would be the way to
go, as apache gets installed on ANY RedHat scripted installation. Don't know
about Devian.

ja

-----Original Message-----
From: webdev-bounce@xxxxxxxxx [mailto:webdev-bounce@xxxxxxxxx]On Behalf
Of Tom Hull
Sent: Friday, March 22, 2002 1:45 PM
To: webdev@xxxxxxxxx
Subject: [webdev] Re: evolution



OK, I'm going with the single 4GB disk. Installed the latest KRUD Red Hat
last night, default server, 865MB, so I have some stuff to add and some
stuff to get rid of. I didn't install apache, but will do so so we can
try it both with aolserver and mod-aolserver. If the latter works well,
it would probably be easier for people to set up development systems at
home, since they're probably running apache already.

Some more answers to Dale interposed below.

John Alexander wrote:
>
> I'll top-post to make it wasy. I haven't seen anything that details the
> configuration of SSL on AOLServer, but if we use mod-aolserver on top of
> apache, should be an exercise in triviality (is that a word?).

Yeah, but not here: trivial exercise.

> Just generate
> the cert, the key, and point the apacheconf at it. I'm assuming that there
> IS a way to run an SSL-enhanced AOLServer, since it's used for e-commerce
> sites (not my words, theirs), so the OpenACS would inherit those
> capabilities, correct?

I'm just cypherphobic. I've configured aolserver, but haven't set up the
keyfiles. I wonder whether this is where you get into certificates like
Thawte sells, or whether that matters.

> I haven't had any isses with working on Zope, but, here again, that was on
a
> machine that I configured, and only with very minimal web sites. I haven't
> really tried any of the add-ons to test/learn their functionality.
>
> ja
>
> -----Original Message-----
> From: webdev-bounce@xxxxxxxxx [mailto:webdev-bounce@xxxxxxxxx]On Behalf
> Of Dale W Hodge
> Sent: Friday, March 22, 2002 10:37 AM
> To: webdev@xxxxxxxxx
> Subject: [webdev] Re: evolution
>
> > -----Original Message-----
> > From: webdev-bounce@xxxxxxxxx [mailto:webdev-bounce@xxxxxxxxx]On Behalf
> > Of Tom Hull
>
> > > I'm assuming you mean that to fully implement all the feature
> > > will take that long.  Surely we could have something more basic
> > > working much sooner, right?
> >
> > Right. It should take a couple of days to configure a machine, set up
cvs,
> > openacs, aolserver, postgresql, htdig, some other stuff. I don't know
much
> > about ssh, and I've never gotten aolserver ssl set up, so I'll need some
> > help there.
>
> SSH isn't hard.  The default works well, or you can throw some switches if
> you are more paranoid. I haven't set up SSL yet, but it's not supposed to
be
> too hard.  It's enabled on my servers, but I've yet to configure it. We
> would also need _sudo_ set up.

I figure this is stuff that can be set up when I cart the machine to John
Alexander's place. Same for firewalling; right now I'm working to defeat
it, since it's in my way, but it needs to be rebuilt. You guys know more
about that kind of thing than I do.

> > Could stretch out, but not much. Then a couple more
> > days to lay
> > out some skeletal content. I'm a little shaky on some acs concepts like
> > groups and content sections, so it could take a bit longer to sort them
> > out. But it should give you user management, the ability for select
users
> > to add/structure content, ability for users to comment on content,
forums,
> > calendar, news, several other useful ready-built modules. Logs and
backups
> > will take some extra thought.
>
> I'll try to take a look at aolserver this weekend. I've got a spare box or
> two that I could use to test things locally.

Write me when you need some help on this. I can give you my config file
(at least the old one if not yet the new one), startup script, etc. Not
really much more than that. Check the openacs.org documentation.

> > > My preference would be to use the platform that offered the
> > > most pre-built functionality along with the easiest setup
> > > and maintainance. That's not to say we couldn't build something
> > > ourselves, but why re-invent the wheel if we don't have to?
> > > We may find that ease to use and functionality are mutally
> > > exclusive, in which case we'll have to decide which gets
> > >priority. My vote is for ease of use.
> >
> > I've been thinking about writing my own php-based web framework, but
it's
> > mostly for a different set of users/websites (individual writers, not
> > communities), so this effort could be extended if folks really get their
> > noses bent out of shape over openacs. I haven't been hearing that, so
> > for now the plan of record is to try out openacs. OK?
>
> I don't know enough about openacs/aolserver to make a decision yet. I have
> seen it run, but I haven't tried administering it yet. The devil is in the
> details, and that's what has soured me on Zope. I'll reserve judgement on
> openacs until we/I have a prototype running.
>
> That's my take. Hopefully some others will add to the discussion.
>
> --dwh
>
> ---
> Dale W Hodge - dwh@xxxxxxxxxxxxxxxx
> Vice Chairman & Secretary - info@xxxxxxxxx
> Air Capital Linux User's Group  (ACLUG)
> ---

--
/*
 *  Tom Hull * thull at kscable.com * http://www.tomhull.com/
 */