on 2/23/01 9:17 PM, Alan Knowles at [EMAIL PROTECTED] wrote:
> Enrique Vega <[EMAIL PROTECTED]> said:
>> 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?
>>
>
> At present, last nights CVS seems to be working on a test server, I have a few
> more tests, then we will install it on our development server.
> Basically 1.4.1 is very close... (if all goes well, I guess a week???????)
> Nadmin will depend on this, as It includes code that ensure replicatable safe
> sites.
>
>> 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.
> You can try the snapshots - but they will only work on CVS midgard, and full
> instructions wont be available until it is released.
> (hint - there is a tools tab - use the convert images link in it)
Ok, since you all know by now that I am a newbie, I have to ask a couple of
questions about cvs, rpm's, nadmin, repligard, and midgard. I am perplexed
as to what is the best way for me to keep up with the various changes
occurring which end up with revisions to nadmin and midgard.
I've been reading enough about cvs to possibly get myself into trouble :-/
First off, I have midgard 1.4 installed via rpm on my RaQ3 with the helpful
guidance of Alexander. I also have nadmin_M2.xmlgz installed on my
production server. Note that the midgard modified PHP3 is used by other php
based applications which are actively used. Changes to midgard can affect
these online applications, so this is where one of my primary concerns lies.
It seems that nadmin is using the latest CVS midgard, so that if I desire to
use the latest snapshots, I need to upgrade to the latest midgard. I have
read the directions about cvs midgard at:
http://www.midgard-project.org/article/1000.html
And I'm willing to try to set up my midgard application to use the latest
cvs, but I'm concerned about how the change will affect the existing
installation from rpm. So here are a couple of questions which will help me
determine what steps to take to prevent me from totally screwing up my
server:
1. Since I installed midgard from rpm, I used the default settings of where
midgard is installed. Or so I think :-/ The cvs how-to at midgard states in
part:
First tell cvs where to find the source tree:
$ export CVSROOT=':pserver:[EMAIL PROTECTED]:/usr/local/cvs'
Then login using an empty password (just hit return in the prompt):
$ cvs login
You can then get the latest sources with the command:
$ cvs -z3 checkout midgard
So if I do this, where is CVS midgard installed?
2. How do I get my server to use the newly copied CVS midgard?
3. Is it possible to get cvs to use the existing midgard from rpm as a
starting point? If so, how do I tell cvs where my midgard is at?
4. Maybe I am going about this all wrong! I'm assuming that getting the
latest cvs midgard is as simple as using rpm. Am I wrong to think this way?
5. Once I get the latest cvs midgard, do I still have to install it? Is
there an equivalent src.rpm or do I need to make the rpm?
6. Maybe I should simply chill out and wait for the latest rpm from midgard.
Then get the applicable nadmin from hklc which will work with installed rpm.
I'm just concerned about the timeliness of upgrades between midgard official
releases and nadmin upgrades. Does this make any sense to you guys?
All advice is greatly appreciated!
enrique
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
