Front-end resource deployment method, device and system, server and storage medium

Abstract

The embodiment of the invention discloses a front-end resource deployment method, device and system, a server and a storage medium, and relates to the field of computers.The method is applied to a file processor of an automatic deployment system and comprises the steps that a target resource deployment execution instruction sent by a server-side file transfer station in the automatic deployment system is received; the target resource deployment execution instruction is determined by the file transfer station according to a deployment execution mode in an original resource deployment execution instruction from a client server of the automatic deployment system; according to a target deployment execution mode corresponding to the target resource deployment execution instruction, obtaining a to-be-deployed resource; and pushing the to-be-deployed resources to a remote cache server of the automatic deployment system to realize front-end resource deployment. By adopting the technical scheme provided by the embodiment of the invention, the deployment of the front-end static resources can be conveniently and quickly realized.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of computer technology, and in particular, to a method, device, system, server, and storage medium for front-end resource deployment. Background Art

[0002] In the development of front-end development in software development, the single-page architecture has occupied a large proportion. Whether it is Vue.js or React.js, the front-end code will be compressed into static files such as js (JavaScript) / css (Cascading Style Sheets) / html (Hyper Text Markup Language). Currently, the general processing logic is divided into three modes: 1) As part of the back-end service projects such as Java / Go / C#, it is deployed together with the back-end service; 2) Exist as a static module of the Node application, and then the Node application runs; 3) In the scenario of front-end separation, it exists as a static file of the Nginx service, and the Nginx service is used to provide services for users.

[0003] However, in the process of implementing the present invention, it is found that there are at least the following problems in the existing technology:

[0004] In the 1) mode and 2) mode of the existing technical solutions, the front-end going live still needs to wait for the back-end to go live together, which will affect the whole situation with a minor change. For particularly large projects, the disadvantages are very obvious; although the 3) mode realizes independent front-end and back-end deployment, front-end personnel need to have a very in-depth study and understanding of Nginx skills, and there is a certain learning curve. The above three modes all lead to low efficiency of front-end resource deployment. Summary of the Invention

[0005] The embodiments of the present invention provide a method, device, system, server, and storage medium for front-end resource deployment, so as to conveniently and quickly realize the deployment of front-end static resources.

[0006] In a first aspect, the embodiments of the present invention provide a method for front-end resource deployment. The method is applied to a file processor of an automated deployment system. The automated deployment system further includes a client server, a file transfer station on the server side, and a remote cache server. The method includes:

[0007] Receiving a target resource deployment execution instruction sent by the file transfer station; wherein, the target resource deployment execution instruction is determined by the file transfer station according to the deployment execution method in the original resource deployment execution instruction from the client server;

[0008] Obtaining resources to be deployed according to the target deployment execution method corresponding to the target resource deployment execution instruction;

[0009] Push the to-be-deployed resources into the remote cache server to implement front-end resource deployment.

[0010] In a second aspect, an embodiment of the present invention further provides a front-end resource deployment device, which is configured in a file processor of an automated deployment system. The automated deployment system further includes a client server, a file transfer station on the server side, and a remote cache server. The device includes:

[0011] An instruction receiving module, configured to receive a target resource deployment execution instruction sent by the file transfer station; wherein, the target resource deployment execution instruction is determined by the file transfer station according to the deployment execution method in the original resource deployment execution instruction from the client server;

[0012] A resource acquisition module, configured to acquire to-be-deployed resources according to the target deployment execution method corresponding to the target resource deployment execution instruction;

[0013] A resource deployment module, configured to push the to-be-deployed resources into the remote cache server to implement front-end resource deployment.

[0014] In a third aspect, an embodiment of the present invention provides an automated deployment system, which includes a client server, a file transfer station on the server side, a file processor, and a remote cache server;

[0015] The client server is configured to send an original resource deployment instruction to the file transfer station according to an input execution instruction;

[0016] The file transfer station is configured to determine at least one target resource deployment execution instruction matching the file processor according to the deployment execution method in the original resource deployment instruction, and send the at least one target resource execution instruction to the file processor;

[0017] The file processor is configured to execute the front-end resource deployment method as described in any embodiment of the present invention;

[0018] The remote cache server is configured to receive the to-be-deployed resources pushed by the file processor.

[0019] In a fourth aspect, an embodiment of the present invention provides a server, which includes:

[0020] One or more processors;

[0021] A memory, configured to store one or more programs;

[0022] When the one or more programs are executed by the one or more processors, the one or more processors implement the front-end resource deployment method provided in any embodiment of the present invention.

[0023] In a fifth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, it implements the front-end resource deployment method provided in any embodiment of the present invention.

[0024] The embodiments in the above invention have the following advantages or beneficial effects:

[0025] The technical solution of the embodiment of the present invention is applied to a file processor of an automated deployment system. By receiving a target resource deployment execution instruction sent by a file transfer station of a server in the automated deployment system; wherein, the target resource deployment execution instruction is determined by the file transfer station according to the deployment execution method in the original resource deployment execution instruction from a client server of the automated deployment system; according to the target deployment execution method corresponding to the target resource deployment execution instruction, obtain the resources to be deployed; push the resources to be deployed into a remote cache server of the automated deployment system to implement front-end resource deployment. Because the technical means of Node service is adopted, the technical problem that in the prior art, the front-end goes online and still needs to wait for the back-end to go online together, or the front-end personnel need to have a very in-depth study and understanding of the remote cache server, resulting in low efficiency of front-end resource deployment, is overcome, and the deployment of front-end static resources is realized conveniently and quickly. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 It is a flowchart of a front-end resource deployment method provided by an embodiment of the present invention;

[0027] Figure 2a It is a flowchart of another front-end resource deployment method provided by an embodiment of the present invention;

[0028] Figure 2b It is a panoramic flowchart of a front-end resource deployment method on an automatic deployment system provided by an embodiment of the present invention;

[0029] Figure 3 It is a schematic structural diagram of a front-end resource deployment device provided by an embodiment of the present invention;

[0030] Figure 4 It is a schematic structural diagram of an automated deployment system provided by an embodiment of the present invention;

[0031] Figure 5 It is a schematic structural diagram of a server provided by an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0032] The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It can be understood that the specific embodiments described herein are only used to explain the present invention, rather than limiting the present invention. In addition, it should be noted that for the convenience of description, only the parts related to the present invention are shown in the drawings, rather than all the structures.

[0033] Figure 1 FIG. 4 is a flowchart of a front-end resource deployment method provided by an embodiment of the present invention. This embodiment is applicable to the situation of deploying static resources in front-end development. This method can be applied to the file processor of an automated deployment system. The automated deployment system also includes a client server, a file transfer station on the server side, and a remote cache server. The file processor can be, for example, a Node file processor, and the file transfer station on the server side can be, for example, a Node server-side file transfer station. This method can be executed by a front-end resource deployment device integrated in the server, and this device can be implemented in a software and / or hardware manner. As Figure 1 shown, the method specifically includes the following steps:

[0034] S110. Receive a target resource deployment execution instruction sent by the file transfer station; wherein, the target resource deployment execution instruction is determined by the file transfer station according to the deployment execution method in the original resource deployment execution instruction from the client server.

[0035] Since there can be at least one deployment execution method in the original resource deployment instruction, after receiving the original resource deployment execution instruction, the file transfer station can send the target resource deployment execution instruction to the corresponding processing factory in the file processor according to the type of the deployment execution method in the original resource deployment execution instruction.

[0036] S120. Obtain the resources to be deployed according to the target deployment execution method corresponding to the target resource deployment execution instruction.

[0037] In the process of front-end resource deployment, there can be simple picture or file uploads, or front-end project engineering uploads. For simple picture or file uploads, they can be uploaded through a web (WorldWide Web) interface at the client of the front-end development engineer; for front-end project engineering, sometimes it is necessary to pull code from a remote repository to implement front-end resource deployment. Among them, the method of pulling code from a remote repository can include the method of pulling code from a remote repository and compiling it, and the method of pulling code of a specified resource path from a remote repository.

[0038] Optionally, if the front-end developer only deploys images or files through the interface upload method, the upload button and the server staging path selection can appear simultaneously on the web interface at the front-end developer's client. If it is necessary to deploy the front-end project, then three types of web interfaces can appear: interface upload, pulling code from a remote repository and compiling, and pulling code of a specified resource path from a remote repository.

[0039] In an alternative implementation, when the target deployment execution method is the interface upload method, according to the target deployment execution method corresponding to the target resource deployment execution instruction, obtaining the resource to be deployed may include: obtaining the original resource uploaded through the interface, and determining the resource type corresponding to the original resource; when the resource type is an image resource and / or a file resource, determining the image resource and / or the file resource as the resource to be deployed; when the resource type is a static resource compressed file, decompressing the static resource compressed file to obtain the resource to be deployed.

[0040] If the front-end developer selects resource upload, here it is only necessary to distinguish between images, files, and static resources. If it is a static resource, it is generally stipulated to upload a compressed package, and here it is necessary to decompress the compressed package to obtain the resource to be deployed. Among them, the static resources can be html files, css files, js files, etc.

[0041] In another alternative implementation, when the target deployment execution method is the method of pulling code from a remote repository, according to the target deployment execution method corresponding to the target resource deployment execution instruction, obtaining the resource to be deployed may include: based on the method of pulling code from a remote repository, pulling the deployment code corresponding to the resource to be deployed from the remote repository according to the target resource deployment execution instruction; determining the resource path of the resource to be deployed; and obtaining the resource to be deployed according to the deployment code and the resource path.

[0042] Among them, the remote repository can be, for example, git and svn, etc.

[0043] Specifically, based on the method of pulling code from a remote repository and compiling, the remote repository address and the compilation command can be obtained from the preset resource deployment information database according to the target resource deployment execution instruction; according to the remote repository address, pulling the original deployment code corresponding to the resource to be deployed from the remote repository; determining the resource path from the compilation command; and compiling the original deployment code according to the compilation command to obtain the resource to be deployed according to the resource path.

[0044] Among them, the preset resource deployment information database can be, for example, a MySQL database. The basic work information of front-end developers can be pre-stored in the preset resource deployment information database, such as basic information of the front-end system / project, project type, remote repository address, remote repository key, execution type, and other basic information. The project type can refer to static resources such as pictures / files or front-end system static resources. The execution type is the deployment execution method.

[0045] It should be noted that after the client server issues the original resource deployment execution instruction, the file transfer station on the server side can read the MySQL database to obtain all the information of this service, and then send the command to the corresponding processing factory in the file processor according to different execution types.

[0046] If it is the method of pulling code from the remote repository and compiling, input buttons for the remote repository address and script commands can appear on the web interface of the client server for future project follow-up to pull code and execute; the file processor can use Node to execute Linux commands to pull remote code, obtain the compilation command of the code from the MySQL database, and then execute it. Then, Node obtains the resources to be deployed according to the resource path in the compilation command.

[0047] Based on the method of pulling the code of the specified resource path from the remote repository, the remote repository address and resource path can be obtained from the preset resource deployment information database according to the target resource deployment execution instruction; according to the remote repository address, pull the compiled deployment code corresponding to the resource to be deployed from the remote repository; execute the compiled deployment code to obtain the resources to be deployed according to the resource path.

[0048] If it is to pull the code of the specified resource path from the remote repository, in addition to the input of the remote repository address on the web interface of the client server, a resource path specification is also required to accurately find the resource file directory; the file processor can use Node to execute Linux commands to pull remote code because the resources already exist in the remote repository. At this time, only the resources to be deployed need to be extracted from the pulled code through the specified static file path.

[0049] S130. Push the resources to be deployed into the remote cache server to implement front-end resource deployment.

[0050] Among them, the remote cache server can be, for example, a CDN server, a cache server, or a cache cloud, etc.

[0051] In this embodiment, the resources to be deployed can be pushed to the remote cache server to implement front-end resource deployment.

[0052] The technical solution of the embodiment of the present invention is applied to a file processor of an automated deployment system. By receiving a target resource deployment execution instruction sent by a file transfer station of a server in the automated deployment system; wherein, the target resource deployment execution instruction is determined by the file transfer station according to the deployment execution method in the original resource deployment execution instruction from the client server of the automated deployment system; according to the target deployment execution method corresponding to the target resource deployment execution instruction, obtain the resource to be deployed; push the resource to be deployed into the remote cache server of the automated deployment system to implement front-end resource deployment. It solves the problem in the prior art that the front-end goes online and still needs to wait for the back-end to go online together, or the front-end personnel need to have a very in-depth learning and understanding of the remote cache server, resulting in low efficiency of front-end resource deployment, and conveniently and quickly realizes the deployment of front-end static resources.

[0053] Figure 2a It is a flowchart of another front-end resource deployment method provided by the embodiment of the present invention. On the basis of the above embodiment, the operation of pushing the resource to be deployed into the remote cache server to implement front-end resource deployment is refined, and operations are further added. As Figure 2a shown, the method specifically includes the following steps:

[0054] S210. Receive the target resource deployment execution instruction sent by the file transfer station; wherein, the target resource deployment execution instruction is determined by the file transfer station according to the deployment execution method in the original resource deployment execution instruction from the client server.

[0055] S220. Obtain the resource to be deployed according to the target deployment execution method corresponding to the target resource deployment execution instruction.

[0056] S230. Store the resource to be deployed in the temporary file cache area.

[0057] Among them, the temporary file cache area can be, for example, the hard disk of the server where the file processor is located, or a redis cache server, a cache cluster, etc.

[0058] S240. Generate an execution log for the resource to be deployed, and store the execution log in the preset resource deployment information database; wherein, the execution log includes an execution version number.

[0059] S250. Compress the resource to be deployed to obtain a compressed file, and name the compressed file using the execution version number to obtain a named compressed file.

[0060] S260. Push the named compressed file to the preset historical file cache area for version rollback.

[0061] S270. Establish a file transfer pipeline between the temporary file cache area and the remote cache server.

[0062] S280. Push the resources to be deployed in the temporary file buffer to the remote cache server through the file transfer pipeline to implement front-end resource deployment.

[0063] S290. Empty the temporary file buffer and trigger the automatic refresh mechanism of the remote cache server to present the resources to be deployed currently; and / or,

[0064] When receiving the user's access request for the resources to be deployed, provide the address of the server where the file processor is located to the user.

[0065] Triggering the automatic refresh mechanism of the remote cache server can automatically refresh the cache of the remote cache server, so that the static resources presented currently are the latest files.

[0066] When the user accesses the resources to be deployed, do not directly expose the address of the remote cache server, but only expose the address of the current Node system, aiming to improve the security guarantee of the remote cache server.

[0067] The technical solution of the embodiment of the present invention uses Node means, without the need for front-end personnel to understand the concepts of server-side services such as Nginx servers, CDN servers, and cache servers, and can quickly realize the rapid deployment and service presentation of front-end services; without any special processing of the static server by the front-end, static resource acceleration can be achieved, thereby improving the front-end access speed and high availability; the release and rollback of front-end static resources are realized conveniently and quickly, and the convenience of front-end deployment is achieved.

[0068] To enable those skilled in the art to better understand the front-end resource deployment method of the embodiment of the present invention, Figure 2b A panoramic process schematic diagram of the front-end resource deployment method on an automatic deployment system is provided.

[0069] After receiving the resource deployment execution instruction, the file transfer station on the server side can read the MySQL database to obtain all the information of this service, and then send the command to the corresponding processing factory in the file processor according to different execution types.

[0070] If the front - end developer uploads resources through the interface, the static files (i.e., resources to be deployed) can be directly obtained based on the uploaded resources; if it is necessary to pull code from a remote repository and compile it, here node is used to execute Linux commands to pull code from the remote repository, and the compilation command of the code is obtained from mysql and then executed. Then, Node extracts static files through a static file extractor according to the resource path in the compilation command; if it is necessary to pull code with a specified resource path from the remote repository, the static files can be extracted from the pulled code according to the specified resource path through a static file extractor, and then the static files are pushed to the file storage (i.e., the remote cache server) through a remote file pusher. It is also possible to trigger the cache refresh of the remote cache server, store the static files in the historical file cache for version rollback, and provide a service proxy when users access the static files.

[0071] The following is an embodiment of the front - end resource deployment device provided by the embodiment of the present invention. This device and the front - end resource deployment method in the above - mentioned Embodiment 1 belong to the same inventive concept. For the details not described in detail in the embodiment of the front - end resource deployment device, the content of the above - mentioned embodiments can be referred to.

[0072] Figure 3 The following is a schematic structural diagram of the front - end resource deployment device provided by the embodiment of the present invention. This device is configured in the file processor of the automated deployment system, and the automated deployment system further includes a client - side server, a file transfer station on the server - side, and a remote cache server. As Figure 3 shown, the device includes: an instruction receiving module 310, a resource acquisition module 320, and a resource deployment module 330. Among them:

[0073] The instruction receiving module 310 is used to receive the target resource deployment execution instruction sent by the file transfer station; among them, the target resource deployment execution instruction is determined by the file transfer station according to the deployment execution method in the original resource deployment execution instruction from the client - side server;

[0074] The resource acquisition module 320 is used to obtain the resources to be deployed according to the target deployment execution method corresponding to the target resource deployment execution instruction;

[0075] The resource deployment module 330 is used to push the resources to be deployed into the remote cache server to implement front - end resource deployment.

[0076] The technical solution of the embodiment of the present invention is applied to a file processor of an automated deployment system. By receiving a target resource deployment execution instruction sent by a file transfer station of a server in the automated deployment system; wherein, the target resource deployment execution instruction is determined by the file transfer station according to the deployment execution method in the original resource deployment execution instruction from a client server of the automated deployment system; according to the target deployment execution method corresponding to the target resource deployment execution instruction, obtain the resource to be deployed; push the resource to be deployed into the remote cache server of the automated deployment system to implement the front-end resource deployment. It solves the problem in the prior art that the front-end goes online and still needs to wait for the back-end to go online together, or the front-end personnel need to have a very in-depth study and understanding of the remote cache server, resulting in low efficiency of front-end resource deployment, and conveniently and quickly realizes the deployment of front-end static resources.

[0077] In the above device, optionally, the target deployment execution method is the method of uploading through an interface;

[0078] Correspondingly, the resource acquisition module 320 can specifically be used for:

[0079] Obtain the original resources uploaded through the interface, and determine the resource type corresponding to the original resources;

[0080] When the resource type is a picture resource and / or a file resource, determine the picture resource and / or the file resource as the resource to be deployed;

[0081] When the resource type is a static resource compressed file, decompress the static resource compressed file to obtain the resource to be deployed.

[0082] In the above device, optionally, the target deployment execution method is the method of pulling code from a remote repository;

[0083] Correspondingly, the resource acquisition module 320 may include:

[0084] A deployment code pulling unit, configured to pull the deployment code corresponding to the resource to be deployed from the remote repository based on the method of pulling code from the remote repository according to the target resource deployment execution instruction;

[0085] A resource path determination unit, configured to determine the resource path of the resource to be deployed;

[0086] A resource acquisition unit, configured to obtain the resource to be deployed according to the deployment code and the resource path.

[0087] In the above device, optionally, the method of pulling code from the remote repository includes the method of pulling code from the remote repository and compiling;

[0088] Correspondingly, the deployment code pulling unit can be specifically used for:

[0089] Based on the method of pulling code from the remote repository and compiling, obtain the remote repository address and the compilation command from the preset resource deployment information database according to the target resource deployment execution instruction;

[0090] According to the remote repository address, pull the original deployment code corresponding to the resource to be deployed from the remote repository;

[0091] Correspondingly, the resource path determination unit can be specifically used for:

[0092] Determine the resource path from the compilation command;

[0093] Correspondingly, the resource acquisition unit can be specifically used for:

[0094] Compile the original deployment code according to the compilation command to obtain the resource to be deployed according to the resource path.

[0095] In the above device, optionally, the method of pulling code from the remote repository includes the method of pulling code with a specified resource path from the remote repository;

[0096] Correspondingly, the deployment code pulling unit can be specifically used for:

[0097] Based on the method of pulling code with a specified resource path from the remote repository, obtain the remote repository address and the resource path from the preset resource deployment information database according to the target resource deployment execution instruction;

[0098] According to the remote repository address, pull the compiled deployment code corresponding to the resource to be deployed from the remote repository;

[0099] Correspondingly, the resource acquisition unit can be specifically used for:

[0100] Execute the compiled deployment code to obtain the resource to be deployed according to the resource path.

[0101] In the above device, optionally, the resource deployment module 330 may include:

[0102] The resource staging unit is used to store the resource to be deployed in the temporary file buffer;

[0103] The file transfer pipeline establishment unit is used to establish a file transfer pipeline between the temporary file buffer and the remote cache server;

[0104] A resource deployment unit is used to push the resources to be deployed in the temporary file buffer to the remote cache server through the file transfer pipeline to implement front-end resource deployment.

[0105] In the above device, optionally, it further includes a historical resource cache module, which is used after storing the resources to be deployed in the temporary file buffer:

[0106] Generate an execution log for the resources to be deployed and store the execution log in a preset resource deployment information database; wherein, the execution log includes an execution version number;

[0107] Compress the resources to be deployed to obtain a compressed file, and name the compressed file using the execution version number to obtain a named compressed file;

[0108] Push the named compressed file to a preset historical file buffer for version rollback.

[0109] In the above device, optionally, it further includes a resource presentation module, which is used after pushing the resources to be deployed in the temporary file buffer to the remote cache server through the file transfer pipeline:

[0110] Empty the temporary file buffer; trigger the automatic refresh mechanism of the remote cache server to currently present the resources to be deployed; and / or,

[0111] When receiving an access request from a user for the resources to be deployed, provide the address of the server where the file processor is located to the user.

[0112] The front-end resource deployment device configured in the file processor provided by the embodiments of the present invention can execute the front-end resource deployment method applied to the file processor provided by Embodiment 1 of the present invention, and has corresponding functional modules and beneficial effects for executing the front-end resource deployment method.

[0113] Figure 4 It is a schematic structural diagram of an automated deployment system provided by an embodiment of the present invention, as Figure 4 shown. The system includes a client server 410, a file transfer station 420 on the server side, a file processor 430, and a remote cache server 440;

[0114] The client server 410 is used to send an original resource deployment instruction to the file transfer station 420 according to an input execution instruction;

[0115] The file transfer station 420 is configured to determine at least one target resource deployment execution instruction that matches the file processor 430 according to the deployment execution method in the original resource deployment instruction, and send the at least one target resource execution instruction to the file processor 430;

[0116] The file processor 430 is configured to execute the front-end resource deployment method as described in any embodiment of the present invention;

[0117] The remote cache server 440 is configured to receive the resources to be deployed pushed by the file processor 430.

[0118] In the technical solution of the embodiment of the present invention, the client server sends an original resource deployment instruction to the file transfer station according to the input execution instruction; the file transfer station determines at least one target resource deployment execution instruction that matches the file processor according to the deployment execution method in the original resource deployment instruction, and sends the at least one target resource execution instruction to the file processor; the file processor executes the front-end resource deployment method as described in any embodiment of the present invention; the remote cache server receives the resources to be deployed pushed by the file processor. This solves the problem in the prior art that the front-end goes online and still needs to wait for the back-end to go online together, or the front-end personnel need to have a deep learning and understanding of the remote cache server, resulting in low efficiency of front-end resource deployment, and conveniently and quickly realizes the deployment of front-end static resources.

[0119] Figure 5 FIG. is a schematic structural diagram of a server provided by an embodiment of the present invention. Figure 5 FIG. shows a block diagram of an exemplary server 12 suitable for use in implementing the embodiments of the present invention. Figure 5 The shown server 12 is merely an example and should not impose any limitation on the functions and usage scope of the embodiments of the present invention.

[0120] As Figure 5 shown, the server 12 is presented in the form of a general-purpose computing device. The components of the server 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 connecting different system components (including the system memory 28 and the processing unit 16).

[0121] The bus 18 represents one or more of several types of bus structures, including a memory bus or a memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus structures. For example, these architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

[0122] Server 12 typically includes a variety of computer system readable media. These media can be any available media accessible to server 12, including volatile and non-volatile media, removable and non-removable media.

[0123] System memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. Server 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 34 can be used for reading and writing on non-removable, non-volatile magnetic media ( Figure 5 not shown, commonly referred to as a "hard disk drive"). Although Figure 5 not shown in the figure, a disk drive for reading and writing on removable non-volatile disks (such as "floppy disks") and an optical disk drive for reading and writing on removable non-volatile optical disks (such as CD-ROM, DVD-ROM or other optical media) can be provided. In these cases, each drive can be connected to bus 18 through one or more data media interfaces. System memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of the present invention.

[0124] A program / utility 40 having a set (at least one) of program modules 42 can be stored, for example, in system memory 28. Such program modules 42 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include the implementation of a network environment. Program modules 42 generally perform the functions and / or methods in the embodiments described in the present invention.

[0125] Server 12 can also communicate with one or more external devices 14 (such as keyboards, pointing devices, monitors 24, etc.), and can also communicate with one or more devices that enable users to interact with the server 12, and / or communicate with any device that enables the server 12 to communicate with one or more other computing devices (such as network cards, modems, etc.). This communication can be carried out through the input / output (I / O) interface 22. Moreover, the server 12 can also communicate with one or more networks (such as local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) through the network adapter 20. As shown in the figure, the network adapter 20 communicates with other modules of the server 12 through the bus 18. It should be understood that although not shown in the figure, other hardware and / or software modules can be used in combination with the server 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0126] The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, for example, implementing the steps of a front-end resource deployment method provided in the first embodiment of the present invention. This method is applied to the file processor of an automated deployment system. The automated deployment system further includes a client server, a file transfer station on the server side, and a remote cache server. The method includes:

[0127] Receiving a target resource deployment execution instruction sent by the file transfer station; wherein, the target resource deployment execution instruction is determined by the file transfer station according to the deployment execution method in the original resource deployment execution instruction from the client server;

[0128] Obtaining the resources to be deployed according to the target deployment execution method corresponding to the target resource deployment execution instruction;

[0129] Pushing the resources to be deployed into the remote cache server to implement front-end resource deployment.

[0130] Of course, those skilled in the art can understand that the processor can also implement the technical solutions of the front-end resource deployment method provided in any embodiment of the present invention.

[0131] This embodiment provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, it implements the steps of a front-end resource deployment method provided in the foregoing embodiments of the present invention. This method is applied to the file processor of an automated deployment system. The automated deployment system further includes a client server, a file transfer station on the server side, and a remote cache server. The method includes:

[0132] Receive the target resource deployment execution instruction sent by the file transfer station; wherein, the target resource deployment execution instruction is determined by the file transfer station according to the deployment execution method in the original resource deployment execution instruction from the client server;

[0133] Obtain the resource to be deployed according to the target deployment execution method corresponding to the target resource deployment execution instruction;

[0134] Push the resource to be deployed into the remote cache server to implement front-end resource deployment.

[0135] The computer storage medium of the embodiments of the present invention may adopt any combination of one or more computer-readable media. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium may be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples (non-exhaustive list) of the computer-readable storage medium include: an electrical connection with one or more wires, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0136] The computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries the computer-readable program code. Such a propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer-readable signal medium may also be any computer-readable medium other than the computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0137] The program code contained on the computer-readable medium may be transmitted by any appropriate medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination of the above.

[0138] Computer program code for performing the operations of the present invention may be written in one or more programming languages or combinations thereof. The programming languages include object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, executed as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or it may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0139] Those of ordinary skill in the art should understand that the various modules or steps of the present invention described above can be implemented using a general-purpose computing device. They can be centralized on a single computing device or distributed across a network composed of multiple computing devices. Optionally, they can be implemented using program code executable by a computer device, so that they can be stored in a storage device and executed by the computing device, or they can be separately fabricated into individual integrated circuit modules, or multiple modules or steps of them can be fabricated into a single integrated circuit module to be implemented. Thus, the present invention is not limited to any specific combination of hardware and software.

[0140] Note that the above is only the preferred embodiment of the present invention and the technical principles applied. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein. Various obvious changes, re-adjustments, and substitutions can be made by those skilled in the art without departing from the protection scope of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments. Without departing from the concept of the present invention, more other equivalent embodiments can be included, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A front-end resource deployment method, applied to a file processor of an automated deployment system, the automated deployment system further comprising a client server, a file transfer station on the server side, and a remote cache server, characterized in that, The method includes: Receiving a target resource deployment execution instruction sent by the file transfer station; wherein, the target resource deployment execution instruction is determined by the file transfer station according to the deployment execution method in the original resource deployment execution instruction from the client server; Obtaining the resources to be deployed according to the target deployment execution method corresponding to the target resource deployment execution instruction; Pushing the resources to be deployed into the remote cache server to implement front-end resource deployment.

2. The method according to claim 1, characterized in that, The target deployment execution method is the method of uploading through the interface; Obtaining the resources to be deployed according to the target deployment execution method corresponding to the target resource deployment execution instruction includes: Obtaining the original resources uploaded through the interface and determining the resource type corresponding to the original resources; When the resource type is picture resources and / or file resources, determining the picture resources and / or file resources as the resources to be deployed; When the resource type is a static resource compressed file, decompressing the static resource compressed file to obtain the resources to be deployed.

3. The method according to claim 1, characterized in that, The target deployment execution method is the method of pulling code from a remote repository; Obtaining the resources to be deployed according to the target deployment execution method corresponding to the target resource deployment execution instruction includes: Based on the method of pulling code from a remote repository, pulling the deployment code corresponding to the resources to be deployed from the remote repository according to the target resource deployment execution instruction; Determining the resource path of the resources to be deployed; Obtaining the resources to be deployed according to the deployment code and the resource path.

4. The method according to claim 3, characterized in that, The method of pulling code from a remote repository includes the method of pulling code from a remote repository and compiling; Based on the method of pulling code from a remote repository, pulling the deployment code corresponding to the resources to be deployed from the remote repository according to the target resource deployment execution instruction includes: Based on the method of pulling code from a remote repository and compiling, obtaining the remote repository address and the compilation command from the preset resource deployment information database according to the target resource deployment execution instruction; Pulling the original deployment code corresponding to the resources to be deployed from the remote repository according to the remote repository address; Determining the resource path of the resources to be deployed includes: Determining the resource path from the compilation command; Obtaining the resources to be deployed according to the deployment code and the resource path includes: Compiling the original deployment code according to the compilation command to obtain the resources to be deployed according to the resource path.

5. The method according to claim 3, characterized in that, The method of pulling code from a remote repository includes the method of pulling code of a specified resource path from a remote repository; Based on the method of pulling code from a remote repository, pulling the deployment code corresponding to the resources to be deployed from the remote repository according to the target resource deployment execution instruction includes: Based on the method of pulling code of a specified resource path from a remote repository, obtaining the remote repository address and the resource path from the preset resource deployment information database according to the target resource deployment execution instruction; Pulling the compiled deployment code corresponding to the resources to be deployed from the remote repository according to the remote repository address; Obtain the resource to be deployed according to the deployment code and the resource path, including: Execute the compiled deployment code to obtain the resource to be deployed according to the resource path.

6. The method according to claim 1, characterized in that, Push the resource to be deployed to the remote cache server to implement front-end resource deployment, including: Store the resource to be deployed in the temporary file cache area; Establish a file transfer pipeline between the temporary file cache area and the remote cache server; Use the file transfer pipeline to push the resource to be deployed in the temporary file cache area to the remote cache server to implement front-end resource deployment.

7. The method according to claim 6, wherein After storing the resource to be deployed in the temporary file cache area, it further includes: Generate an execution log for the resource to be deployed and store the execution log in a preset resource deployment information database; wherein, the execution log includes an execution version number; Compress the resource to be deployed to obtain a compressed file, and name the compressed file using the execution version number to obtain a named compressed file; Push the named compressed file to a preset historical file cache area for version rollback.

8. The method according to claim 6, wherein After using the file transfer pipeline to push the resource to be deployed in the temporary file cache area to the remote cache server, it further includes: Empty the temporary file cache area and trigger the automatic refresh mechanism of the remote cache server to present the resource to be deployed currently; and / or, When receiving an access request from a user for the resource to be deployed, provide the address of the server where the file processor is located to the user.

9. A front-end resource deployment device, configured in a file processor of an automated deployment system, the automated deployment system further including a client server, a file transfer station on the server side, and a remote cache server, wherein It includes: An instruction receiving module, configured to receive a target resource deployment execution instruction sent by the file transfer station; wherein, the target resource deployment execution instruction is determined by the file transfer station according to the deployment execution method in the original resource deployment execution instruction from the client server; A resource acquisition module, configured to obtain the resource to be deployed according to the target deployment execution method corresponding to the target resource deployment execution instruction; A resource deployment module, configured to push the resource to be deployed to the remote cache server to implement front-end resource deployment.

10. An automated deployment system, wherein It includes a client server, a file transfer station of the server side, a file processor, and a remote cache server; The client server is configured to send an original resource deployment instruction to the file transfer station according to the input execution instruction; The file transfer station is configured to determine at least one target resource deployment execution instruction matching the file processor according to the deployment execution method in the original resource deployment instruction, and send the at least one target resource execution instruction to the file processor; The file processor is configured to execute the front-end resource deployment method according to any one of claims 1-8; The remote cache server is configured to receive the resource to be deployed pushed by the file processor.

11. A server, wherein The server includes: One or more processors; A memory, configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the front-end resource deployment method according to any one of claims 1-8.

12. A computer-readable storage medium, having a computer program stored thereon, wherein When the program is executed by a processor, it implements the front-end resource deployment method described in any one of claims 1-8.

Images