Ok, well I'm still skeptical about multiple citservers running a single site
in a non-federated tandem ... but either way it still sets out a pretty clear
roadmap for the kind of things we need to do next. It still means we move
all of the config stuff into the database. So we'll
I do understand the whole uptime thing. Remember, I work in the hosting
business. I know all about 99.999% SLA's (which somehow seem to be disregarded
when Exchange shits the bed -- shouldn't all those people be running something
more reliable?)
Only problem I can see with a
P.S. I should have added: the whole 'logging' thing goes away, and the 'CULL' command is a no-op in the HA setup.
P.P.S. As I'm a bit late to the citadel world, I actually have no certain idea what anyone who posts here does for work, where in the world they live, or, well, anything. I gather
The beautiful thing about the mariadb/galera multimaster database approach is: Each cit-server talking to a database server instance --- running on the same box citadel is --- thinks it's the only server running. The fact that citadel has that wonderful 'go threading' call, and has sorted
From the very beginning, the idea of a pluggable data store has been part
of the architecture. We've done it once -- originally we were using gdbm
but because that was so unstable we switched to Berkeley DB.
dothebart would undoubtedly want to use ArangoDB.
I'm ok with it as long as it
Fri Apr 03 2015 10:58:37 EDTfrom IGnatius T Foobar @ Uncensored Subject: Re: CODE FREEZE - RELEASE IMMINENT
From the very beginning, the idea of a pluggable data store has been part of the architecture. We've done it once -- originally we were using "gdbm" but because that was so unstable we
I really don't think we should try to fill that gap - since nobody
had scalability issues with citadel so far. Just for failover drdb is
perfect.
There was a time when we wanted to try to be an enterprise mail/groupware
system. That gave rise to the Global Address Book and the idea
the idea that you could spread a single Internet domain across a large
group of Citadel servers, and there is still all sorts of bizarre
message routing code to make that happen.
... and this brings up the first bit of axe wielding.
Effective immediately, I am removing support
I've done a lot of comparison between options in the email server space, and also in the high availability space. Because of the clamav and built in access to the spam daemon, Citadel server lacks only one thing to be the best replacement for hacked-together postfix+lmtp+caldav/webdav, etc.,
Ok folks, the v9.01 tag is in git, and Easy Install has been updated.
I'll do the tarballs shortly.
For the 9.xx development cycle, I'd like to keep the trunk fairly stable
and do unstable work in branches, if possible. Some of the things I'd like
to accomplish during 9.xx:
*
Wed Apr 01 2015 12:45:07 EDT from IGnatius T Foobar @ Uncensored Subject: Re: CODE FREEZE - RELEASE IMMINENT
Whats the release version gonna be? 8.30?
9.01 I'm updating it now.
did you try out the discount configure etc. code? I wasn't really able to test it, as I would have liked with
Ok, fixed some tiny leaks, and install stuff.
easy install git will now drag discount - wasn't able to test it with the download yet, can we get queasy install working once more?
http://www.pell.portland.or.us/~orc/Code/discount/discount-2.1.8.tar.gz
should be copied to the download directory.
hm, I've fixed the init script for the .debs, wanted to continue with easy install, but can't seem to find it?
wouldn't setup contain them as here document?
13 matches
Mail list logo
