Details
-
Story
-
Resolution: Unresolved
-
None
-
None
-
None
-
Linux
-
Empty show more show less
Description
introduction
The install- and Update-Kit is the needed base for translate5 to gain a wide spread installation base - and to be able to maintain and update installations for anyone regardless of his computer skills.
The main aspect for a wide spread distribution is the installer - while the main aspect for a happy user base is the updater. Only with the updater it will be possible to support a larger installation base of translate5 by the developers - and thus deploy new features and bugfixes to the users.
glossary
Application
An application equates to our current git main repositories. It can be the standard translate5-instance, or another Zend Framework-based project, in which translate5 is integrated
Installation
An installation is the running version of the above application.
Build / Deploy
Building an application means creating a release with a dedicated release number for an application.
Deploying means installing / updating the above created release to / in a dedicated installation.
Base-System: Linux or Windows
Windows
Currently the Install- and Update-Kit is only planned for Linux. A windows version based on MOWES Portable or XAMPP package is possible but not planned so far due to open financing and open questions how to handle license aspects of the used components (like apache, mysql etc.).
Linux
Under Linux we assume that all system dependencies (php, mysql, apache, used php-extensions etc.) are given. This assures the “System Checker” in the pre installation phase. Used external code libs (like ExtJs, Zend Framework, XliffTermTagger etc.) will be installed and updated by the kit.
Installer and Updater
Installable will be only major updates which will be made publicly available. After running an installation the user should then be redirected to the update overview to install available minor updates.
The whole Installer and Updater runs in a separate Zend Framework Module /updater/. The whole update-module can be protected by:
- .htaccess
- Default User handling
Order of Implementation
- Configuration Management (
TRANSLATE-123) → is basic task for refactoring and the other tasks - Database Installation / Updating (
TRANSLATE-130) → blocksTRANSLATE-133 - Refactor Release Management (
TRANSLATE-131) → blocks TRANSLATE-134 andTRANSLATE-130(only in conjunction with the updater) - Release Provider on our Server (TRANSLATE-134) → blocks
TRANSLATE-133 - File Updater / Fetcher (
TRANSLATE-133) → blocksTRANSLATE-135 - Requirements Checker (
TRANSLATE-124) → blocksTRANSLATE-135 - Install and Update Wizard (
TRANSLATE-135)
Technically independant from above subtasks (can be done everytime, with light modifications after TRANSLATE-131 and TRANSLATE-135):
- Maintenance Mode (
TRANSLATE-137) - Application Versioning in the Frontend (
TRANSLATE-138)
Attachments
1.
|
write to mysql, apache, php and php extensions, Ext Js, Horde, XliffTermTagger, restfullZendFramework about integration in installer | Done | Marc Mittag [Administrator] | |
2.
|
concept, what in detail the installer should be able to do | Done | Marc Mittag [Administrator] | |
3.
|
Configuration Management | Done | Thomas Lauria | |
4.
|
Database Installation / Updating | Done | Thomas Lauria | |
5.
|
Refactor Release Management | Done | Unassigned | |
6.
|
Release Provider on our Server | Backlog | Unassigned | |
7.
|
File Updater / Fetcher | Done | Unassigned | |
8.
|
Requirements Checker | Done | Unassigned | |
9.
|
Install and Update Wizard | Done | Unassigned | |
10.
|
Maintenance Mode | Done | Aleksandar Mitrev | |
11.
|
Application Versioning in the Frontend | Done | Unassigned |