MESSAGE
| DATE | 2005-05-29 |
| FROM | From: "Steve Milo"
|
| SUBJECT | Re: [NYLXS - HANGOUT] Sunday Server Maintence Agenda
|
>From the webpage:
"Mason solves the common problems of site development: caching, debugging, templating, *maintaining development and production sites, and more*."
It is longer than 'content management software'.
Steve M
> Mason is not content management software
>
> It's an embedded web server programming tool
>
> ruben
>
> On Sun, 2005-05-29 at 11:50, Steve Milo wrote:
> > I figured some kind of 'content management software' would be necessary to help organize and accomodate for future growth.
> > The only reason I suggested Mason was because it was written entirely in Perl.
> > There may be other options to explore, I'm not biased towards or against any particular technology that fits NYLX's mission statement.
> >
> >
> > Steve
> >
> > > Yes
> > >
> > > I probably will. Mason is very popular. I'm not particularly found of
> > > it, but those who like the javabean concept love it.
> > >
> > > Ruben
> > > On Sun, 2005-05-29 at 10:15, Steve Milo wrote:
> > > > If I may make a suggestion.
> > > >
> > > > Install MySQL and Mason so they can be available for future expansion and growth.
> > > > Mason is a website content management software written entirely in Perl.
> > > >
> > > > www.masonhq.com
> > > >
> > > > Having these installed and available will not interfer with the operation of the server.
> > > >
> > > > Steve M
> > > >
> > > > > As it is, I'm not working tomorrow so I'll be in the house for most of
> > > > > the day. For everyone coming, our battle plan for the Server tomorrow
> > > > > is the following:
> > > > >
> > > > > 1: Make a backup server on the spare box
> > > > >
> > > > > 2: Reboot the server with the backup server ready and working in case
> > > > > of trouble
> > > > >
> > > > > 3: rebuilding Apache with Apache 2, mod_perl and embperl. this will be
> > > > > my first look at Apache2 closely, so we'll be looking at a bunch of
> > > > > documentation.
> > > > >
> > > > > 4: Load up a sizable amount of static content back on the Apache server
> > > > >
> > > > > 5: Move the mail server to the backup server and make it the new mail
> > > > > server, separate from the main machine.
> > > > >
> > > > > 6: Rebuild the freedom-IT box and install the webmail interface on it.
> > > > >
> > > > > Ruben
> > > > >
> > > >
> > >
> >
>
|
|
