2
edits
Changes
Jump to navigation
Jump to search
Created page with "== MozUS - Mozilla Update Server == MozUS is a server update for the Mozilla products. MozUS was thought to install in complement of SOGo and was developed to allow a fast m..."
== MozUS - Mozilla Update Server ==
MozUS is a server update for the Mozilla products.
MozUS was thought to install in complement of SOGo and was developed to allow a fast maintenance and fast deployments of a SOGo/Thunderbird solution.
=== Requirements ===
SOGo requires SME 8 (Final release available since May 2012)
=== Optionnal Requirements ===
MozUS can function without SOGo being installed on your server.
To install SOGo : [http://wiki.contribs.org/Sogo SOGo].
It is not necessary to follow the procedure “Thunderbird Configuration”, this part is integrated in MozUS.
=== Principle of Operations ===
MozUS integrates two functionalities:
- Maintenance of the updates software Thunderbird and Firefox (ESR version only).
- Maintenance and deployments of the additional modules for Thunderbird (Firefox does not profit for the moment of this functionalitie).
=== Install ===
To complete
yum install smeserver-mozus
signal-event post-upgrade; signal-event reboot
=== Configuration ===
Once installed you will have access to a new section in the server-manager. This section comprises 3 new pages:
- Mozilla Update Server : You will be able to enable/disable MozUS, to authorize the updates for Thunderbird/Firefox, to authorize the major updates, the maintained versions and platforms.
- Planner of MozUS : Allows you to define the frequency of synchronization of “mirror” MozUS
- Complementary Modules: You allows to download the additional modules directly and to manage the modules to be maintained. The preset preferences via the module “sogo_integrator” are also defined here.
1.) Define your various parameters in the first panel.
2.) Define the interval of synchronization of “mirroir” - has interval regular where Mozus will check on the Mozilla servers if one or more new versions are available.
3.) Download the modules “sogo-integrator”, “sogo-connector” and “Lightnings” for the versions to be maintained here: [http://www.sogo.nu/en/downloads/frontends.html Inverse Sogo Frontends En]
4.) Download the additional modules that you wish deploy and define the parameters preset.
5.) Download [http://www.mozilla.org/en-US/thunderbird/organizations/all-esr.html Thunderbird ESR] and/or [http://www.mozilla.org/en-US/firefox/organizations/all.html Firefox ESR]
==== Thunderbird ====
Import the certificate of your SME as an authority of certifications (If not the synchronization of the modules will not be done).
The certificate is downloadable here: https://servername.domainname/SOGo-plugins/servername.domainname.crt (ex: https://www.example.com/SOGo-plugins/www.example.com.crt).
Configure the default account email before installing the module “sogo_integrator”.
In the server-manager, download the module “sogo-integrator” modified by MozUS and install it in Thunderbird.
Start again Thunderbird and let make.
==== Firefox ====
Import the certificate of your SME as an authority of certifications (If not the synchronization of the modules will not be done).
The certificate is downloadable here: https://servername.domainname/SOGo-plugins/servername.domainname.crt (ex: https://www.example.com/SOGo-plugins/www.example.com.crt).
In Firefox, go in the editor of configuration (accessible via 'about:config').
Create/Modify the following parameters :
app.update.url.override=https://servername.domainname/moz-updates/updates/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
app.update.auto=false
app.update.cert.checkAttributes=false
app.update.cert.requireBuiltIn=false
app.update.enabled=true
autoupdate.enabled=false
=== Command Line ===
MozUS is provided with two utilities :
==== /usr/bin/Mozmirup ====
Allows to manage the synchronization of the update and accepts two parameters :
/usr/bin/Mozmirup --update => Force a software research of the updates on the Mozilla servers.
/user/bin/Mozmirp --delete-obsolete => removes the files of updates not answering the criteria (also accessible since the first panel)
==== /usr/bin/Mozaddons ====
Allows to manage the integration of the additional modules and accepts two parameters :
/usr/bin/Mozaddons --update_sogo => makes it possible to update the modules 'sogo-integrator present.
/usr/bin/Mozaddons --add_update /path/addon.xpi <nowiki> [new name] </nowiki> => allows the addition or update of a module.
''The module path is an obligatory parameter while the parameter “new name” is optional.''
=== Optional Configuration ===
==== UseSSL ====
If your installation of SOGo does not comprise redirections HTTP towards HTTPS, you are likely to meet an error during the synchronization of the calendars/contact and additional module.
It is possible to modify the parameters of MozUS not to use “https”.
Disable the use of “https” and regenerate PHP files of Mozus:
db Mozus setprop Mozus UseSSL disabled
expand-template /opt/mozilla-updates/mirror/updates
expand-template /opt/mozilla-updates/SOGo-plugins/updates.php
/usr/bin/Mozaddons --update_sogo
=== Appendices ===
==== How Mozus integrates a module ====
The integration of a module by MozUS is done in the following way:
1.) The modules “xpi” are with the format zip, the first stage thus consists with decompress
2.) Once decompressed, one treats the file “install.rdf” which comprises following information:
- Name and Identifier of the module.
- Version of the module.
- Compatible Mozilla Products.
- Versions of the compatible products.
- Compatible platforms.
3.) According to the module, we modify the file “install.rdf” to remove useless information
- For a simple module we leave only information relating to Thunderbird
- For the module “sogo-integrator” we modify his internal version (with an aim of managing a single version for each modification carried out by MozUS). The files “extensions.rdf”, “Site.js” and “custom-preferences.js” are regenerated and to integrate in the module.
''Note: The treatment is carried out line by line. The file “install.rdf” is of type xml and the various developers do not conform all to the same format.''
So none the methods of parse tested before gave a conclusive result on the various modules.
4.) The module is then recomposed, a key east creates in the Mozus base. In same time, the module is copied in “/opt/mozilla-updates/Moz-AddOns” and symbolic links are created
in “/opt/mozilla-updates/SOGo-plugins” according to each supported platform (Windows/Mac/Linux 32 and 64 bits).
''Note: By default, only the modules “sogo-integrator” and “sogo-connector” are activated with their integration, the other modules will require an activation via the server-manager.''
=== References ===
http://wiki.sogo.nu/TB-upgrade-service
https://developer.mozilla.org/en-US/docs/Mozilla/Setting_up_an_update_server
http://www.sogo.nu/en/support/documentation.html
http://wiki.contribs.org/Sogo
MozUS is a server update for the Mozilla products.
MozUS was thought to install in complement of SOGo and was developed to allow a fast maintenance and fast deployments of a SOGo/Thunderbird solution.
=== Requirements ===
SOGo requires SME 8 (Final release available since May 2012)
=== Optionnal Requirements ===
MozUS can function without SOGo being installed on your server.
To install SOGo : [http://wiki.contribs.org/Sogo SOGo].
It is not necessary to follow the procedure “Thunderbird Configuration”, this part is integrated in MozUS.
=== Principle of Operations ===
MozUS integrates two functionalities:
- Maintenance of the updates software Thunderbird and Firefox (ESR version only).
- Maintenance and deployments of the additional modules for Thunderbird (Firefox does not profit for the moment of this functionalitie).
=== Install ===
To complete
yum install smeserver-mozus
signal-event post-upgrade; signal-event reboot
=== Configuration ===
Once installed you will have access to a new section in the server-manager. This section comprises 3 new pages:
- Mozilla Update Server : You will be able to enable/disable MozUS, to authorize the updates for Thunderbird/Firefox, to authorize the major updates, the maintained versions and platforms.
- Planner of MozUS : Allows you to define the frequency of synchronization of “mirror” MozUS
- Complementary Modules: You allows to download the additional modules directly and to manage the modules to be maintained. The preset preferences via the module “sogo_integrator” are also defined here.
1.) Define your various parameters in the first panel.
2.) Define the interval of synchronization of “mirroir” - has interval regular where Mozus will check on the Mozilla servers if one or more new versions are available.
3.) Download the modules “sogo-integrator”, “sogo-connector” and “Lightnings” for the versions to be maintained here: [http://www.sogo.nu/en/downloads/frontends.html Inverse Sogo Frontends En]
4.) Download the additional modules that you wish deploy and define the parameters preset.
5.) Download [http://www.mozilla.org/en-US/thunderbird/organizations/all-esr.html Thunderbird ESR] and/or [http://www.mozilla.org/en-US/firefox/organizations/all.html Firefox ESR]
==== Thunderbird ====
Import the certificate of your SME as an authority of certifications (If not the synchronization of the modules will not be done).
The certificate is downloadable here: https://servername.domainname/SOGo-plugins/servername.domainname.crt (ex: https://www.example.com/SOGo-plugins/www.example.com.crt).
Configure the default account email before installing the module “sogo_integrator”.
In the server-manager, download the module “sogo-integrator” modified by MozUS and install it in Thunderbird.
Start again Thunderbird and let make.
==== Firefox ====
Import the certificate of your SME as an authority of certifications (If not the synchronization of the modules will not be done).
The certificate is downloadable here: https://servername.domainname/SOGo-plugins/servername.domainname.crt (ex: https://www.example.com/SOGo-plugins/www.example.com.crt).
In Firefox, go in the editor of configuration (accessible via 'about:config').
Create/Modify the following parameters :
app.update.url.override=https://servername.domainname/moz-updates/updates/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
app.update.auto=false
app.update.cert.checkAttributes=false
app.update.cert.requireBuiltIn=false
app.update.enabled=true
autoupdate.enabled=false
=== Command Line ===
MozUS is provided with two utilities :
==== /usr/bin/Mozmirup ====
Allows to manage the synchronization of the update and accepts two parameters :
/usr/bin/Mozmirup --update => Force a software research of the updates on the Mozilla servers.
/user/bin/Mozmirp --delete-obsolete => removes the files of updates not answering the criteria (also accessible since the first panel)
==== /usr/bin/Mozaddons ====
Allows to manage the integration of the additional modules and accepts two parameters :
/usr/bin/Mozaddons --update_sogo => makes it possible to update the modules 'sogo-integrator present.
/usr/bin/Mozaddons --add_update /path/addon.xpi <nowiki> [new name] </nowiki> => allows the addition or update of a module.
''The module path is an obligatory parameter while the parameter “new name” is optional.''
=== Optional Configuration ===
==== UseSSL ====
If your installation of SOGo does not comprise redirections HTTP towards HTTPS, you are likely to meet an error during the synchronization of the calendars/contact and additional module.
It is possible to modify the parameters of MozUS not to use “https”.
Disable the use of “https” and regenerate PHP files of Mozus:
db Mozus setprop Mozus UseSSL disabled
expand-template /opt/mozilla-updates/mirror/updates
expand-template /opt/mozilla-updates/SOGo-plugins/updates.php
/usr/bin/Mozaddons --update_sogo
=== Appendices ===
==== How Mozus integrates a module ====
The integration of a module by MozUS is done in the following way:
1.) The modules “xpi” are with the format zip, the first stage thus consists with decompress
2.) Once decompressed, one treats the file “install.rdf” which comprises following information:
- Name and Identifier of the module.
- Version of the module.
- Compatible Mozilla Products.
- Versions of the compatible products.
- Compatible platforms.
3.) According to the module, we modify the file “install.rdf” to remove useless information
- For a simple module we leave only information relating to Thunderbird
- For the module “sogo-integrator” we modify his internal version (with an aim of managing a single version for each modification carried out by MozUS). The files “extensions.rdf”, “Site.js” and “custom-preferences.js” are regenerated and to integrate in the module.
''Note: The treatment is carried out line by line. The file “install.rdf” is of type xml and the various developers do not conform all to the same format.''
So none the methods of parse tested before gave a conclusive result on the various modules.
4.) The module is then recomposed, a key east creates in the Mozus base. In same time, the module is copied in “/opt/mozilla-updates/Moz-AddOns” and symbolic links are created
in “/opt/mozilla-updates/SOGo-plugins” according to each supported platform (Windows/Mac/Linux 32 and 64 bits).
''Note: By default, only the modules “sogo-integrator” and “sogo-connector” are activated with their integration, the other modules will require an activation via the server-manager.''
=== References ===
http://wiki.sogo.nu/TB-upgrade-service
https://developer.mozilla.org/en-US/docs/Mozilla/Setting_up_an_update_server
http://www.sogo.nu/en/support/documentation.html
http://wiki.contribs.org/Sogo