CustomizationAndBuild

Customize and build your base installers

This page describes the customizations to code required before you can build base installers, and also the actual build process.

Set nodemanager version

In $REPO_PARENT_DIR there is a subdirectory for the nodemanager. Go there, and edit nmmain.py. It includes a line starting with version = .

Change the version string to reflect your project / clearinghouse / Custom Installer Builder name, and also the current build. You will later need this string when launching the build script.

Check softwareupdater URL and key pair

Remember the public/private key pair whose filenames and paths you configured in the build script? In order for your installers to be able to validate updates that you push, the softwareupdater component must include your (or your update site's) public key.

For this, change into the softwareupdater subdir of custominstallerbuilder/scripts/ and edit softwareupdater.py. On the line starting with softwareupdatepublickey = , replace the value under the key 'e' of the dict with the first int of your public key, and the value of key 'n' with the second.

Step 4: Build the base installers and place them in the "custominstallerbuilder/html/static/installer/base" directory.

$ cd ../dist/
$ ./rebuild_base_installers_for_seattlegeni.sh VERSION_OF_RELEASE
$ pushd /var/www/dist (location your BASE_INSTALLER_DIRECTORY is set to)
$ cp seattle_linux.tgz seattle_mac.tgz seattle_win.zip seattle_android.zip /user/trunk/dist
$ popd
$ cd /attic/trunk/dist
$ tar -xf seattle_linux.tgz

(change seattle_linux.tgz to match whichever operating system you are installing this for)

Step 5: Install Seattle with the base installers.(Optional)

$ cd seattle
$ ./install.sh

Step 7: Still within the "custominstallerbuilder" directory, run the django test server:

$ ./manage.py runserver 0.0.0.0:PORT

This command assumes that the Seattle standard library is in your Python path.

If it isn't, then run:

$ export PYTHONPATH=home/user/attic/trunk/dist/seattle/seattle_repy

You should now be able to access your Custom Installer Builder test server at the address specified for BASE_URL above.