Packaging Specifications of Software Packages
JAR and WAR packages can be directly uploaded.
For other types of software packages, such as ZIP packages:
The software package name must be in the following format: software name+suffix. The suffix must be .tar.gz, .tar, or .zip.
The extension must be consistent with the package compression mode. Otherwise, the software package cannot be decompressed.
Directory Structure
For decompressed software packages, ensure that lifecycle command scripts can be normally executed.
The following software package directory structure is recommended:
|- bin |- xxx.tar.gz |- xxx.bin |- scripts |- install.sh |- start.sh ...
Currently, you are advised not to store decompressed software packages in the top-level directory. Otherwise, when you need to modify lifecycle execution commands, you have to use the top-level directory name to find the corresponding scripts.
Directory |
Description |
---|---|
bin |
Stores execution information about software packages, such as executable bin files and dependent compressed packages. |
scripts |
Stores lifecycle scripts. When creating an application, you can specify execution commands based on the location of lifecycle scripts. For example, specify bash scripts/install.sh in the install phase to run the installation script. Lifecycles supported by software package applications are as follows:
|
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot