CN117931261A - Modularized deployment method, device, equipment and storage medium - Google Patents
Modularized deployment method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN117931261A CN117931261A CN202410140724.XA CN202410140724A CN117931261A CN 117931261 A CN117931261 A CN 117931261A CN 202410140724 A CN202410140724 A CN 202410140724A CN 117931261 A CN117931261 A CN 117931261A
- Authority
- CN
- China
- Prior art keywords
- deployment
- module
- file
- target
- determining
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 59
- 238000013515 script Methods 0.000 claims abstract description 104
- 230000008569 process Effects 0.000 claims abstract description 21
- 238000009434 installation Methods 0.000 claims description 40
- 238000004590 computer program Methods 0.000 claims description 14
- 238000004422 calculation algorithm Methods 0.000 claims description 9
- 230000006835 compression Effects 0.000 claims description 6
- 238000007906 compression Methods 0.000 claims description 6
- 238000004806 packaging method and process Methods 0.000 claims description 5
- 230000008878 coupling Effects 0.000 abstract description 10
- 238000010168 coupling process Methods 0.000 abstract description 10
- 238000005859 coupling reaction Methods 0.000 abstract description 10
- 230000006870 function Effects 0.000 abstract description 8
- 230000009471 action Effects 0.000 description 21
- 238000004891 communication Methods 0.000 description 5
- 238000007726 management method Methods 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 4
- 238000012795 verification Methods 0.000 description 3
- 238000012360 testing method Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012858 packaging process Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000000630 rising effect Effects 0.000 description 1
- 230000008685 targeting Effects 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Abstract
The application discloses a modularized deployment method, a device, equipment and a storage medium, which relate to the technical field of computers and comprise the following steps: determining a target module needing to be deployed based on the received module deployment instruction; acquiring an extensible markup language file corresponding to a target module, and reading the extensible markup language file to determine an execution script and a target file corresponding to deployment operation; and determining a deployment operation type corresponding to the module deployment instruction, determining a corresponding deployment rule according to the deployment operation type, and running an execution script based on the deployment rule to process the target file so as to realize the deployment of the target module. Therefore, the logic of module deployment can be simplified, the operation logic of different modules with different functions is separated, the coupling is reduced, and only the changed files are needed to be downloaded and replaced during operation, so that the bandwidth pressure of a user is reduced, and the correctness and the stability of upgrading can be ensured based on the principles of modularized management, incremental upgrading and integrity checking.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a modular deployment method, apparatus, device, and storage medium.
Background
Upgrading and installing are important and complex problems in enterprise projects, upgrading is one of the most problematic components, existing upgrading installation methods require that software developers continuously update software to meet the demands of users along with the continuous change of the demands of the users in the process of upgrading the software, however, because the upgrading of the software may require redesign, test and deployment of the software, the combination of an excessively high upgrading frequency necessarily results in high upgrading cost, and frequent upgrading may result in unstable software and increased bandwidth pressure of the users.
Disclosure of Invention
In view of the above, the present invention is to provide a modular deployment method, apparatus, device and storage medium, which can simplify the logic of module deployment, separate the operation logic of different modules with different functions, reduce the coupling, only need to download and replace the changed file when operating, so as to reduce the bandwidth pressure of the user, and ensure the correctness and stability of the upgrade based on the principles of modular management, incremental upgrade and integrity verification. The specific scheme is as follows:
In a first aspect, the application discloses a modular deployment method, applied to a target platform, comprising:
determining a target module needing to be deployed based on the received module deployment instruction;
acquiring an extensible markup language file corresponding to the target module, and reading the extensible markup language file to determine an execution script and a target file corresponding to the deployment operation;
Determining a deployment operation type corresponding to the module deployment instruction, determining a corresponding deployment rule according to the deployment operation type, and running the execution script based on the deployment rule to process the target file so as to realize the deployment of the target module.
Optionally, the determining, based on the received module deployment instruction, the target module that needs to perform the deployment operation includes:
judging whether a module deployment instruction is received, if so, reading instruction information in the module deployment instruction to determine a target module needing to be deployed according to the instruction information.
Optionally, the obtaining the extensible markup language file corresponding to the target module and reading the extensible markup language file to determine an execution script and a target file corresponding to the deployment operation include:
acquiring an extensible markup language file corresponding to the target module from a preset file server;
and reading the code nodes in the extensible markup language file to determine target files in a to-be-processed file list and an execution script corresponding to the deployment operation.
Optionally, the determining a deployment operation type corresponding to the module deployment instruction, so as to determine a corresponding deployment rule according to the deployment operation type, and running the execution script based on the deployment rule to process the target file, so as to implement deployment of the target module, includes:
determining a deployment operation type corresponding to the module deployment instruction, if the deployment operation type is an installation operation, running a pre-installation script in the execution script to copy the target file to a preset installation catalog, and running a post-installation script in the execution script to end current deployment.
Optionally, the determining a deployment operation type corresponding to the module deployment instruction, so as to determine a corresponding deployment rule according to the deployment operation type, and running the execution script based on the deployment rule to process the target file, so as to implement deployment of the target module, includes:
determining a deployment operation type corresponding to the module deployment instruction, and determining a new added file and an updated file in the target file if the deployment operation type is an upgrade operation;
And running a pre-update script in the execution script to download the new added file and the updated file to a preset installation directory, and running an post-update script in the execution script to end the current deployment.
Optionally, the determining a deployment operation type corresponding to the module deployment instruction, so as to determine a corresponding deployment rule according to the deployment operation type, and running the execution script based on the deployment rule to process the target file, so as to implement deployment of the target module, includes:
And determining a deployment operation type corresponding to the module deployment instruction, if the deployment operation type is an unloading operation, running a pre-unloading script in the execution script to delete the target file, and running an post-unloading script in the execution script to end the current deployment.
Optionally, the modular deployment method further includes:
If a module packaging instruction is received, a module catalog of a module to be packaged is input, and all module files of the module to be packaged are determined through the module catalog;
And signing the module file to obtain a signed file, and compressing the signed file by using a preset compression algorithm to obtain a compressed module.
In a second aspect, the application discloses a modular deployment apparatus for use with a target platform, comprising:
the target determining module is used for determining a target module needing to be subjected to deployment operation based on the received module deployment instruction;
The file reading module is used for acquiring the extensible markup language file corresponding to the target module and reading the extensible markup language file to determine an execution script and a target file corresponding to the deployment operation;
The deployment execution module is used for determining a deployment operation type corresponding to the module deployment instruction, determining a corresponding deployment rule according to the deployment operation type, and running the execution script based on the deployment rule to process the target file so as to realize the deployment of the target module.
In a third aspect, the present application discloses an electronic device, comprising:
A memory for storing a computer program;
a processor for executing the computer program to implement the modular deployment method as described above.
In a fourth aspect, the application discloses a computer readable storage medium for storing a computer program which, when executed by a processor, implements a modular deployment method as described above.
In the application, a target module needing to be deployed is determined based on a received module deployment instruction; then, an extensible markup language file corresponding to the target module is obtained, and the extensible markup language file is read to determine an execution script and a target file corresponding to the deployment operation; and finally, determining a deployment operation type corresponding to the module deployment instruction, determining a corresponding deployment rule according to the deployment operation type, and running the execution script based on the deployment rule to process the target file so as to realize the deployment of the target module. Therefore, according to the method, after the module deployment instruction is received, the target module to be deployed is determined, then the execution script and the target file used for the deployment operation are determined by reading the extensible markup language file corresponding to the target module, and then only the corresponding script is needed according to the operation type of the deployment operation, so that the target file is processed, and the deployment of the target file is realized. Therefore, the logic of module deployment can be simplified, the operation logic of different modules with different functions is separated, the coupling is reduced, and only the changed files are needed to be downloaded and replaced during operation, so that the bandwidth pressure of a user is reduced, and the correctness and the stability of upgrading can be ensured based on the principles of modularized management, incremental upgrading and integrity checking.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present invention, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a modular deployment method of the present disclosure;
FIG. 2 is a flow chart of a specific modular packaging process of the present disclosure;
FIG. 3 is a flow chart of a specific modular installation of the present disclosure;
FIG. 4 is a flowchart of a specific modular update of the present disclosure;
FIG. 5 is a specific modular unloading flow chart of the present disclosure;
FIG. 6 is a schematic diagram of a modular deployment apparatus of the present disclosure;
fig. 7 is a block diagram of an electronic device according to the present disclosure.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
In the prior art, because software upgrading may require redesign, testing and deployment of the software, combining too high an upgrade frequency necessarily results in high upgrade costs, and frequent upgrades may result in instability of the software and an increase in user bandwidth pressure.
In order to overcome the technical problems, the application discloses a modularized deployment method, a modularized deployment device, modularized deployment equipment and a modularized deployment storage medium, which can simplify the logic of module deployment, separate the operation logic of different modules with different functions, reduce coupling, only need to download and replace changed files when in operation so as to reduce the bandwidth pressure of a user, and can ensure the correctness and stability of upgrading based on the principles of modularized management, incremental upgrading and integrity verification.
Referring to fig. 1, an embodiment of the present invention discloses a modular deployment method, which is applied to a target platform, and includes:
and S11, determining a target module needing to be subjected to deployment operation based on the received module deployment instruction.
In this embodiment, in a target platform that needs to perform modular deployment, a target module that needs to perform deployment operation needs to be determined according to a received modular deployment instruction, specifically, whether a module deployment instruction is received needs to be determined according to a preset polling period, the polling period may be set by a user according to the user's needs, and if the module deployment instruction is received, the module deployment instruction may be analyzed to determine instruction information in the read module deployment instruction, and determine, according to the read instruction information, the target module that needs to perform deployment operation.
The modular deployment method further includes: if a module packaging instruction is received, a module catalog of a module to be packaged is input, and all module files of the module to be packaged are determined through the module catalog; and signing the module file to obtain a signed file, and compressing the signed file by using a preset compression algorithm to obtain a compressed module. That is, as shown in fig. 2, after receiving a module packaging instruction, a module directory to be packaged may be input, then all module files of a module to be packaged are determined according to information in the module directory, then the module files are signed in sequence, and then the signed files are compressed by a 7z algorithm, because the 7z algorithm has an extremely high compression ratio, the files are compressed by the 7z algorithm, so that consumption of bandwidth resources of the files to users in a transmission process can be effectively reduced, safety of executing deployment operation is improved by signing the files, the compressed package is ensured not to be tampered in the transmission process, and the coupling degree of installation and unloading between the modules can be reduced, thereby reducing maintenance cost.
And step S12, acquiring an extensible markup language file corresponding to the target module, and reading the extensible markup language file to determine an execution script and a target file corresponding to the deployment operation.
In this embodiment, after determining the target module to be deployed, an extensible markup language file corresponding to the target module needs to be obtained, and the extensible markup language file needs to be read to determine an execution script and the target file corresponding to the deployment operation, specifically, the extensible markup language file corresponding to the target module may be obtained from a preset file server, and it needs to be described that the extensible markup language file is a file in XML format, and the XML is different from a traditional database, where the database provides more powerful data storage and analysis capability, for example: data indexing, sorting, searching, correlation consistency and the like, but XML represents data in a tree structure form, is very suitable for describing semi-structured data, and has advantages in data transmission. In this embodiment, a module description file supp.xml is relied upon when the deployment of the module is performed, and detailed information of the module, file description information, lua script executed when the upgrade is deployed, and the like are described in the file. Specifically, the supp.xml file contains a number of code nodes, wherein the config nodes can define personalized contents of the installation package, such as the name of the installation package, the company name, information of the OEM, and the like; the translate node may define translation configurations related to internationalization of installation packages, and may use different languages in different countries. The product node describes the detailed information of the installation package, including the version number, the installation package name, the installation path, the size and the like; scripts node: the node describes a lua script which can be executed by the installation package, and the lua script can perform related operations of files, registries, processes and configuration files and is used for assisting the installation package to execute different actions under different conditions; actions node: the borrowing point describes which lua scripts the installation package can execute in different phases; the item node describes file information contained in the installation package, which will be released under the installation directory at installation time and deleted from the installation directory at uninstallation time. Based on these nodes defined in the supp.xml file, the corresponding code nodes may be read when running the XML file to determine the target file in the pending file list and the execution script corresponding to the deployment operation. It should be further noted that, the target file is a file corresponding to a deployment operation to be executed, for example, when an uninstall operation is executed, the target file is a file to be deleted, and when an upgrade operation is executed, the target file is a file to be updated and replaced.
Step S13, determining a deployment operation type corresponding to the module deployment instruction, determining a corresponding deployment rule according to the deployment operation type, and running the execution script based on the deployment rule to process the target file so as to realize the deployment of the target module.
In this embodiment, a corresponding script is executed according to the type of the deployment operation, and a corresponding target file is processed to implement deployment of the module. It should be noted that, the Lua script may be executed in combination in different phases, and the present system mainly defines three phases of "install", "uninstall" and "upgrade", and each phase is divided into two occasions of "before" and "after" execution. Lua scripts are defined in scripts nodes, and a plurality of scripts with different functions can be inserted. Taking a certain offload script as an example, the script format is as follows:
Wherein, the name attribute is the unique identification of the script in the system, and the system can find the script and execute the script through the identification; the desc attribute is descriptive information of the script and gives a friendly prompt to the user.
The configuration format is as follows:
<actions>
<action index＝"0"id＝"base.action.after.install"name＝"base.lua.after.install"oppor＝"after"scope＝"install"desc＝" Post-installation execution "/>
<action index＝"0"id＝"base.action.after.update"name＝"base.lua.after.update"oppor＝"after"scope＝"update"desc＝" Execution after rising of the grade "/>
<action index＝"100"id＝"base.action.before.uninstall"name＝"base.lua.before.uninstall"oppor＝"before"scope＝"uninstall"desc＝" Execution before offloading "/>
<action index＝"1000"id＝"base.action.start"name＝"base.uesstart.action"oppor＝"after"scope＝"update|install"/>
<action index＝"1"id＝"base.action.stop"name＝"base.uesstop.action"oppor＝"before"scope＝"update|uninstall"/>
</actions>
Wherein Scope: the attribute represents the execution stage, the install stage, the update stage and the uninstall uninstall stage; oppor: the attribute represents the execution time, the execution is performed before the after stage and the execution is performed after the before stage; name: lua script representing the action reference, id: representing the unique id of the action within the system.
The method is divided into three specific implementation scenes according to three different deployment operation types.
In a first specific implementation scenario, as shown in fig. 3, if the type of the deployment operation is an installation operation, a supp.xml file needs to be pulled from a file server, a file list in the supp.xml is read, a corresponding target file needing to be installed is downloaded, then a pre-installation script in the execution script is executed to copy the target file to a preset installation catalog, and a post-installation script in the execution script is executed to end the current deployment.
In a second specific implementation scenario, as shown in fig. 4, if the deployment operation type is an upgrade operation, determining a new added file and an updated file in a target file, and the upgrade procedure is a link of software update, where in order to reduce the client bandwidth, the upgrade is performed by adopting an incremental update mode according to the present invention, specifically, a supp.xml file needs to be pulled from a file server, a file list in the supp.xml is read, then differences of the file list are compared, the new added, deleted and updated file is found out, then a pre-update script in an execution script is run to download the new added file and the updated file to a preset installation directory, and an updated script in the execution script is run to end the current deployment.
In a third specific implementation scenario, as shown in fig. 5, if the type of the deployment operation is an uninstall operation, a supp.xml file needs to be pulled from a file server, a file list in the supp.xml is read, then a target file to be deleted is determined, then a pre-uninstall script in an execution script is run to delete the target file, and a post-uninstall script in the execution script is run to end the current deployment.
Therefore, in this embodiment, the target module that needs to be deployed is determined based on the received module deployment instruction; then, an extensible markup language file corresponding to the target module is obtained, and the extensible markup language file is read to determine an execution script and a target file corresponding to the deployment operation; and finally, determining a deployment operation type corresponding to the module deployment instruction, determining a corresponding deployment rule according to the deployment operation type, and running the execution script based on the deployment rule to process the target file so as to realize the deployment of the target module. Therefore, according to the method, after the module deployment instruction is received, the target module to be deployed is determined, then the execution script and the target file used for the deployment operation are determined by reading the extensible markup language file corresponding to the target module, and then only the corresponding script is needed according to the operation type of the deployment operation, so that the target file is processed, and the deployment of the target file is realized. Therefore, the logic of module deployment can be simplified, the operation logic of different modules with different functions is separated, the coupling is reduced, and only the changed files are needed to be downloaded and replaced during operation, so that the bandwidth pressure of a user is reduced, the correctness and the stability of upgrading can be ensured based on the principles of modularized management, incremental upgrading and integrity checking, and the coupling degree of installation and unloading between the modules can be reduced, so that the maintenance cost is reduced.
Referring to fig. 6, an embodiment of the present invention discloses a modular deployment apparatus, applied to a target platform, including:
a target determining module 11, configured to determine a target module that needs to perform a deployment operation based on the received module deployment instruction;
A file reading module 12, configured to obtain an extensible markup language file corresponding to the target module, and read the extensible markup language file to determine an execution script and a target file corresponding to the deployment operation;
The deployment execution module 13 is configured to determine a deployment operation type corresponding to the module deployment instruction, determine a corresponding deployment rule according to the deployment operation type, and run the execution script based on the deployment rule to process the target file, so as to implement deployment of the target module.
Therefore, in this embodiment, the target module that needs to be deployed is determined based on the received module deployment instruction; then, an extensible markup language file corresponding to the target module is obtained, and the extensible markup language file is read to determine an execution script and a target file corresponding to the deployment operation; and finally, determining a deployment operation type corresponding to the module deployment instruction, determining a corresponding deployment rule according to the deployment operation type, and running the execution script based on the deployment rule to process the target file so as to realize the deployment of the target module. Therefore, according to the method, after the module deployment instruction is received, the target module to be deployed is determined, then the execution script and the target file used for the deployment operation are determined by reading the extensible markup language file corresponding to the target module, and then only the corresponding script is needed according to the operation type of the deployment operation, so that the target file is processed, and the deployment of the target file is realized. Therefore, the logic of module deployment can be simplified, the operation logic of the modules with different functions is separated, the coupling is reduced, only the files with changed functions are needed to be downloaded and replaced during operation, so that the bandwidth pressure of a user is reduced, the coupling degree of installation and unloading between the modules can be reduced, the maintenance cost is reduced, the correctness and the stability of the upgrade can be ensured based on the principles of modularized management, incremental upgrade and integrity verification, and the coupling degree of installation and unloading between the modules can be reduced, so that the maintenance cost is reduced.
In some embodiments, the targeting module 11 may specifically include:
The information reading unit is used for judging whether a module deployment instruction is received or not, and if the module deployment instruction is received, the instruction information in the module deployment instruction is read so as to determine a target module needing to be deployed according to the instruction information.
In some embodiments, the file reading module 12 may specifically include:
The file acquisition unit is used for acquiring the extensible markup language file corresponding to the target module from a preset file server;
and the node reading unit is used for reading the code nodes in the extensible markup language file to determine target files in a file list to be processed and execution scripts corresponding to the deployment operation.
In some embodiments, the deployment execution module 13 may specifically include:
The first deployment unit is used for determining a deployment operation type corresponding to the module deployment instruction, if the deployment operation type is an installation operation, running a pre-installation script in the execution script to copy the target file to a preset installation catalog, and running a post-installation script in the execution script to finish current deployment.
In some embodiments, the deployment execution module 13 may specifically include:
The file determining unit is used for determining a deployment operation type corresponding to the module deployment instruction, and determining a new added file and an updated file in the target file if the deployment operation type is an upgrading operation;
The second deployment unit is used for running the pre-update script in the execution script to download the newly added file and the updated file to a preset installation catalog, and running the post-update script in the execution script to finish the current deployment.
In some embodiments, the deployment execution module 13 may specifically include:
The third deployment unit is used for determining a deployment operation type corresponding to the module deployment instruction, if the deployment operation type is an unloading operation, running a pre-unloading script in the execution script to delete the target file, and running a post-unloading script in the execution script to end the current deployment.
In some embodiments, the modular deployment apparatus may further comprise:
the module file determining unit is used for inputting a module catalog of a module to be packaged if a module packaging instruction is received, so as to determine all module files of the module to be packaged through the module catalog;
The module compression unit signs the module file to obtain a signed file, and compresses the signed file by using a preset compression algorithm to obtain a compressed module.
Further, the embodiment of the present application further discloses an electronic device, and fig. 7 is a block diagram of an electronic device 20 according to an exemplary embodiment, where the content of the figure is not to be considered as any limitation on the scope of use of the present application.
Fig. 7 is a schematic structural diagram of an electronic device 20 according to an embodiment of the present application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input output interface 25, and a communication bus 26. Wherein the memory 22 is configured to store a computer program that is loaded and executed by the processor 21 to implement the relevant steps of the modular deployment method disclosed in any of the foregoing embodiments. In addition, the electronic device 20 in the present embodiment may be specifically an electronic computer.
In this embodiment, the power supply 23 is configured to provide an operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and an external device, and the communication protocol to be followed is any communication protocol applicable to the technical solution of the present application, which is not specifically limited herein; the input/output interface 25 is used for acquiring external input data or outputting external output data, and the specific interface type thereof may be selected according to the specific application requirement, which is not limited herein.
The memory 22 may be a carrier for storing resources, such as a read-only memory, a random access memory, a magnetic disk, or an optical disk, and the resources stored thereon may include an operating system 221, a computer program 222, and the like, and the storage may be temporary storage or permanent storage.
The operating system 221 is used for managing and controlling various hardware devices on the electronic device 20 and the computer program 222, which may be Windows Server, netware, unix, linux, etc. The computer program 222 may further comprise a computer program capable of performing other specific tasks in addition to the computer program capable of performing the modular deployment method performed by the electronic device 20 disclosed in any of the embodiments described above.
Further, the application also discloses a computer readable storage medium for storing a computer program; wherein the computer program, when executed by a processor, implements the modular deployment method disclosed previously. For specific steps of the method, reference may be made to the corresponding contents disclosed in the foregoing embodiments, and no further description is given here.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, so that the same or similar parts between the embodiments are referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software modules may be disposed in Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing has outlined rather broadly the more detailed description of the application in order that the detailed description of the application that follows may be better understood, and in order that the present principles and embodiments may be better understood; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.
Claims (10)
1. A modular deployment method, applied to a target platform, comprising:
determining a target module needing to be deployed based on the received module deployment instruction;
acquiring an extensible markup language file corresponding to the target module, and reading the extensible markup language file to determine an execution script and a target file corresponding to the deployment operation;
Determining a deployment operation type corresponding to the module deployment instruction, determining a corresponding deployment rule according to the deployment operation type, and running the execution script based on the deployment rule to process the target file so as to realize the deployment of the target module.
2. The modular deployment method of claim 1, wherein the determining a target module that requires a deployment operation based on the received module deployment instruction comprises:
judging whether a module deployment instruction is received, if so, reading instruction information in the module deployment instruction to determine a target module needing to be deployed according to the instruction information.
3. The modular deployment method of claim 1, wherein the obtaining the extensible markup language file corresponding to the target module and reading the extensible markup language file to determine the execution script and the target file corresponding to the deployment operation comprises:
acquiring an extensible markup language file corresponding to the target module from a preset file server;
and reading the code nodes in the extensible markup language file to determine target files in a to-be-processed file list and an execution script corresponding to the deployment operation.
4. The modular deployment method of claim 1, wherein the determining the type of deployment operation corresponding to the module deployment instruction to determine a corresponding deployment rule according to the type of deployment operation, and running the execution script based on the deployment rule to process the target file to implement the deployment of the target module, comprises:
determining a deployment operation type corresponding to the module deployment instruction, if the deployment operation type is an installation operation, running a pre-installation script in the execution script to copy the target file to a preset installation catalog, and running a post-installation script in the execution script to end current deployment.
5. The modular deployment method of claim 1, wherein the determining the type of deployment operation corresponding to the module deployment instruction to determine a corresponding deployment rule according to the type of deployment operation, and running the execution script based on the deployment rule to process the target file to implement the deployment of the target module, comprises:
determining a deployment operation type corresponding to the module deployment instruction, and determining a new added file and an updated file in the target file if the deployment operation type is an upgrade operation;
And running a pre-update script in the execution script to download the new added file and the updated file to a preset installation directory, and running an post-update script in the execution script to end the current deployment.
6. The modular deployment method of claim 1, wherein the determining the type of deployment operation corresponding to the module deployment instruction to determine a corresponding deployment rule according to the type of deployment operation, and running the execution script based on the deployment rule to process the target file to implement the deployment of the target module, comprises:
And determining a deployment operation type corresponding to the module deployment instruction, if the deployment operation type is an unloading operation, running a pre-unloading script in the execution script to delete the target file, and running an post-unloading script in the execution script to end the current deployment.
7. The modular deployment method of any of claims 1-6, further comprising:
If a module packaging instruction is received, a module catalog of a module to be packaged is input, and all module files of the module to be packaged are determined through the module catalog;
And signing the module file to obtain a signed file, and compressing the signed file by using a preset compression algorithm to obtain a compressed module.
8. A modular deployment apparatus for application to a target platform, comprising:
the target determining module is used for determining a target module needing to be subjected to deployment operation based on the received module deployment instruction;
The file reading module is used for acquiring the extensible markup language file corresponding to the target module and reading the extensible markup language file to determine an execution script and a target file corresponding to the deployment operation;
The deployment execution module is used for determining a deployment operation type corresponding to the module deployment instruction, determining a corresponding deployment rule according to the deployment operation type, and running the execution script based on the deployment rule to process the target file so as to realize the deployment of the target module.
9. An electronic device, comprising:
A memory for storing a computer program;
A processor for executing the computer program to implement the modular deployment method of any of claims 1 to 7.
10. A computer readable storage medium for storing a computer program which when executed by a processor implements the modular deployment method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410140724.XA CN117931261A (en) | 2024-02-01 | 2024-02-01 | Modularized deployment method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410140724.XA CN117931261A (en) | 2024-02-01 | 2024-02-01 | Modularized deployment method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117931261A true CN117931261A (en) | 2024-04-26 |
Family
ID=90757472
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410140724.XA Pending CN117931261A (en) | 2024-02-01 | 2024-02-01 | Modularized deployment method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117931261A (en) |
-
2024
- 2024-02-01 CN CN202410140724.XA patent/CN117931261A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7263699B2 (en) | Preparation of a software configuration using an XML type programming language | |
| US6772083B2 (en) | Computer program test configurations with data containers and test scripts | |
| CN108388445B (en) | Continuous integration method based on 'platform + application' mode | |
| US7814484B2 (en) | System and method for web application extensibility | |
| US7549148B2 (en) | Self-describing software image update components | |
| US5761510A (en) | Method for error identification in a program interface | |
| US6748591B1 (en) | Method, system, program, and data structures for loading programs into a runtime environment | |
| EP1672489A2 (en) | Language-Neutral And Language-Specific Installation Packages For Software Setup | |
| US20060026591A1 (en) | Method and apparatus for providing a pluggable and extendable J2EE architecture | |
| US8997085B2 (en) | Image delta-based upgrade of complex stack in software appliance | |
| CN109766099B (en) | Front-end source code compiling method and device, storage medium and computer equipment | |
| WO2001093030A1 (en) | Method for resolving dependency conflicts among multiple operative entities within a computing environment | |
| CN111061643B (en) | SDK cluster compatibility detection method and device, electronic equipment and storage medium | |
| US20060031827A1 (en) | System, apparatus and method of assisting with software product update installations | |
| CN115185550A (en) | Service deployment method, device, computer equipment and storage medium | |
| US20060136906A1 (en) | Software product installation facilitation | |
| CN115794214B (en) | Application module metadata management method, device, storage medium and apparatus | |
| CN116069366A (en) | Client application program updating method and device, storage medium and electronic equipment | |
| CN117931261A (en) | Modularized deployment method, device, equipment and storage medium | |
| CN113448793A (en) | System monitoring method and device compatible with multiple operating systems | |
| CN115437643A (en) | Project code conversion method, device, equipment and storage medium | |
| CN106997364A (en) | A kind of application resource detection method and device of terminal | |
| CN115729590A (en) | Service deployment method, device, equipment and computer readable storage medium | |
| CN109697080B (en) | Online upgrading method for operating system of Internet of things | |
| CN113885924A (en) | XML configuration file upgrading method and device and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination |