|
From: | Don Cruickshank |
Subject: | RE: [Myexperiment-discuss] RE: deploy myexp |
Date: | Sat, 26 Jul 2008 16:50:15 +0100 |
Tony, If it’s a similar machine (e.g. the same version of Ubuntu
etc) then you should be able just apt-get install exactly the same packages
that you used apt-get to install on the development machine. Then instead of going through the process of installing all the
gems as before, you should be able to just erase /usr/lib/ruby on the production
machine and replace it with a copy of that directory on the development
machine. Once you do this, you should be able to list all the gems you’d
expect to see there. Just as a reminder, you’ll also need the “dot”
binary to generate workflow images. With regards to our trunk directory, our aim is to keep trunk stable
enough for anyone to check out a working copy at any time and be able to get
myExperiment up and running. When we do development work in the
repository that isn’t stable, we work on a branch in the branches
directory. Give us a shout if you want a hand with the merge process. Cheers, Don. From:
address@hidden
[mailto:address@hidden On
Behalf Of David De Roure Great! I’ll let Don, Jits or Dan respond to this one
in detail (sounds like something to be on the developers wiki... we have
policies about how trunk is handled with our distributed dev team and how we
stage via an internal test server). -- Dave From:
address@hidden
[mailto:address@hidden On
Behalf Of Linde, A.E. One more... In
a week or so I'm hoping to deploy the version of myexperiment that I've
modified (rev 1549) so that colleagues on SKUA can see what I've got so
far. Is there an easy way to do that or do I have to get access to the server
concerned and go through the same process as in developers.txt? Once
I've done that I'll merge the current version of the code back in to my
version. Is trunk always a clean working version or do I need to wait for
someone to announce a clean version? Cheers, Tony. |
[Prev in Thread] | Current Thread | [Next in Thread] |