CN110750242B - File deployment method, system, medium and electronic equipment - Google Patents
File deployment method, system, medium and electronic equipment Download PDFInfo
- Publication number
- CN110750242B CN110750242B CN201910885726.0A CN201910885726A CN110750242B CN 110750242 B CN110750242 B CN 110750242B CN 201910885726 A CN201910885726 A CN 201910885726A CN 110750242 B CN110750242 B CN 110750242B
- Authority
- CN
- China
- Prior art keywords
- instruction
- file
- description file
- instruction description
- type
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The disclosure provides a method, a system, a medium and electronic equipment for deploying files. The method comprises the following steps: acquiring a first instruction description file change message sent by an instruction file management module through a network hook interface based on a preset network hook interface message rule; generating a pulling instruction meeting a preset network hook interface pulling rule based on the triggering of the first instruction description file changing message; acquiring a first instruction description file managed in the instruction file management module through a network hook interface according to the pulling instruction; acquiring a first instruction executable file according to the file type of the first instruction description file and the first instruction description file, forcibly closing the process of a second instruction executable file associated with the first instruction executable file, and sending starting information for starting the first instruction executable file according to a preset starting rule to a daemon module. The method and the device improve deployment efficiency and reduce error rate.
Description
Technical Field
The present disclosure relates to the field of file deployment, and in particular, to a method, a system, a medium, and an electronic device for deploying a file.
Background
The system framework is a technical implementation framework for the determined requirements, well plans, and uses complete sets of complete tools to complete tasks in the planning step. In an abstract sense, it is a computer system architecture, or computer architecture, that is the highest level of concept of a system in its environment. It determines the engagement between a piece of computer hardware and software. In particular, computer architecture refers to the concept and architecture of computer system design, depicting the design principles of a computer in practice. It determines the component functions of a computer design, interfaces between components and computer architecture emphasis "central functions responsible for computer architecture: compute "run actions and memory accesses within the central processor.
Currently, system frameworks are developed in multiple ways along with business requirements, and more single-machine architecture services corresponding to smaller requirements or asynchronous tasks are provided. The single machine architecture refers to an architecture scheme that services (front-end pages, back-end services and databases) of an application are all deployed on one server. Because the deployment and operation of the single-machine architecture are simpler, a heavyweight automatic deployment scheme is not needed, and therefore, manual deployment is still performed in most cases. For example, a deployment script is manually written and a stand-alone service deployment is performed by running script commands. However, manual deployment has the problems of high error rate and low efficiency.
Disclosure of Invention
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
The present disclosure aims to provide a method, a system, a medium and an electronic device for deploying files, which can solve at least one technical problem mentioned above. The specific scheme is as follows:
according to a specific embodiment of the present disclosure, in a first aspect, the present disclosure provides a method for deploying a file, including:
acquiring a first instruction description file change message sent by an instruction file management module through a network hook interface based on a preset network hook interface message rule;
generating a pulling instruction meeting a preset network hook interface pulling rule based on the triggering of the first instruction description file changing message;
acquiring a first instruction description file managed in the instruction file management module through a network hook interface according to the pulling instruction;
acquiring a first instruction executable file according to the file type of the first instruction description file and the first instruction description file, forcibly closing the process of a second instruction executable file associated with the first instruction executable file, and sending starting information for starting the first instruction executable file according to a preset starting rule to a daemon module.
According to a second aspect of particular embodiments of the present disclosure, the present disclosure provides a system for deploying a file, comprising:
an instruction file management module configured to: managing a first instruction description file, and sending a first instruction description file change message to a network hook module through a network hook interface based on a preset network hook interface message rule;
the network hook module is configured to: acquiring the first instruction description file change message through a network hook interface based on a preset network hook interface message rule; generating a pulling instruction meeting a preset network hook interface pulling rule based on the triggering of the first instruction description file changing message; acquiring a first instruction description file managed in the instruction file management module through a network hook interface according to the pulling instruction; acquiring a first instruction executable file according to the file type of the first instruction description file and the first instruction description file, forcibly closing a second instruction executable file associated with the first instruction executable file, and sending starting information for starting the first instruction executable file to a daemon module;
the daemon module is configured to: and receiving the starting information, and starting the first instruction executable file according to the preset starting rule based on the triggering of the starting information.
According to a third aspect of the disclosure, there is provided a computer readable storage medium having stored thereon a computer program which when executed by a processor implements a method of deploying a file as claimed in any of the first aspects.
According to a fourth aspect of the present disclosure, there is provided an electronic device comprising: one or more processors; storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the method of deploying a file as claimed in any of the first aspects.
Compared with the prior art, the scheme of the embodiment of the disclosure has at least the following beneficial effects:
the disclosure provides a method, a system, a medium and electronic equipment for deploying files. The method comprises the following steps: acquiring a first instruction description file change message sent by an instruction file management module through a network hook interface based on a preset network hook interface message rule; generating a pulling instruction meeting a preset network hook interface pulling rule based on the triggering of the first instruction description file changing message; acquiring a first instruction description file managed in the instruction file management module through a network hook interface according to the pulling instruction; acquiring a first instruction executable file according to the file type of the first instruction description file and the first instruction description file, forcibly closing the process of a second instruction executable file associated with the first instruction executable file, and sending starting information for starting the first instruction executable file according to a preset starting rule to a daemon module. The invention provides a lightweight single machine architecture automatic deployment scheme based on a process daemon principle, which realizes automatic deployment after the instruction description file is submitted, and the access mode is simple and controllable. The deployment efficiency is improved, and the error rate is reduced.
Drawings
The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale. In the drawings:
FIG. 1 illustrates a flow chart of a method of deploying a file according to an embodiment of the disclosure;
FIG. 2 illustrates a block diagram of a system for deploying files according to an embodiment of the disclosure;
fig. 3 illustrates a schematic diagram of an electronic device connection structure according to an embodiment of the present disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure have been shown in the accompanying drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustration purposes only and are not intended to limit the scope of the present disclosure.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order and/or performed in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
The term "including" and variations thereof as used herein are intended to be open-ended, i.e., including, but not limited to. The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. Related definitions of other terms will be given in the description below.
It should be noted that the terms "first," "second," and the like in this disclosure are merely used to distinguish between different devices, modules, or units and are not used to define an order or interdependence of functions performed by the devices, modules, or units.
It should be noted that references to "one", "a plurality" and "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be understood as "one or more" unless the context clearly indicates otherwise.
The names of messages or information interacted between the various devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.
Alternative embodiments of the present disclosure are described in detail below with reference to the drawings.
The first embodiment provided in the present disclosure is an embodiment of a method for deploying a file.
Embodiments of the present disclosure are described in detail below with reference to fig. 1, where fig. 1 is a flowchart of a method for deploying a file according to an embodiment of the present disclosure.
Step S101, a first instruction description file change message sent by an instruction file management module is obtained through a network hook interface based on a preset network hook interface message rule.
In web page development, web hooks (webhooks) are a method to add or alter web page behavior by custom callback functions. These callbacks may be saved, modified, and managed by third party users and developers associated with the original website or application. Network hooks are typically activated by certain events or messages, often used to activate the build operations of the continuously integrated system or to alert the defect tracking management system. Because web hooks use HTTP, they can be seamlessly integrated into a web page service without adding new infrastructure. The network hook is provided with an interface which inputs and outputs data with the outside through the data transmission specification of the network hook interface.
The instruction file management module is mainly used for managing instruction description files (such as source code files or script files). For example, the instruction file management module is a Gitlab code hosting platform, wherein the Git tool is a code management tool in the Gitlab code hosting platform; when the instruction description file is placed in the Git tool, the Gitlab code hosting platform automatically sends an instruction description file change message to the web hook interface.
The instruction description file change message is generated according to a preset network hook interface message rule.
The preset network hook interface message rule is configured in advance based on the data transmission specification of the network hook interface.
Meanwhile, the Webhook receives an instruction description file change message based on a preset network hook interface message rule.
Step S102, based on the triggering of the first instruction description file change message, a pulling instruction meeting the pulling rule of the preset network hook interface is generated.
The preset network hook interface pulling rule is configured in advance based on the data transmission specification of the network hook interface.
Step S103, obtaining a first instruction description file managed in the instruction file management module through a network hook interface according to the pull instruction.
Step S104, a first instruction executable file is obtained according to the file type of the first instruction description file and the first instruction description file, the process of a second instruction executable file associated with the first instruction executable file is forcedly closed, and starting information for starting the first instruction executable file according to a preset starting rule is sent to a daemon module.
The file type of the first instruction description file comprises a script type.
The script file is an extension of a batch file, is a program stored in a plain text, and is generally a combination of a series of determined control computer operation actions, in which a certain logic branch can be implemented.
The script file is similar to a batch file in the DOS operating system, and it can combine different commands and execute automatically and continuously in a defined order. The script file is a text file that a user can use any text editor to create.
Typically, script types are discernable through the suffix of the script file. For example, the file with suffix name cfg, csh, sh, py or the like belongs to the script type file.
The method for acquiring the first instruction executable file according to the file type of the first instruction description file and the first instruction description file comprises the following steps:
and step S104-11, judging whether the file type of the first instruction description file meets script type conditions.
And step S104-12, if yes, judging the first instruction description file as the first instruction executable file.
If so, the first instruction description file is a script file.
The file type of the first instruction description file includes a compilable type.
The compilable file must be compiled by a compiler to generate the executable file.
The compilable type can be distinguished by the suffix of the script file. For example, files with suffix names c, vbp, res, h and the like all belong to compilable type files.
The method for acquiring the first instruction executable file according to the file type of the first instruction description file and the first instruction description file comprises the following steps:
step S104-21, judging whether the file type of the first instruction description file meets the condition of the compilable type.
And step S104-22, if yes, compiling the first instruction description file and generating the first instruction executable file.
The second instruction executable file associated with the first instruction executable file refers to an executable file with the same file name as the second instruction executable file. That is, the processes generated by the second instruction executable and the first instruction executable have the same process ID.
The process of the second instruction executable file associated with the first instruction executable file is forced to be closed, the purpose of which is to start the first instruction executable file by the daemon module. For example, an exit instruction invoking the system may force a specified process to be shut down.
The preset starting rule is a rule that the daemon module starts the first instruction executable file. This rule is a preconfigured rule.
Daemon modules are a background service process, a longer-lived process, typically controlled independently of the terminal and periodically performing certain tasks or waiting to process certain events that occur.
For example, the daemon module is a supervisor daemon process, and when the supervisor daemon process obtains starting information (such as a process list of a supervisor daemon process real-time monitoring system, when obtaining information that a specified process is not in a system process list, the starting information is obtained), the specified process is started according to a preset starting rule configured.
The embodiment of the disclosure provides a lightweight single machine architecture automatic deployment scheme based on a process daemon principle, realizes automatic deployment after the instruction description file is submitted, and has a simple and controllable access mode. The deployment efficiency is improved, and the error rate is reduced.
Corresponding to the first embodiment provided by the present disclosure, the present disclosure also provides a second embodiment, namely a system for deploying files. Since the second embodiment is substantially similar to the first embodiment, the description is relatively simple, and the relevant portions will be referred to the corresponding descriptions of the first embodiment. The system embodiments described below are merely illustrative.
FIG. 2 illustrates an embodiment of a system for deploying a file provided by the present disclosure. FIG. 2 illustrates a block diagram of a system for deploying files according to an embodiment of the disclosure.
Referring to fig. 2, the present disclosure provides a system for deploying a file, including:
an instruction file management module configured to: managing a first instruction description file, and sending a first instruction description file change message to a network hook module through a network hook interface based on a preset network hook interface message rule;
the network hook module is configured to: acquiring the first instruction description file change message through a network hook interface based on a preset network hook interface message rule; generating a pulling instruction meeting a preset network hook interface pulling rule based on the triggering of the first instruction description file changing message; acquiring a first instruction description file managed in the instruction file management module through a network hook interface according to the pulling instruction; acquiring a first instruction executable file according to the file type of the first instruction description file and the first instruction description file, forcibly closing a second instruction executable file associated with the first instruction executable file, and sending starting information for starting the first instruction executable file to a daemon module;
the daemon module is configured to: and receiving the starting information, and starting the first instruction executable file according to the preset starting rule based on the triggering of the starting information.
Optionally, the instruction file management module further includes: configuring a preset network hook interface message rule; and configuring a preset network hook interface pulling rule.
Optionally, the daemon module further comprises: and configuring a preset starting rule.
Optionally, the network hook module includes: a first judgment unit and a second judgment unit;
the first judging unit is configured to: judging whether the file type of the first instruction description file meets script type conditions or not; if yes, judging the first instruction description file as the first instruction executable file;
the second judging unit is configured to: judging whether the file type of the first instruction description file meets a compilable type condition or not; if yes, compiling the first instruction description file and generating the first instruction executable file.
The embodiment of the disclosure provides a lightweight single machine architecture automatic deployment scheme based on a process daemon principle, realizes automatic deployment after the instruction description file is submitted, and has a simple and controllable access mode. The deployment efficiency is improved, and the error rate is reduced.
An embodiment of the present disclosure provides a third embodiment, namely an electronic device, where the electronic device is configured to implement a method for deploying a file, and the electronic device includes: at least one processor; and a memory communicatively coupled to the at least one processor; wherein, the liquid crystal display device comprises a liquid crystal display device,
the memory stores instructions executable by the one processor to enable the at least one processor to perform the method of deploying a file as described in the first embodiment.
The present disclosure provides a fourth embodiment, namely a computer storage medium storing computer-executable instructions that can perform the method of deploying a file as described in the first embodiment.
Referring now to fig. 3, a schematic diagram of an electronic device suitable for use in implementing embodiments of the present disclosure is shown. The terminal devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and the like, and stationary terminals such as digital TVs, desktop computers, and the like. The electronic device shown in fig. 3 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.
As shown in fig. 3, the electronic device may include a processing means (e.g., a central processor, a graphics processor, etc.) 301 that may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 302 or a program loaded from a storage means 308 into a Random Access Memory (RAM) 303. In the RAM 303, various programs and data required for the operation of the electronic device are also stored. The processing device 301, the ROM 302, and the RAM 303 are connected to each other via a bus 304. An input/output (I/O) interface 305 is also connected to bus 304.
In general, the following devices may be connected to the I/O interface 305: input devices 306 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; an output device 307 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 308 including, for example, magnetic tape, hard disk, etc.; and communication means 309. The communication means 309 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. While fig. 3 shows an electronic device having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a non-transitory computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via a communication device 309, or installed from a storage device 308, or installed from a ROM 302. The above-described functions defined in the methods of the embodiments of the present disclosure are performed when the computer program is executed by the processing means 301.
It should be noted that the computer readable medium described in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.
In some implementations, the clients, servers may communicate using any currently known or future developed network protocol, such as HTTP (HyperText Transfer Protocol ), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the internet (e.g., the internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed networks.
The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device.
Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, including, but not limited to, an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present disclosure may be implemented by means of software, or may be implemented by means of hardware. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.
The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this disclosure is not limited to the specific combinations of features described above, but also covers other embodiments which may be formed by any combination of features described above or equivalents thereof without departing from the spirit of the disclosure. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).
Moreover, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are example forms of implementing the claims.
Claims (9)
1. A method of deploying a file, comprising:
acquiring a first instruction description file change message sent by an instruction file management module through a network hook interface based on a preset network hook interface message rule;
generating a pulling instruction meeting a preset network hook interface pulling rule based on the triggering of the first instruction description file changing message;
acquiring a first instruction description file managed in the instruction file management module through a network hook interface according to the pulling instruction; the file type of the first instruction description file comprises a script type or a compilable type;
acquiring a first instruction executable file according to the file type of the first instruction description file and the first instruction description file, forcibly closing the process of a second instruction executable file associated with the first instruction executable file, and sending starting information for starting the first instruction executable file according to a preset starting rule to a daemon module.
2. The method of claim 1, wherein the obtaining a first instruction executable file from the file type of the first instruction description file and the first instruction description file comprises:
judging whether the file type of the first instruction description file meets script type conditions or not;
if yes, the first instruction description file is judged to be the first instruction executable file.
3. The method of claim 1, wherein the obtaining a first instruction executable file from the file type of the first instruction description file and the first instruction description file comprises:
judging whether the file type of the first instruction description file meets a compilable type condition or not;
if yes, compiling the first instruction description file and generating the first instruction executable file.
4. A system for deploying a file, comprising:
an instruction file management module configured to: managing a first instruction description file, and sending a first instruction description file change message to a network hook module through a network hook interface based on a preset network hook interface message rule;
the network hook module is configured to: acquiring the first instruction description file change message through a network hook interface based on a preset network hook interface message rule; generating a pulling instruction meeting a preset network hook interface pulling rule based on the triggering of the first instruction description file changing message; acquiring a first instruction description file managed in the instruction file management module through a network hook interface according to the pulling instruction; acquiring a first instruction executable file according to the file type of the first instruction description file and the first instruction description file, forcibly closing a second instruction executable file associated with the first instruction executable file, and sending starting information for starting the first instruction executable file to a daemon module; the file type of the first instruction description file comprises a script type or a compilable type;
the daemon module is configured to: and receiving the starting information, and starting the first instruction executable file according to the preset starting rule based on the triggering of the starting information.
5. The system of claim 4, wherein the instruction file management module further comprises: configuring a preset network hook interface message rule; and configuring a preset network hook interface pulling rule.
6. The system of claim 4, wherein the daemon module further comprises: and configuring a preset starting rule.
7. The system of claim 4, wherein the network hook module comprises: a first judgment unit and a second judgment unit;
the first judging unit is configured to: judging whether the file type of the first instruction description file meets script type conditions or not; if yes, judging the first instruction description file as the first instruction executable file;
the second judging unit is configured to: judging whether the file type of the first instruction description file meets a compilable type condition or not; if yes, compiling the first instruction description file and generating the first instruction executable file.
8. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any one of claims 1 to 3.
9. An electronic device, comprising:
one or more processors;
a storage means for storing one or more programs which when executed by the one or more processors cause the one or more processors to implement the method of any of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910885726.0A CN110750242B (en) | 2019-09-19 | 2019-09-19 | File deployment method, system, medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910885726.0A CN110750242B (en) | 2019-09-19 | 2019-09-19 | File deployment method, system, medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110750242A CN110750242A (en) | 2020-02-04 |
| CN110750242B true CN110750242B (en) | 2023-05-02 |
Family
ID=69276665
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910885726.0A Active CN110750242B (en) | 2019-09-19 | 2019-09-19 | File deployment method, system, medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110750242B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2013196066A (en) * | 2012-03-16 | 2013-09-30 | Hitachi Information & Control Solutions Ltd | File server, data input/output method, i/o hook module program and i/o proxy demon program |
| CN108958927A (en) * | 2018-05-31 | 2018-12-07 | 康键信息技术（深圳）有限公司 | Dispositions method, device, computer equipment and the storage medium of container application |
| CN109918079A (en) * | 2019-01-31 | 2019-06-21 | 平安科技（深圳）有限公司 | Rule update method, device and the computer equipment of rule engine system |
| CN110058994A (en) * | 2019-03-01 | 2019-07-26 | 视联动力信息技术股份有限公司 | A kind of method and system for debugging program in Android medical terminal |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7917901B2 (en) * | 2006-08-07 | 2011-03-29 | International Business Machines Corporation | Maintainable dynamic instrumentation technique for changing versions of software |
-
2019
- 2019-09-19 CN CN201910885726.0A patent/CN110750242B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2013196066A (en) * | 2012-03-16 | 2013-09-30 | Hitachi Information & Control Solutions Ltd | File server, data input/output method, i/o hook module program and i/o proxy demon program |
| CN108958927A (en) * | 2018-05-31 | 2018-12-07 | 康键信息技术（深圳）有限公司 | Dispositions method, device, computer equipment and the storage medium of container application |
| CN109918079A (en) * | 2019-01-31 | 2019-06-21 | 平安科技（深圳）有限公司 | Rule update method, device and the computer equipment of rule engine system |
| CN110058994A (en) * | 2019-03-01 | 2019-07-26 | 视联动力信息技术股份有限公司 | A kind of method and system for debugging program in Android medical terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110750242A (en) | 2020-02-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111367516B (en) | Application interface generation method and device and electronic equipment | |
| CN113505302A (en) | Method, device and system for supporting dynamic acquisition of buried point data and electronic equipment | |
| CN111309304B (en) | Method, device, medium and electronic equipment for generating IDL file | |
| CN111338944B (en) | Remote Procedure Call (RPC) interface testing method, device, medium and equipment | |
| US20230385080A1 (en) | Method and apparatus for presenting information on lock screen interface, terminal, and storage medium | |
| CN111259636A (en) | Document rendering method and device and electronic equipment | |
| CN111596992B (en) | Navigation bar display method and device and electronic equipment | |
| CN112596854A (en) | Method and device for continuously integrating running of assembly line | |
| CN112256372A (en) | Information processing method and device and electronic equipment | |
| CN110750242B (en) | File deployment method, system, medium and electronic equipment | |
| CN116302271A (en) | Page display method and device and electronic equipment | |
| CN112817701B (en) | Timer processing method, device, electronic equipment and computer readable medium | |
| CN111309323B (en) | Parameter initialization method and device and electronic equipment | |
| CN111459893B (en) | File processing method and device and electronic equipment | |
| CN110221854A (en) | A kind of multi-process data-updating method, device, medium and electronic equipment | |
| CN112346728B (en) | Device adaptation method, apparatus, device and computer readable medium | |
| CN110908867B (en) | Task completion judging method and device, storage medium and electronic equipment | |
| CN116360710B (en) | Data storage method applied to server cluster, electronic device and readable medium | |
| CN116755889B (en) | Data acceleration method, device and equipment applied to server cluster data interaction | |
| CN111581305B (en) | Feature processing method, device, electronic equipment and medium | |
| CN111626787B (en) | Resource issuing method, device, medium and equipment | |
| CN111796802B (en) | Function package generation method and device and electronic equipment | |
| CN114253520B (en) | Interface code generation method and device | |
| CN111367555B (en) | Assertion method, assertion device, electronic equipment and computer readable medium | |
| CN111399902B (en) | Client source file processing method and device, readable medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |