Creating MindTouch Packages

Upon installation, end-users automatically receive all deployable packages based on license capabilities

Upon any new installation, MindTouch packages will automatically deploy that mirror those in SVN at last code freeze.

Upon update, end-users automatically receive updates to all deployable packages based on license capabilities

Upon update, MindTouch packages will automatically deploy that mirror those in SVN at last code freeze, with the exception of hierarchies that are flagged as "editable" - particularly those in the IDF/pages hierarchy.

Command Line

These are the command line tools I run to create all the packages. They reference loose files ("mindtouch-templates") which are files with  absolute URLs (one per line) of the targeted template tree (as outlined in the table above under "hierarchies covered").

mono mindtouch.import.exe -U "admin" -P "password" -h "TARGET-MINDTOUCH-INSTALL" -e -L mindtouch-templates -r -O ../packages/default/public/0010-mindtouch-templates.mtapp;
mono mindtouch.import.exe -U "admin" -P "password" -h "TARGET-MINDTOUCH-INSTALL" -e -L mindtouch-special-reports -r -O ../packages/default/private/0010-mindtouch-special-reports.mtapp;
mono mindtouch.import.exe -U "admin" -P "password" -h "TARGET-MINDTOUCH-INSTALL" -e -L mindtouch-templates-ckb -r -O -cap package-idf ../packages/default/public/0020-mindtouch-templates-idf.mtapp;
mono mindtouch.import.exe -U "admin" -P "password" -h "TARGET-MINDTOUCH-INSTALL" -e -L mindtouch-templates-ckb-pages -r -l -cap package-idf ../packages/default/public/0030-mindtouch-templates-idf-pages.mtapp;
mono mindtouch.import.exe -U "admin" -P "password" -h "TARGET-MINDTOUCH-INSTALL" -e -L mindtouch-imm -r -O -cap package-imm ../packages/default/public/0040-mindtouch-imm.mtapp;

Creating/Updating Packages

All steps assume you've checked out the base svn library, above.

To create new packages (.mtapp files):

• Go to the root library folder and run ./package.sh (provide host/name/password when prompted)
• This checks out the latest content from svn, re-imports, and creates the packages above.
• Packages are exported to ./packages/export/default. They can then be tested or checked into svn trunk.
• Remove title nodes from package.xml for the OOBE homepages
  • http://bugs.developer.mindtouch.com/view.php?id=8777
    
     

To update loose XML files in svn:

Sample Scenario: Update default templates with new content

• Go to the /oobe, /template, or /specials folder under the library
• Import the loose XML files into your MindTouch installation: ./import.sh (you'll be prompted for host, name and password)
• ...Make changes to template pages in your local installation...
• Copy your MindTouch pages back to loose files: ./export.sh (again, prompted for host/name/password)
• Commit the modified loose files into svn (including package.xml)
• If repackaging the .mtapp files, create new packages as above

To copy pages to another server

Sample Scenario: Give Product Management a safe area to edit the OOBE experience

• Export the desired pages as a zip file (suppose you are in the /oobe folder and want to export /Template:MindTouch/OOBE):
  •  mono ../mindtouch.import.exe -e -r -p /Template:MindTouch/OOBE -X /Template:MindTouch/OOBE oobe.zip
  • This recursively exports /Template:MindTouch/OOBE relative to /Template:MindTouch/OOBE, so it can be re-imported anywhere
• Import the .zip file onto a hierarchy (/Product_Management/OOBE) on the new server
  • mono ../mindtouch.import.exe -I /Product_Management/OOBE oobe.zip
  • When prompted, enter the host/user/password for the destination
  • Edit the pages on the new server.
  • When finished, perform the reverse: Export the files from the new server, and import back into the old.
  • You can then export the files on the old server, commit to svn, and repackage.

Administration Notes

Note: The .mtapp files are zips, and can be extracted with "7za e package.mtapp" (apt-get install p7zip-full if 7za is not installed). For some reason, the packages do not open on Mac -- use Windows and Izarc (for example) to edit the contents of the package.