Skip to content
Browse files

Moving install-from to the scripts directory

  • Loading branch information...
1 parent 43149cb commit eda7cdc40b21eaf44326f5eea650b8ea344cd462 @timf timf committed Oct 14, 2010
Showing with 6 additions and 10 deletions.
  1. +5 −9 README.mkd
  2. +1 −1 { → scripts}/install-from
View
14 README.mkd
@@ -17,17 +17,13 @@ Run this command to build, install, and configure Nimbus to a specified path:
./install /path/to/destination
-NOTE: This is an interactive program, you will be asked a few questions at
+Note: This is an interactive program, you will be asked a few questions at
the end.
-
-Run this command to do the same thing but use a previously installed Nimbus
-service as the basis for the configuration of the new one.
-
- ./install-from /path/to/old/install /path/to/destination
-NOTE: 1) This will only work if the old install is Nimbus 2.5 or higher.
- 2) The old installation needs to be taken offline first and no VMs
- should be running.
+To upgrade from an existing Nimbus installation, visit the current upgrade
+guide to learn how to use the install-from command.
+
+ http://www.nimbusproject.org/docs/current/admin/upgrading.html
Advanced users may also want to build and deploy to an existing GT4.0
container. Refer to the readme and scripts in the `scripts/` directory
View
2 install-from → scripts/install-from
@@ -4,7 +4,7 @@ FORCE_FRESH_INSTALL="yes"
START_DIR=`pwd`
-NIMBUS_SRC_REL="`dirname $0`"
+NIMBUS_SRC_REL="`dirname $0`/.."
NIMBUS_SRC=`cd $NIMBUS_SRC_REL; pwd`
function usagetxt {

0 comments on commit eda7cdc

Please sign in to comment.
Something went wrong with that request. Please try again.