A method, apparatus, terminal, and storage medium for publishing a resource

Abstract

This application is applicable to the field of computer technology, and provides a method, device, terminal, and storage medium for resource publishing. Among them, the above-mentioned resource publishing method is applied to a first terminal, and the publishing method specifically includes: deploying a target resource to an object storage system of a content delivery network, and extracting a target entry file bound with an access address of the target resource; uploading the target entry file to a test server, where the test server is used to test the target entry file; in response to an upload operation triggered by a first user on the first terminal when the test of the target entry file is completed, uploading the target entry file to a target server, and updating the content delivery network so that users can access the target resource through the target entry file in the target server. The embodiments of this application can improve the efficiency of resource publishing.

Description

Technical Field

[0001] This application belongs to the field of computer technology, and particularly relates to a method, device, terminal, and storage medium for resource publishing. Background Art

[0002] In order to achieve fast access to front-end static file resources, an object storage system (Operation Support Systems, OSS) is usually used currently. When deploying resources using OSS, in the production environment, it is necessary to back up, deploy, and refresh the Content Delivery Network (CDN). In the process of testing, each step requires a certain amount of time. If the version code volume is large, the release time is long. If problems are found during testing, a new release is required, resulting in a further increase in the resource publishing time. Summary of the Invention

[0003] Embodiments of this application provide a method, device, terminal, and storage medium for resource publishing, which can improve the resource publishing efficiency.

[0004] In the first aspect of the embodiments of this application, a method for resource publishing is provided, which is applied to a first terminal. The publishing method includes:

[0005] Deploy the target resource to the object storage system of the content delivery network, and extract the target entry file bound with the access address of the target resource;

[0006] Upload the target entry file to the test server, and the test server is used to test the target entry file;

[0007] In response to the upload operation triggered by the first user on the first terminal when the testing of the target entry file is completed, upload the target entry file to the target server, and update the content delivery network, so that the user can access the target resource through the target entry file in the target server.

[0008] In some embodiments of this application, when the content delivery network is updated, the mirror cache server of the content delivery network reads and caches the target entry file stored in the target server, so that when the mirror cache server receives a resource access request triggered by a second user on a second terminal, the target resource is sent to the second terminal based on the target entry file cached in the mirror cache server.

[0009] In some embodiments of the present application, deploying the target resource to the object storage system of the content delivery network includes: creating a target folder on the object storage system, where the file name of the target folder corresponds to the version identifier of the target resource; uploading the target resource to the target folder.

[0010] In some embodiments of the present application, the publishing method further includes: in response to a rollback operation triggered by the first user on the first terminal, uploading a rollback entry file to the target server according to the version identifier pointed to by the rollback operation, and updating the content delivery network so that the user can access the rollback resource through the rollback entry file in the target server, where the rollback resource is stored in a folder corresponding to the version identifier pointed to by the rollback operation.

[0011] In some embodiments of the present application, the domain names of the target server and the test server are different. The test server is used to read the target resource based on the target entry file on the test server when receiving a test request triggered by a third user on a third terminal, and feedback the target resource to the third terminal to test the function of accessing the target resource through the target entry file.

[0012] A resource publishing device provided in the second aspect of the embodiments of the present application is configured on a first terminal. The publishing device includes:

[0013] A deployment unit, configured to deploy a target resource to an object storage system of a content delivery network and extract a target entry file bound with an access address of the target resource;

[0014] A test unit, configured to upload the target entry file to a test server, where the test server is used to test the target entry file;

[0015] A publishing unit, configured to, in response to an upload operation triggered by a first user on the first terminal when the test of the target entry file is completed, upload the target entry file to a target server and update the content delivery network so that the user can access the target resource through the target entry file in the target server.

[0016] A terminal provided in the third aspect of the embodiments of the present application includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the above method are implemented.

[0017] In a fourth aspect of the embodiments of the present application, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0018] In a fifth aspect of the embodiments of the present application, a computer program product is provided. When the computer program product runs on a terminal, the terminal is enabled to execute the steps of the method.

[0019] In an implementation manner of the present application, by deploying a target resource to the OSS system of the CDN, extracting a target entry file bound with an access address of the target resource, and then uploading the target entry file to a test server, it is possible to complete the functional test of accessing the target resource through the target entry file before resource distribution. Furthermore, in response to an upload operation triggered by a first user on a first terminal when the test of the target entry file is completed, the target entry file is uploaded to a target server, and the CDN is updated, so that the user can access the target resource through the target entry file in the target server, without the need for testing after release, which can improve the release efficiency of the resource. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0021] Figure 1 It is a schematic implementation flowchart of a resource release method provided by an embodiment of the present application;

[0022] Figure 2 It is a schematic diagram of the OSS system provided by an embodiment of the present application;

[0023] Figure 3 It is a schematic structural diagram of a resource release device provided by an embodiment of the present application;

[0024] Figure 4 It is a schematic structural diagram of a terminal provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0025] In order to make the objectives, technical solutions, and advantages of the present application clearer, the following further details the present application in conjunction with the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the protection scope of the present application.

[0026] When releasing new version resources currently, it is usually necessary to deploy the resources to OSS and enable CDN, make a backup before release, then upload the new version of the resources to the target server, refresh CDN, and then conduct tests. If problems are found during the tests, it is necessary to re-release, refresh CDN and test again, resulting in a significant reduction in the release efficiency.

[0027] To illustrate the technical solution of this application, the following will be described through specific embodiments.

[0028] Figure 1 The schematic diagram of the implementation process of a resource release method provided by an embodiment of this application is shown. This method can be applied to a terminal and is applicable to the situation where it is necessary to improve the resource release efficiency.

[0029] Among them, the above terminal can be an intelligent device such as a computer, a smart phone, a tablet device, etc. In some embodiments, it can specifically refer to the device used by the first user to release resources. Among them, the first user can refer to an operation and maintenance staff member.

[0030] Specifically, the above resource release method can include the following steps S101 to S103.

[0031] Step S101, deploy the target resource to the object storage system of the content distribution network, and extract the target entry file bound with the access address of the target resource.

[0032] Among them, the above target resource can refer to static file resources, which can include but are not limited to resources such as pictures, static scripts, and audio.

[0033] In an embodiment of this application, the first terminal can deploy the target resource to the OSS system of the content distribution network, that is, upload the target resource to the cloud server corresponding to OSS for cloud storage.

[0034] To realize the access to the target resource, the first terminal also needs to extract the target entry file bound with the access address of the target resource from the target resource. In some specific embodiments, the target entry file can include HTML files, and other configuration files that support the operation of HTML files, etc.

[0035] In some embodiments of this application, the entry file can be a file in the target resource, and the terminal can extract the entry file from the target resource based on the file name or file information.

[0036] At this time, if the user initiates an access request, CDN can grab the target resource based on the access address recorded in the target entry file and feedback it to the terminal that initiated the request.

[0037] Step S102: Upload the target entry file to the test server.

[0038] Among them, the above-mentioned test server can be used to test the target entry file. The type of the test server can be selected according to the actual situation. For example, it can be an Nginx server.

[0039] In some embodiments of the present application, the test server is bound to a corresponding domain name. The test server can be used to read the target resource based on the target entry file on the test server when receiving a test request triggered by a third user on a third terminal, and feedback the target resource to the third terminal to test the function of accessing the target resource through the target entry file.

[0040] Among them, the third user can be the same as or different from the first user, and the third terminal can also be the same as or different from the first terminal.

[0041] Specifically, after the third user triggers a test request on the third terminal, the target resource feedback by the test server can be received. Since there is often a function list recording the functions updated in this release when the resource is released, the third user can manually detect whether each function in the function list can be normally implemented. If all can be normally implemented, it means that the target resource can be normally accessed through the target entry file, and it also means that both the target resource and the target entry file are available files, then it can be confirmed that the test of the target entry file is completed.

[0042] Step S103: In response to the upload operation triggered by the first user on the first terminal when the test of the target entry file is completed, upload the target entry file to the target server and update the content delivery network so that the user can access the target resource through the target entry file in the target server.

[0043] In the embodiments of the present application, if the test of the target entry file is completed, the first user can trigger an upload operation on the first terminal to upload the target entry file to the target server.

[0044] Among them, the target server refers to the server used for the official release, which can specifically refer to the data source server in the content delivery network. Its type can also be selected according to the actual situation. For example, it can be an Nginx server. And the domain name corresponding to the target server is different from that of the test server.

[0045] After uploading the target entry file to the target server, the first terminal can update the content delivery network. At this time, the user can access the target resource through the target entry file in the target server.

[0046] In some embodiments of the present application, when the CDN is updated, the mirror cache server of the CDN will read and cache the target entry file stored in the target server, so that when the mirror cache server receives a resource access request triggered by a second user on a second terminal, the target resource will be sent to the second terminal based on the target entry file cached in the mirror cache server.

[0047] Among them, the second terminal can be the same as or different from the first terminal. And, in some embodiments, the mirror cache server that receives the resource access request of the second terminal can be the edge node corresponding to the second terminal among all the mirror cache servers of the content delivery network, that is, the node closest to the request location where the second terminal is located, thereby improving the access speed of the second terminal to the target resource.

[0048] Specifically, before updating the CDN, since the cache of the mirror cache server has not been updated, the entry file cached in the mirror cache server is the one grabbed from the target server last time. If a second user triggers a resource access request on a second terminal, the second user will read the previous version of the resource based on the entry file grabbed from the target server last time. Based on this, the testing and uploading processes before updating the CDN in the present application will not affect the normal use of the second user.

[0049] After updating the CDN, the mirror cache server will read and cache the entry file in the target server again, and the entry file cached at this time is the target entry file. If a second user triggers a resource access request on a second terminal, the second user will read the target resource based on the access address recorded in the target entry file.

[0050] It should be noted that when the CDN is updated, each mirror cache server of the CDN will re-read and cache the entry file. And, in some embodiments, the target resource can also be read and cached further according to the entry file, thereby improving the access speed of the second terminal to the target resource.

[0051] On the contrary, if some or all functions cannot be realized normally during the test on the test server, it means that at least part of the target resource and the target entry file are unavailable. At this time, according to the test results, the first user can repair the problem file, redeploy the target resource to the object storage system of the content delivery network again, and upload the target entry file to the test server again until the test is completed and then the release is carried out.

[0052] In an embodiment of the present application, by deploying the target resource to the OSS system of the CDN, extracting the target entry file bound with the access address of the target resource, and then uploading the target entry file to the test server, it is possible to complete the functional test of accessing the target resource through the target entry file before resource distribution. Furthermore, in response to the upload operation triggered by the first user on the first terminal when the test of the target entry file is completed, the target entry file is uploaded to the target server, and the CDN is updated, so that the user can access the target resource through the target entry file in the target server, without the need for testing after release, which can improve the release efficiency of the resource.

[0053] Considering that a backup operation is required for each release, in an embodiment of the present application, when deploying the target resource to the object storage system of the content distribution network, the first terminal can create a target folder on the object storage system and then upload the target resource to the target folder.

[0054] Among them, the file name of the target folder corresponds to the version identifier of the target resource. As Figure 2 shown, the version identifier can refer to the version number.

[0055] That is to say, each time a resource is uploaded, the resource can be uploaded to the folder with the file name corresponding to the version identifier. At this time, the operation of uploading the resource realizes the backup operation. If a version rollback is required, there is no need to upload the old version resource again, and the rollback can be realized according to the version identifier.

[0056] Specifically, in some embodiments of the present application, in response to the rollback operation triggered by the first user on the first terminal, according to the version identifier pointed to by the rollback operation, the first terminal can upload the rollback entry file to the target server and update the content distribution network.

[0057] At this time, the user can access the rollback resource through the rollback entry file in the target server, where the rollback resource refers to the resource of any version before the version corresponding to the target resource, and the rollback resource can be stored in the folder corresponding to the version identifier pointed to by the rollback operation.

[0058] In the embodiment of the present application, by storing the resource in the folder with the file name corresponding to the version identifier, there is no need to perform a backup again on other servers, which reduces the time required for backup and improves the release efficiency of the resource. At the same time, using the version identifier, it is possible to roll back to any version according to the requirement, so that the user can access the resource of any version.

[0059] It should be noted that for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that this application is not limited by the described action sequence, because according to this application, certain steps can be performed in other sequences.

[0060] As Figure 3 shown in the structural schematic diagram of a resource publishing device 300 provided by an embodiment of this application, the resource publishing device 300 is configured on a first terminal.

[0061] Specifically, the resource publishing device 300 may include:

[0062] A deployment unit 301, configured to deploy a target resource to an object storage system of a content delivery network, and extract a target entry file bound with an access address of the target resource;

[0063] A test unit 302, configured to upload the target entry file to a test server, and the test server is used to test the target entry file;

[0064] A publishing unit 303, configured to, in response to an upload operation triggered by a first user on the first terminal when the test of the target entry file is completed, upload the target entry file to a target server, and update the content delivery network, so that a user can access the target resource through the target entry file in the target server.

[0065] In some embodiments of this application, when the above content delivery network is updated, a mirror cache server of the content delivery network reads and caches the target entry file stored in the target server, so that when the mirror cache server receives a resource access request triggered by a second user on a second terminal, the target resource is sent to the second terminal based on the target entry file cached in the mirror cache server.

[0066] In some embodiments of this application, the above deployment unit 301 may specifically be configured to: create a target folder on the object storage system, where the file name of the target folder corresponds to the version identifier of the target resource; upload the target resource to the target folder.

[0067] In some embodiments of the present application, the publishing device 300 of the above resources may further include a rollback unit, which is configured to: in response to a rollback operation triggered by the first user on the first terminal, upload a rollback entry file to the target server according to the version identifier pointed to by the rollback operation, and update the content delivery network, so that the user can access the rollback resources through the rollback entry file in the target server, where the rollback resources are stored in a folder corresponding to the version identifier pointed to by the rollback operation.

[0068] In some embodiments of the present application, the domain names of the above target server and the test server are different. The test server is configured to, when receiving a test request triggered by a third user on a third terminal, read target resources based on a target entry file on the test server, and feed back the target resources to the third terminal, so as to test the function of accessing the target resources through the target entry file.

[0069] It should be noted that, for the sake of convenience and brevity of description, the specific working process of the above resource publishing device 300 can refer to Figures 1 to 2 the corresponding process of the method, which will not be elaborated here.

[0070] As Figure 4 shown, it is a schematic diagram of a terminal provided by an embodiment of the present application. The terminal may refer to the aforementioned first terminal.

[0071] Among them, the terminal 4 may include: a processor 40, a memory 41, and a computer program 42 stored in the memory 41 and executable on the processor 40, such as a resource publishing program. When the processor 40 executes the computer program 42, the steps in the above-mentioned embodiments of the resource publishing method are implemented, such as Figure 1 the steps S101 to S103 shown. Alternatively, when the processor 40 executes the computer program 42, the functions of each module / unit in the above-mentioned device embodiments are implemented, such as Figure 3 the deployment unit 301, the test unit 302, and the publishing unit 303 shown.

[0072] The computer program may be divided into one or more modules / units. The one or more modules / units are stored in the memory 41 and executed by the processor 40 to complete the present application. The one or more modules / units may be a series of computer program instruction segments capable of performing specific functions, and these instruction segments are used to describe the execution process of the computer program in the terminal.

[0073] For example, the computer program may be divided into: a deployment unit, a test unit, and a publishing unit.

[0074] The specific functions of each unit are as follows: The deployment unit is used to deploy the target resource to the object storage system of the content delivery network and extract the target entry file bound with the access address of the target resource; the test unit is used to upload the target entry file to the test server, and the test server is used to test the target entry file; the publishing unit is used to, in response to the upload operation triggered by the first user on the first terminal when the test of the target entry file is completed, upload the target entry file to the target server and update the content delivery network so that the user can access the target resource through the target entry file in the target server.

[0075] The terminal may include, but is not limited to, a processor 40 and a memory 41. Those skilled in the art can understand that Figure 4 merely examples of the terminal, which do not constitute a limitation to the terminal, may include more or fewer components than shown in the figure, or combine certain components, or different components. For example, the terminal may also include input and output devices, network access devices, a bus, etc.

[0076] The so-called processor 40 may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0077] The memory 41 may be an internal storage unit of the terminal, such as the hard disk or memory of the terminal. The memory 41 may also be an external storage device of the terminal, such as a plug-in hard disk equipped on the terminal, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. Further, the memory 41 may also include both the internal storage unit and the external storage device of the terminal. The memory 41 is used to store the computer program and other programs and data required by the terminal. The memory 41 may also be used to temporarily store the data that has been output or will be output.

[0078] It should be noted that for the convenience and conciseness of description, the structure of the above terminal can also refer to the specific description of the structure in the method embodiments, which will not be elaborated here.

[0079] Those skilled in the art can clearly understand that for the convenience and conciseness of description, only the above division of each functional unit and module is used as an example. In actual applications, the above functions can be allocated to different functional units and modules according to needs, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiment can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. In addition, the specific names of each functional unit and module are only for the convenience of mutual distinction and do not limit the protection scope of the present application. The specific working processes of the units and modules in the above system can refer to the corresponding processes in the foregoing method embodiments, which will not be elaborated here.

[0080] In the above embodiments, the descriptions of the respective embodiments have their own emphases. For the parts not elaborated or recorded in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0081] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or by a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled professionals can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0082] In the embodiments provided in the present application, it should be understood that the disclosed device / terminal and method can be implemented in other ways. For example, the device / terminal embodiments described above are only illustrative. For example, the division of the module or unit is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling, direct coupling or communication connection can be through some interfaces, and the indirect coupling or communication connection of the device or unit can be in electrical, mechanical or other forms.

[0083] The unit described as a separation component may or may not be physically separated. The component shown as a unit may or may not be a physical unit, that is, it may be located in one place or distributed across multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0084] In addition, in each embodiment of the present application, each functional unit may be integrated in a processing unit, may exist independently physically for each unit, or two or more units may be integrated in one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0085] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such understanding, to implement all or part of the processes in the above-mentioned embodiment methods of the present application, it can also be completed by a computer program instructing relevant hardware. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, the steps of the above-mentioned various method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in the form of source code, object code, executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disc, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium, etc. It should be noted that the content included in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electrical carrier signals and telecommunication signals.

[0086] The above-mentioned embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A method for publishing a resource, characterized in that, Applied to a first terminal, the publishing method includes: Deploy the target resource to the object storage system of the content delivery network, and extract the target entry file bound with the access address of the target resource; Upload the target entry file to a test server, which is used to test the function of accessing the target resource through the target entry file; In response to the upload operation triggered by the first user on the first terminal when the test of the target entry file is completed, upload the target entry file to the target server, and update the content delivery network so that users can access the target resource through the target entry file in the target server.

2. The resource publishing method according to claim 1, wherein When the content delivery network is updated, the mirror cache server of the content delivery network reads and caches the target entry file stored in the target server, so that when the mirror cache server receives a resource access request triggered by a second user on a second terminal, it sends the target resource to the second terminal based on the target entry file cached in the mirror cache server.

3. The resource publishing method according to claim 1, characterized in that, The deploying the target resource to the object storage system of the content delivery network includes: Create a target folder on the object storage system, and the file name of the target folder corresponds to the version identifier of the target resource; Upload the target resource to the target folder.

4. The method for publishing resources according to claim 3, wherein The publishing method further includes: In response to the rollback operation triggered by the first user on the first terminal, upload the rollback entry file to the target server according to the version identifier pointed to by the rollback operation, and update the content delivery network so that users can access the rollback resource through the rollback entry file in the target server, where the rollback resource is stored in the folder corresponding to the version identifier pointed to by the rollback operation.

5. The method for publishing resources according to any one of claims 1 to 4, characterized in that The domain names of the target server and the test server are different. The test server is used to read the target resource based on the target entry file on the test server and feedback the target resource to the third terminal when receiving a test request triggered by a third user on a third terminal, so as to test the function of accessing the target resource through the target entry file.

6. A resource publishing device, characterized in that, Configured on a first terminal, the publishing device includes: A deployment unit for deploying the target resource to the object storage system of the content delivery network and extracting the target entry file bound with the access address of the target resource; A test unit for uploading the target entry file to a test server, which is used to test the function of accessing the target resource through the target entry file; A publishing unit for, in response to the upload operation triggered by the first user on the first terminal when the test of the target entry file is completed, uploading the target entry file to the target server and updating the content delivery network so that users can access the target resource through the target entry file in the target server.

7. The resource publishing device according to claim 6, wherein When the content delivery network is updated, the mirrored cache server of the content delivery network reads and stores the target entry file of the target server so that users can access the target resource based on the mirrored cache server.

8. The resource publishing device according to claim 6, characterized in that, The resource deployment unit is further configured to: create a target folder on the object storage system, where the target folder corresponds to the version of the target resource; and upload the target resource to the target folder.

9. A terminal, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the publishing method according to any one of claims 1 to 5.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the publishing method according to any one of claims 1 to 5.

Images