From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HOWTO unmaintained?
Date: Thu, 18 Aug 2005 07:04:54 +0000 [thread overview]
Message-ID: <200508180904.55023.stef.coene@docum.org> (raw)
In-Reply-To: <m3d5odyoom.fsf@reason.gnuhh-core>
On Wednesday 17 August 2005 23:44, Taylor, Grant wrote:
> > It looks like a number of people are offering sites -
> > IMHO, a "distributed" wiki (ie: you can edit at any of
> > the sites) or a master/mirror setup would be good, as
> > that would help prevent problems if site maintainers
> > get kidnapped by aliens, sites get slashdotted, etc.
>
> I think the Wiki, if that route is chosen, should be on the www.lartc.org
> domain name. This means that we will have to find and contact the
> administrators of that domain / DNS servers.
(I'm not official subscribed to this list, but I'm still reading some posts)
I know the owner of lartc.org and I mailed him about this problem. I will
keep the list updated if he answers me.
> As far as the distributed web
> site goes I think it is a good idea. To pull off the distributed site we
> would need to have the DNS records resolve to multiple boxen across the
> net. I have considered a self replicating set up for some of my servers
> and at present I'm looking at using Coda or AFS as a replicating / caching
> local copies of the remote file system content. I've never dealt with
> Wikis other than and end user (and I say that the ones that I've looked at
> have been slow) so I don't know what they take to set up. I suspect that
> they use a database and thus we would want to set up the Wiki to use a
> database that has real time replication between the two (or more) web
> servers that the wiki points to. I would be more than happy to help with
> such an endeavor. I can not host it at my office (bosses will not let me)
> but I can help provide content and / or convert stuff.
There are lots of wiki's available. Some use plain text files, some uses
mysql, some are written in php, some are written in perl. I prefer the mysql
+ php way to store the information.
Stef
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-08-18 7:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 8:04 [LARTC] HOWTO unmaintained? Georg C. F. Greve
2005-08-17 10:19 ` Andreas Klauer
2005-08-17 10:40 ` Georg C. F. Greve
2005-08-17 11:28 ` Ed W
2005-08-17 12:26 ` Kenneth Kalmer
2005-08-17 12:27 ` Mike O
2005-08-17 13:38 ` Lee Sanders
2005-08-17 14:09 ` Andre D. Correa
2005-08-17 16:24 ` Stephen Hemminger
2005-08-17 16:28 ` Dariusz Dwornikowski
2005-08-17 17:05 ` Jonathan Day
2005-08-17 17:27 ` Andreas Klauer
2005-08-17 17:33 ` Carl-Daniel Hailfinger
2005-08-17 17:39 ` Carl-Daniel Hailfinger
2005-08-17 21:44 ` Taylor, Grant
2005-08-18 7:04 ` Stef Coene [this message]
2005-08-18 13:00 ` Ed W
2005-08-19 14:52 ` Stephen Hemminger
2005-08-20 11:17 ` Riccardo Losselli
2005-08-20 15:17 ` Alexander Reelsen
2005-10-05 23:18 ` noc ops
2005-10-06 2:41 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200508180904.55023.stef.coene@docum.org \
--to=stef.coene@docum.org \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.