Page History
| Table of Contents |
|---|
Introduction
For JS7 - Automated Deployment On Premises use of a Deployment Area is recommended.
...
The JS7 - Deployment Packaging requires the jq utility to be installed and available from the operating system.
Version 1.6 of jq is available from the js7_deploy.tar.gz archive, see Download section, and ships with the MIT license, see https://opensource.org/licenses/MIT.
No additional software requirements apply to a Deployment Area. The following resources should be considered:
...
- Security is the basic reason why the JS7 deployment scripts ship as shell scripts and not from a high level programming language that might require installation and updates. Transparency and adjustability are key. Users are free to modify deployment scripts at their will and to request changes within the scope of SOS professional services.
- The source of JS7 installation tarballs is a major concern. Basically the installer scripts for JS7 components offer to download components from the SOS Web Site on demand. Users are discouraged to make use of this feature for automated deployment. Instead, the JS7 components should be separately downloaded and checked that no tampered versions of the files have been downloaded.
- Good understanding of the deployment process and of the working of deployment scripts is key for security.
| Anchor | ||||
|---|---|---|---|---|
|
A tarball of the directories and scripts that make up the Deployment Area is provided per JS7 release.
...
...
Overview
Content Tools