[webdev] Postnuke hosting -- more specifics

[John Goerzen <jgoerzen@xxxxxxxxxxxx>]

On Sun, Oct 06, 2002 at 06:43:18PM -0500, Dale W Hodge wrote:
> John Goerzen has offered to host the new site on the same machine as the 
> current
> site. We would have to work out what we need in terms of access (ssh shell, 
> etc)
> and see if he would be willing to provide such.

Let me put forth a more specific offer.  Again, this is just an offer; y'all
can discuss whether you like this option or others, and I'm fine with it
either way.  I'm happy to continue hosting DNS, mailing lists, and archives
for ACLUG independant of the location of the website.

I'm willing to host www.aclug.org using a current version of Postnuke on
complete.org.  The specifics are:

 * complete.org is located in a California hosting facility with
   three independant upstream connections.  The machine itself contains
   redundant power supplies from separate companies, Diesel backup, Halon
   fire suppression, hot-swap power supplies and fans, hot swap disks
   (RAID), and is backed up daily on-site at the facility and weekly to my
   system in Hesston.  The operating system is FreeBSD (yeah, not my first
   choice either, but that's all that they support).  The facility and I
   both monitor FreeBSD security alerts, bugtraq, etc. and keep the system
   up-to-date.  I am the primary administrator of the machine, but the
   facility employs professional FreeBSD admins that can act on my behalf,
   and can do things like kernel upgrades that require a reboot -- they'll
   make sure it comes back up :-)

 * I am willing to install the latest version of Postnuke with a PostgreSQL
   backend.  Also, any Postnuke-related
   PHP packages or Postnuke themes, blocks, or modules from the postnuke
   site.  Once installed, the Postnuke installation will be managed
   solely by the ACLUG webdev team or other designees of the ACLUG president.
   I would not expect to have an admin login to Postnuke nor to actively
   maintain its content (only its installation -- upgrades, etc).

 * I would not want to install a hacked Postnuke core.  This will make
   administration and upgrades difficult and could introduce unexpected
   security consequences.

 * I will expect to ask consent prior to any Postnuke code upgrade
   unless security considerations demand otherwise, in which case I will
   inform webdev after the upgrade has been taken place so they have a
   chance to review the site immediately.

 * I will not provide root to anyone.

 * I may possibly provide shell access to someone; however, I am not
   inclined to do so.  There's not a lot that can be done with a non-root
   shell that would be of any benefit.

> >   * bug tracking system
> 
> Only needed on modules we produce. Bugs in PostNuke itself should be filed at
> the development site.

Complete.org already has a bug-tracking system set up at bugs.complete.org. 
I am more than willing to add ACLUG categories to this system.  This offer
stands regardless of where you put the site or what it's hosted on.

FWIW, I maintain a Postnuke installation for my company intranet, so I am
not a total stranger to it; though I am doubtless less knowledgable about it
than others in this list.

-- 
John Goerzen <jgoerzen@xxxxxxxxxxxx>                       www.complete.org