On  6 Dec, Ken Pooley wrote:
> 1.A question.... The Midgard website mentions using the system on 
> MacOSX...which parts of the system is being used is it the whole 
> Apache/Midgard/MySQL system or just parts...in part I guess I am asking if 
> there is a MySQL build for MacOSX I didn't know about....

IIRC, Emile has notes on what is required for Midgard
install on OSX Server. Also, some people on this list
are running it, so you'll probably get more information
from them.

The long term plan is to include notes on how the
installation procedure differs on a specific platform
to the Installation section of the manual, but we are
not quite there yet.
 
> 2. The problem...I installed the Apache_midgard monster RPM and inspite of 
> my efforts to mess it up got it running...it is doing something odd now 
> though....the first time I go in I just get the directory for the http 
> document root...but if I reload a few times it will finally come up...this 
> wil also happen as I move about the admin site...click a link get an 
> error...reload and get the page...one of the debug errors that is coming up 
> often is "database not defined for my.computer.edu" Any ideas?? This is a 
> test server running off of my laptop so it may be a little 
> squirrely(sp?)...it only starts up ever fifth time too....

I've seen this same happen with some setups. The problem
is that every Apache process you have running on your
system makes a separate connection with the MySQL database.

When the number of processes running passes the limit
of client connections defined in MySQL's configuration,
some are left without access to Midgard information.

These processes then display normal Apache content instead
of the actual Midgard content. Because you don't have
any static HTML files in your DocumentRoot, the server
then just displays the directory contents.

To fix this, adjust the amount of child processes
Apache spawns and the allowed number of client connections
in MySQL so that they are in sync (preferably so that
MySQL accepts a bit more connections than Apache
spawns processes, just to be on the safe side).

> 3.The Suggestion.....In my far too exhaustive search for content management 
> services I have seen most of the big...and wicked expensive....systems and 
> there are simple features out there that might be looked at for future 
> versions of midgard.

It would be very nice to see some feature comparisons
between Midgard and these products. While we try to
make Midgard's topic system as good content management 
environment as we can, it wouldn't hurt to borrow ideas
from other similar systems.

<snip>
> writers and editors I work with liked the ability to write a story in a 
> writer's interface and have a release button in the editor's interface so 
> that there would be flow control and authority in a centralized place. Both 
> parties also liked having version histories so that as the editor/writer 
> exchange process went on ther would be a history of the revisions and 
> versions...the first would be pretty easy though i can see where the 
> revision history feature could tax a database if too many versions of a 
> story clogged up the DB...maybe when a story is released for distribution 
> the history would be discarded........

We have some of that functionality in use with 
Stonesoft's Midgard-based content management
system (which we use with most of Stonesoft's
external sites). The writers and editors have
a simple interface for adding and modifying
documents (articles, files, images and links)
in a topic tree. The interface is just a
simplified version of the one found in the
Admin site. It has the additions of previewing
and primitive version control.

When a document is ready, and the editors want
it published on the external site, they just go
to the document and push a 'Approve this document'
button. This button makes a copy of the article
using Midgard's reply mechanism and adds the
Approval stamp.

The document versions stored by the approval
system can be retrieved and modified with the
same system.

When the document has been approved, it then
gets noticed by a cron script and replicated
to our external servers via SSH.


While this way of handling version control is
far from ideal, it is a beginning. It would be
nice to study Xanadu's extensive version control
features now that it is open source, and see
how we can improve Midgard to add at least some
of those functionalities.

> kp

/Bergie

-- 
-- Henri Bergius -- +358 40 525 1334 -- [EMAIL PROTECTED] --
               http://www.iki.fi/Henri.Bergius


--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org

To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]

Reply via email to