on 2/22/01 8:51 PM, Alan Knowles at [EMAIL PROTECTED] wrote:
> Current documentation is on www.hklc.com/midgard_manual - under staging/live -
> the nadmin code is very close to M3 - which depends on CVS midgard - as images
> and our 'news' code is replication safe.
> This inculdes
> - sample repligard.conf files
> - an perl script to generate apache conf files based on midgard host data.
> - the repligard_withsg.xml definition.
> - a script to downgrade the update times in the repligard table for
> non-approved pages and dependants based on the approval record_extension.
>
> I will try and put some release notes together for M3 as it makes some serious
> changes to existing sites developed with nadmin. - I have a script that goes
> through all the HTML and replaces any refernce to attachments with the new
> URL.
> - We will be testing on a few more machines.
Does "which depends on CVS midgard" mean that we need the newer php4 version
of midgard? And if so, is there an rpm for redhat available yet?
I'm also confused as to whether we should wait for the annoucement of M3
before we try to use HKLC's replication files or if we can go ahead and set
up staging/live replication as mentioned above.
Speaking of attachments, are they handled differently now? If so, could you
explain a little about the changes?
I'm really looking forward to setting up staging on my midgard web sites and
am putting off any real development until the midgard php4 upgrade becomes
available so replication of staging/live servers becomes a reality :-)
>>> Also, one additional intresting feature that I'm thinking about
>>> would be sending notifications to authors when their articles
>>> have been replicated to both servers. But this can easily be done
>>> on the PHP level...
>
> Our script replicates on a single server - a bit more work is needed to
> transfer the file across (rsync) to other servers and run import on them.
>
> I'm not sure about notifications. - this could be done at php level - but it's
> difficult to see how work out the conditions for this notification.....
>
> the replicate script would have to study what has been replicated, then
> reverse lookup who was the owner and then send emails... - Perl sounds like
> the easiest solution here......
>
> The import wrapper script:
> do the import
> grep for action='update' read the GUID's from the repligard.xml.gz file
> look up the info on the GUID from the repligard table in database
> look up the owner's email from the database
> send email....
> delete xml.gz file...
God this would be great!!! Automatic notification would be a real +!
Kudos to midgard, repligard, Aurora and HKLC!
enrique
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
