Tom Jackson wrote:
=0 A
> What was broken? Is it just the website hosting?
Turns out, the aolserver.{com,net,org} DNS was set up as A records to
66.35.250.210 instead of CNAME's to vhost.sourceforge.net - which
recently changed to 216.34.181.97 with the SourceForge move to Chicago.
I've put in the necessary request to get the DNS updated at AOL (who
still manages the DNS for the domains).
No idea how long it'll take for them to act on the request. You can
access the site at http://aolserver.sourceforge.net/ for now, though.
--
Dossy Shiobara | do...@panoptic.com | http://dossy.org/
Panoptic Computer Network | http://panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <list...@listserv.aol.com>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
0
-- AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <list...@listserv.aol.com> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
So, several generous offers have been made towards hosting of the
AOLserver project. What does the project actually need? Here's a short
list off the top of my head:
1) Web content hosting, preferably using AOLserver itself
2) Code repository hosting
3) Bug tracking
4) Project file downloads
5) Mailing lists
(Have I left anything off the list? Please add anything you feel is
missing.)
How should this be accomplished? Should we set this up in OpenACS? Use
third-party services (Google Code, Launchpad, etc.)? Something else,
entirely?
Or, should we just leave everything the way it is?