Web Installer
Table of contents
Introduction
With the launch of Olympic, MindTouch now has two primary delivery mechanisms for populuating content: SQL scripts and import/export. With the web installer not receiving a facelift in many releases, it comes time for us to factor in (1) technical advancements in the platform (2) product slices and (3) better understanding of the optimal user experience for installation.
Intended Audience
This will be applicable to all versions of MindTouch.
Status
Initial scoping by RoyK. Candidate for Pipestone.
Functional Specification
Use Cases
User wishes to install MindTouch 2010 or MindTouch Platform
All users will download a single package: MindTouch. From that single package, when they reach the web installer, they will have an option of choosing which version of MindTouch to install: MindTouch 2010, MindTouch Platform v.10, or MindTouch Core (subject to debate). Upon completed install, the proper license type will be requested and sent to them.
Non-goals
- The upgrade script story should not be addressed quite yet - they are two distinct items which can be handled at different times.
Technical Specification
General requirements
Currently the installer's process looks something like this:
- User loads install form
- Script does initial environmental check
- Script detects initial state (VM? Enterprise? Trial?)
- User inputs information
- (For non-VMs, they input necessary server credentials)
- Script installs MindTouch
- Creates schema
- Populates content
- Populates users, services, extensions
- Script requests trial license from trial.mindtouch.com
- Script executes API startup, moves config files around (for VM, for non-VM, automatic steps)
- This triggers package updater
- User logs-into site
- User sets licenses upon login
UI requirements
API requirements
- Tag page
- What links here
| Images 0 | ||
|---|---|---|
| No images to display in the gallery. |
Copyright © 2011 MindTouch, Inc. Powered by