CN112559180A - Resource processing method and device, electronic equipment and storage medium - Google Patents

Abstract

The embodiment of the invention provides a resource processing method, a resource processing device, electronic equipment and a storage medium, wherein the method comprises the following steps: when an instruction for fusing front and rear end resources is received, deleting historical front end resources stored in a rear end project; packaging the resources to be packaged corresponding to the front end to obtain a resource package to be processed, and storing the resource package to be processed to a target storage position corresponding to the historical front end resources; the resource packet to be processed comprises a sub-resource packet to be updated and a sub-resource packet to be combined; calling a sub-resource packet to be updated, and updating the configuration content to be changed in the sub-resource packet to be updated into target configuration content to obtain a target sub-resource packet; and obtaining a target resource packet based on the target sub-resource packet and the sub-resource packet to be combined so as to run the application program based on the target resource packet. The technical scheme of the embodiment of the invention realizes the technical effect of automatically packaging and fusing the resources developed by the front end and the back end.

Description

Resource processing method and device, electronic equipment and storage medium

Technical Field

The embodiment of the invention relates to the technical field of computers, in particular to a resource processing method and device, electronic equipment and a storage medium.

Background

Currently, web development is gradually converted from a traditional development mode in which backend development is dominant to a development mode in which the front and back ends are separated.

The traditional development mode is mainly to develop a main combination FreeMarker template engine by using a rear-end Spring MVC framework. The front-end and back-end separation development mainly comprises front-end and back-end development respectively, the development is deployed after completion, and the front-end and back-end separation development is mainly adopted: the front end and the back end can be developed simultaneously and are independent of each other, so that the development efficiency can be improved, and further, the code coupling degree is low because the front end and the back end are independently developed.

However, when deployment is performed after code development is completed, independent deployment is needed for the front end and the back end, and when independent deployment is performed, the situations of different domain names or ports exist, and at this time, the calling of the front end program and the back end program has a problem of cross-domain, so that the technical problem of inconvenient calling is caused.

Disclosure of Invention

The invention provides a resource processing method, a resource processing device, electronic equipment and a storage medium, which are used for fusing and deploying resources developed by a front end and a back end into a running environment after the front end and the back end are independently developed, so that the cross-domain problem existing in calling of a front end program and a back end program is avoided, and the developing and deploying efficiency is improved.

In a first aspect, an embodiment of the present invention provides a resource processing method, where the method includes:

when an instruction for fusing front and rear end resources is received, deleting historical front end resources stored in a rear end project;

packaging resources to be packaged corresponding to a front end to obtain a resource package to be processed, and storing the resource package to be processed to a target storage position corresponding to the history front end resource; the resource packet to be processed comprises a sub-resource packet to be updated and a sub-resource packet to be combined;

calling the sub resource packet to be updated, and updating the configuration content to be changed in the sub resource packet to be updated into target configuration content to obtain a target sub resource packet;

and obtaining a target resource packet based on the target sub-resource packet and the sub-resource packet to be combined so as to run an application program based on the target resource packet.

In a second aspect, an embodiment of the present invention further provides a resource processing apparatus, where the apparatus is configured for web development, and includes:

the history front-end resource deleting module is used for deleting the history front-end resources stored in the back-end engineering when receiving an instruction for fusing the front-end and back-end resources;

the storage module is used for packaging the resources to be packaged corresponding to the front end to obtain resource packages to be processed and storing the resource packages to be processed to a target storage position corresponding to the history front end resources; the resource packet to be processed comprises a sub-resource packet to be updated and a sub-resource packet to be combined;

the target sub-resource packet determining module is used for calling the sub-resource packet to be updated and updating the configuration content to be changed in the sub-resource packet to be updated into target configuration content to obtain a target sub-resource packet;

and the target resource packet determining module is used for obtaining a target resource packet based on the target sub-resource packet and the sub-resource packet to be combined so as to run an application program based on the target resource packet.

In a third aspect, an embodiment of the present invention further provides an electronic device, where the electronic device includes:

one or more processors;

a storage device for storing one or more programs,

when the program is executed by the processor, the processor is caused to implement the resource processing method according to any one of the embodiments of the present invention.

In a fourth aspect, the present invention further provides a storage medium containing computer-executable instructions, which when executed by a computer processor, are used to perform the resource processing method according to any one of the embodiments of the present invention.

According to the technical scheme of the embodiment of the invention, when the instruction for fusing the front-end and rear-end resources is received, the historical front-end resources stored in the rear-end engineering are deleted, the resources to be packaged corresponding to the front end are packaged to obtain the resource package to be processed, and the resource package to be processed is stored to the target storage position corresponding to the historical front-end resources, wherein the resource package to be processed comprises the sub-resource package to be updated and the sub-resource package to be combined. The method comprises the steps of calling a sub-resource package to be updated, updating configuration content to be changed in the sub-resource package to be updated into target configuration content to obtain a target sub-resource package, obtaining the target resource package based on the target sub-resource package and the sub-resource package to be combined, running an application program based on the target resource package, automatically fusing resources at the front end and the rear end after independent development at the front end and the rear end is completed, deploying the resource package after fusing into a running environment, avoiding the problem that cross-domain exists in calling of the front end program and the rear end program when deployment is respectively carried out, and improving the technical effects of resource deployment efficiency and calling efficiency.

Drawings

In order to more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, a brief description is given below of the drawings used in describing the embodiments. It should be clear that the described figures are only views of some of the embodiments of the invention to be described, not all, and that for a person skilled in the art, other figures can be derived from these figures without inventive effort.

Fig. 1 is a schematic flowchart of a resource processing method according to an embodiment of the present invention;

fig. 2 is a flowchart illustrating a resource processing method according to an embodiment of the present invention;

fig. 3 is a flowchart illustrating a resource processing method according to a second embodiment of the present invention;

fig. 4 is a flowchart illustrating a resource processing method according to a second embodiment of the present invention;

fig. 5 is a flowchart illustrating a resource processing method according to a second embodiment of the present invention;

fig. 6 is a schematic flowchart of a resource processing method according to a third embodiment of the present invention;

fig. 7 is a schematic diagram of a resource processing apparatus module according to a fourth embodiment of the present invention;

fig. 8 is a schematic structural diagram of an electronic device according to a fifth embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.

Example one

Fig. 1 is a flowchart of a resource processing method according to an embodiment of the present invention, where this embodiment is applicable to a situation where updated front-end resources are merged with backend resources and deployed in a corresponding operating environment when a change in resources of a web front-end is detected after front-end and backend resources are merged, and the method may be executed by a resource processing apparatus, where the resource processing apparatus may be implemented in a software and/or hardware manner, and the resource processing apparatus may be integrated in an electronic device such as a computer or a server.

As shown in fig. 1, the method of the present embodiment includes:

and S110, deleting the historical front-end resource stored in the rear-end project when receiving the instruction of fusing the front-end and rear-end resources.

The front-end resources may include static resources and front-end code resources. The front-end resources can be used for resources of a website interface layout, and the website interface layout can be understood as showing static resources through front-end codes. Static assets can be images, video, audio, etc. The front-end code may include html (hypertext Markup Language) code, css (Cascading Style Sheet) code, js (javaScript) code, and the like. The back-end resource can be any code file corresponding to a computer program language, such as a java code file, a PHP file, a C # file, and the like.

The instruction for merging the front-end resource and the back-end resource can be understood as a command for merging the front-end resource and the back-end resource into the back-end project. Optionally, when it is detected that a user triggers a certain control or when it is detected that a change occurs in the front-end resource, a resource fusion instruction is automatically generated. That is, the instructions for front-end and back-end resource fusion may be: instructions generated upon detecting a change in front-end resources. The back-end engineering may include front-end resources and back-end resources. The back-end engineering can be the back-end engineering which is deployed in the operating environment after the front-end resource and the back-end resource are fused. The history front-end resource may be a front-end resource that is deployed inside the back-end project before the current time. The purpose of deleting the history front-end resource is that after the current-end resource changes, the history front-end resource needs to be deployed to a corresponding operating environment based on the changed resource, so that the currently stored history front-end resource needs to be deleted.

In this embodiment, deleting the calendar front-end resource may include at least one implementation. The first embodiment may be: and when the user clicks the button for updating the front-end resource on the front-end and back-end fusion interfaces, the server automatically deletes the historical front-end resource in the back-end project.

The second implementation may be that the historical front-end resources stored in the back-end project include css1 style files, and when it is detected that the front-end resources css1 style file becomes css2 style file, the stored css1 style file in the back-end project is deleted.

In particular, the resource fusion instructions may be generated when a user modification of a front-end resource, such as program code or otherwise, is detected. Based on the resource fusion instruction, a resource deletion module or a resource deletion program can be called to delete the front-end resources stored before the current time in the back-end engineering, so that the modified resources and the back-end resources are fused and then deployed in the corresponding operating environment.

Optionally, when receiving an instruction to merge front and back end resources, deleting the historical front end resource stored in the back end engineering, including: when an instruction of fusing resources developed by a front end and resources developed by a rear end is received, determining that the history front end resources are stored to a target storage position in the rear end project; deleting the historical front-end resources in the target storage location.

Wherein the target storage location has stored therein the calendar front end resource. In practical applications, the target storage location may be a specific location of the front-end resource after the front-end resource and the back-end resource are merged, for example, the location of the front-end resource after the front-end resource and the back-end resource are merged is a, and the target storage location is a. Deleting historical front-end resources of the target storage location is to place front-end updated resources at the target storage location to be merged with back-end resources.

Specifically, when an instruction of merging the front-end developed resource and the back-end developed resource is received, that is, when it is detected that a user triggers a certain control or when it is detected that the front-end resource changes, the storage location of the history front-end resource is acquired. The historical front-end resource stored in the target storage location is deleted.

Illustratively, as shown in fig. 2, in the software development stage, the front-end resources and the back-end resources may be developed simultaneously in a front-end and back-end separation mode, which may advantageously improve the efficiency of software development. Meanwhile, in order to enable the front-end engineering and the rear-end engineering to achieve the effect of high cohesion and low coupling, the later maintenance of the software is facilitated. In the deployment phase of the software, the front-end resources and the back-end resources can be fused and deployed to the corresponding operating environment.

S120, packaging the resource to be packaged corresponding to the front end to obtain a resource package to be processed, and storing the resource package to be processed to a target storage position corresponding to the history front end resource; the resource packet to be processed comprises a sub-resource packet to be updated and a sub-resource packet to be combined.

The updated front-end resource may be used as a resource to be packaged, for example, the unchanged front-end resource is a, the updated front-end resource is B, and the front-end resource B may be used as a resource to be packaged. Packaging the front-end resources: the front-end resources may be packaged by a packaging tool (webpack packaging tool). The resource packet to be processed may be a resource packet obtained by packaging the front-end resource. The target storage location may be a storage location for storing the history front-end resource in the back-end project, and is used for storing the resource package after the fusion processing. The sub resource package to be updated may be a resource package obtained by packaging html file resources. The sub-resource package to be combined may be a resource package obtained by packaging at least one front-end resource of the css file, the picture and the js. The resource packet corresponding to the front-end resource is divided into two sub-resource packets, which has the advantages that: the content in the corresponding resource packet can be modified based on the type corresponding to the modified resource packet, so that the analysis time of the front-end resource is shortened; furthermore, the front-end and rear-end resources are fused together, and later maintenance is facilitated.

The tool for packaging the front-end resource may be any packaging tool as long as the packaging function of the front-end resource can be realized.

Specifically, a classification rule of the resources to be packaged can be preset, and the resources to be packaged are divided into two types, for example, the resources are classified according to whether the resources need to be changed, the resources needing to be changed are used as the sub-resources to be updated, and the resources not needing to be changed are used as the sub-resources to be combined. After the resource division is finished, the corresponding resources can be respectively packed based on the packing tool, and the sub-resource package to be updated and the sub-resource package to be combined are obtained. After the resource package is obtained, the resource package can be stored to a target storage location corresponding to the historical front-end resource so as to be fused with the back-end resource, and the resource package which can be deployed to a corresponding operating environment is obtained.

Illustratively, the target storage location of the history front-end resource is src1, and the resource to be packaged corresponding to the front-end resource includes a cs style file (e.g., common. The sub-resources to be updated can comprise html files, and the sub-resources to be combined can comprise css style files, js files and picture files. And packaging the html files by using a packaging tool webpack to obtain a sub-resource package to be updated, packaging the cs-style files, the js files and the picture files of the sub-resources to be combined to obtain a sub-resource package to be combined, and storing the sub-resource package to be updated and the sub-resource package to be combined to a target storage position src1 to obtain a resource package preliminarily fused with the rear-end resources.

S130, the sub-resource packet to be updated is called, and the configuration content to be changed in the sub-resource packet to be updated is updated to be target configuration content, so that the target sub-resource packet is obtained.

The configuration content to be updated is the configuration content to be changed in each resource packet to be updated, for example, the content corresponding to a certain suffix name is the configuration content to be updated. The configuration content to be updated may include a port number or configuration content corresponding to a custom configuration variable. The target configuration content needs to be changed by the configuration content to be updated. If the suffix name of the configuration content to be changed is content A corresponding to txt, and the target configuration content is content B corresponding to txt, the configuration content A to be changed can be changed into the target configuration content B. And updating the configuration content to be changed in the sub resource packet to be updated into a resource packet obtained by the target configuration content, and taking the resource packet as a target resource packet.

Specifically, the sub-resource package to be updated is called according to the storage position of the sub-resource package to be updated, the configuration content corresponding to the configuration variable in the sub-resource package to be updated is obtained according to the preset configuration variable and the configuration content corresponding to the configuration variable, the configuration content corresponding to the configuration variable in the sub-resource package to be updated is updated into the configuration content corresponding to the preset configuration variable according to the configuration content corresponding to the configuration variable, and the target sub-resource package is obtained by updating the configuration content corresponding to the preset configuration variable in the sub-resource package to be updated.

S140, obtaining a target resource packet based on the target sub-resource packet and the sub-resource packet to be combined, and running an application program based on the target resource packet.

An application refers to a computer program that performs one or more particular functions.

Specifically, the target resource package is obtained according to the target sub-resource package and the sub-resource package to be combined. And obtaining the fused resource packet based on the target resource packet and the resource packet corresponding to the back-end resource stored in the target storage position. The fused resource package can be deployed to an application program, so that resources developed by different terminals are deployed to the corresponding application program as one application, namely, an operating environment.

According to the technical scheme of the embodiment of the invention, when the instruction for fusing the front-end and rear-end resources is received, the historical front-end resources stored in the rear-end engineering are deleted, the resources to be packaged corresponding to the front end are packaged to obtain the resource package to be processed, and the resource package to be processed is stored to the target storage position corresponding to the historical front-end resources to obtain the rear-end engineering to be fused, wherein the resource package to be processed comprises the sub-resource package to be updated and the sub-resource package to be combined. The method comprises the steps of calling a sub-resource package to be updated, updating configuration content to be changed in the sub-resource package to be updated into target configuration content to obtain a target sub-resource package, updating the configuration content to be changed in the sub-resource package to be updated into the target sub-resource package to enable the target sub-resource package to be adapted to a rear-end project, obtaining the target resource package based on the target sub-resource package and a sub-resource package to be combined, running an application program based on the target resource package, automatically fusing resources of a front end and a rear end after independent development of the front end and the rear end is completed, deploying the fused resource package into a running environment, avoiding the problem that cross-domain calling of the front end program and the rear end program exists when the resource package and the calling efficiency are respectively deployed, and improving the technical effects of resource deployment efficiency and calling efficiency.

Example two

Fig. 3 is a schematic flowchart of a resource processing method according to a second embodiment of the present invention, and based on the foregoing embodiment, S120 in the foregoing embodiment is optimized, and specific implementation of the optimization can be referred to in the following embodiment.

The technical terms that are the same as or corresponding to the above embodiments are not repeated herein.

As shown in fig. 3, the method of the present embodiment may specifically include:

s210, deleting the historical front-end resources stored in the rear-end engineering when receiving an instruction for fusing the front-end and rear-end resources.

S220, dividing the resources to be packaged updated at the front end into at least two types based on the packaging tool and the preset resource type to obtain the sub-resource packages to be updated and the sub-resource packages to be combined.

The packaging tool can be any front-end resource packaging tool, such as a webpack packaging tool. The resource type may be a type preset according to actual needs, and in this embodiment, the resource type may be divided into two types according to whether configuration content of the resource to be packaged needs to be changed. Whether the resource configuration content needs to be changed or not can be determined by the suffix name of the resource. For example, a resource with the suffix html is a resource that needs to be changed.

Specifically, when it is detected that the suffix name of the resource to be packaged is the suffix name of the resource to be packaged which needs to be changed, the resource to be packaged is determined as the sub-resource to be updated, and correspondingly, other resources to be packaged are determined as the sub-resources to be combined. Meanwhile, packaging each resource based on a packaging tool, for example, packaging the sub-resources to be updated to obtain a sub-resource package to be updated. And packaging the sub-resources to be combined to obtain a sub-resource package to be combined.

Illustratively, the resource to be packaged includes at least one of index. And presetting the suffix name of the resource to be changed as html. And starting packaging based on a packaging tool, packaging the resource to be packaged into a resource packet to be updated if the suffix name of the resource to be packaged is html, and packaging the rest of the resources together to be used as a sub-resource packet to be combined, such as resources of head.

And packaging the resources to be packaged at the front end, referring to fig. 4, packaging the resources with suffix names img, css and js in the resources at the front end together as a sub-resource package to be combined, and packaging the files with suffix names html as the sub-resource package to be updated.

S230, storing the sub-resource package to be updated under a first sub-directory of the target storage position, and storing the sub-resource package to be combined under a second sub-directory of the target storage position.

In computer applications, a directory refers to a folder. The first sub-directory may be used to store a folder of the sub-resource package to be updated. The second subdirectory may be for storing a combined sub-resource package.

Specifically, a target storage position of the history front-end resource is obtained, a first sub-directory in the target storage position is searched, and a sub-resource package to be updated is stored under the first sub-directory; and simultaneously, searching a second subdirectory in the target storage position, and storing the sub-resource packages to be combined under the second subdirectory.

For example, referring to fig. 4, the first sub-directory is resource, the second sub-directory is template directory, the sub-resource package to be combined is stored under the resource directory, and the sub-resource package to be updated is stored under the template directory. And copying the packed front-end resources to a back-end project.

S240, obtaining the sub-resource package to be updated from the first sub-directory, and determining the configuration content to be changed in the sub-resource package to be updated according to a preset change variable.

The modified variable, that is, the variable to be modified in the resource package to be updated, may be a name of some code, and the code may be specifically determined according to a corresponding scenario, which is not limited herein. The altering variables may include, but are not limited to, the following variables: development environment variables, test environment variables, pre-development environment variables, online environment variables, and global variables. The change variable may be a preset set variable and may be stored in a file responsible for collecting the environment variables.

Specifically, a change variable is preset, the update sub-resource package is obtained from the first directory, the change configuration content corresponding to the preset change variable is determined according to the preset change variable, and the configuration content to be changed in the sub-resource package to be updated is determined according to the preset change variable and the change configuration content corresponding to the preset change variable.

For example, an ENV file is created in a root directory of the backend engineering, an environment variable and a value corresponding to the environment variable are input in the ENV file, for example, NDOE _ ENV ═ depth PROT ═ 10086, and the configuration content corresponding to the environment variable PROT corresponding to the child resource package to be updated is determined 10086, that is, the configuration content to be changed of the child resource package to be updated is 10086.

S250, updating the configuration content to be changed into target configuration content adapted to the current deployment environment, and generating the target sub-resource package based on the updated target configuration content.

The target sub-resource package may be a resource package obtained by updating the configuration content to be changed.

Specifically, the target configuration content adapted to the current environment is obtained, the configuration content to be changed is updated to the target configuration content adapted to the current deployment environment according to the target configuration content adapted to the current environment, the updated target configuration content is obtained, and the target sub-resource package is generated according to the updated target configuration content.

S260, obtaining a target resource packet based on the target sub-resource packet and the sub-resource packet to be combined, and running an application program based on the target resource packet.

As a second alternative embodiment of the above embodiment, as shown in fig. 4 and fig. 5, the storage location of the historical front-end resource in the back-end project, that is, the old front-end resource, is determined, and the old front-end resource is deleted. Packaging img files, css files and js files in the modified new front-end resources together to obtain a sub-resource package to be combined, and storing the sub-resource package to a resource directory; and meanwhile, packaging index. After the storage is finished, according to actual corresponding variable information such as environment variables, global variables and the like of development, test, pre-launch, online and the like, html file content under a template directory is modified, the modified file is modified into a freemarker file to adapt to rear-end resources, and the resources in the file obtained at the moment are used as a target sub-resource package.

According to the technical scheme of the embodiment of the invention, when the instruction for fusing the front-end resource and the back-end resource is received, the historical front-end resource stored in the back-end engineering is deleted. Dividing resources to be packaged updated at the front end into at least two types based on a packaging tool and a preset resource type to obtain a sub-resource package to be updated and a sub-resource package to be combined, storing the sub-resource package to be updated under a first sub-directory of a target storage position, and storing the sub-resource package to be combined under a second sub-directory of the target storage position, so as to facilitate later maintenance of rear-end engineering. And acquiring the sub-resource package to be updated from the first sub-directory, determining the configuration content to be changed in the sub-resource package to be updated according to a preset change variable, updating the configuration content to be changed into the target configuration content adapted to the current deployment environment, and generating the target sub-resource package based on the updated target configuration content. The target resource package is obtained based on the target sub-resource package and the sub-resource packages to be combined, the application program is operated based on the target resource package, the resources of the front end and the back end are automatically fused after the front end and the back end are independently developed, the resource packages after fusion processing are deployed in the operation environment, the problem that cross-domain exists in calling of the front end program and the back end program when deployment is carried out respectively is avoided, and the technical effects of resource deployment efficiency and calling efficiency are improved.

EXAMPLE III

Fig. 6 is a schematic flowchart of a resource processing method according to a third embodiment of the present invention, and based on the foregoing embodiment, S140 in the foregoing embodiment is optimized, and specific implementation of the optimization can be referred to in the following embodiment.

The technical terms that are the same as or corresponding to the above embodiments are not repeated herein.

As shown in fig. 6, the method of the present embodiment may specifically include:

and S310, deleting the historical front-end resource stored in the rear-end project when receiving the instruction of fusing the front-end and rear-end resources.

S320, packaging the resource to be packaged corresponding to the front end to obtain a resource package to be processed, and storing the resource package to be processed to a target storage position corresponding to the history front end resource; the resource packet to be processed comprises a sub-resource packet to be updated and a sub-resource packet to be combined.

S330, calling the sub-resource packet to be updated, and updating the configuration content to be changed in the sub-resource packet to be updated into target configuration content to obtain a target sub-resource packet.

S340, obtaining the target resource package through fusion processing of the target sub-resource package, the sub-resource package to be combined and the back-end resource package corresponding to the back-end engineering, and running the application program based on the target resource package.

The target resource packet may be a resource packet obtained by fusing updated front-end resources and updated back-end resources.

Optionally, the obtaining the target resource package by fusing the target sub-resource package, the sub-resource package to be combined, and the back-end resource package corresponding to the back-end engineering includes: and performing fusion processing on the target sub-resource packet, the sub-resource packet to be combined and the back-end resource packet corresponding to the back-end project, and converting the resource packet subjected to fusion processing into a target format to obtain the target resource packet.

The target format is preset according to requirements, for example, the name or suffix name of the resource packet is modified into a format corresponding to a freemarker.

Specifically, after the target sub-resource package, the sub-resource package to be combined, and the back-end resource package are fused together, the target sub-resource package, the sub-resource package to be combined, and the back-end resource package are converted into a file in a target format, for example, an html file is modified into a freemarker file, and the modified whole resource is used as the target resource package. The target resource package can be deployed to the corresponding operating environment, the respective development of front-end and back-end resources is realized, and the technical effect of deployment as an application is achieved.

According to the technical scheme of the embodiment of the invention, when a command for fusing front-end and rear-end resources is received, historical front-end resources stored in a rear-end project are deleted, the resources to be packaged corresponding to the front end are packaged to obtain a resource package to be processed, the resource package to be processed is stored to a target storage position corresponding to the historical front-end resources, the resource package to be processed comprises a sub-resource package to be updated and a sub-resource package to be combined, the sub-resource package to be updated is called, the configuration content to be changed in the sub-resource package to be updated is updated to target configuration content to obtain a target sub-resource package, the target sub-resource package is obtained by fusing the target sub-resource package, the sub-resource package to be combined and the rear-end resource package corresponding to the rear-end project, the application program is operated based on the target resource package, the front-end and rear-end resources are automatically fused after the front-end and rear-end are independently developed, and the resource package after the fusion processing is deployed in the running environment, so that the problem that cross-domain exists in calling of front and back end programs when the resource package is deployed respectively is avoided, and the technical effects of resource deployment efficiency and calling efficiency are improved.

Example four

Fig. 7 is a schematic diagram of a resource processing apparatus module according to a fourth embodiment of the present invention, in which the resource processing apparatus according to the present invention is configured for web development, and the apparatus includes:

a history front-endresource deleting module 410, configured to delete the history front-end resource stored in the back-end project when receiving an instruction to merge front-end and back-end resources;

thestorage module 420 is configured to package a resource to be packaged corresponding to a front end to obtain a resource packet to be processed, and store the resource packet to be processed to a target storage location corresponding to the history front end resource; the resource packet to be processed comprises a sub-resource packet to be updated and a sub-resource packet to be combined;

a target sub-resourcepackage determining module 430, configured to invoke the sub-resource package to be updated, and update the configuration content to be changed in the sub-resource package to be updated into target configuration content, so as to obtain a target sub-resource package;

and a target resourcepackage determining module 440, configured to obtain a target resource package based on the target sub-resource package and the sub-resource package to be combined, so as to run an application based on the target resource package.

According to the technical scheme of the embodiment of the invention, when the history front-end resource deleting module receives the instruction of fusing the front-end and rear-end resources, the history front-end resources stored in the rear-end project are deleted. And packaging the resources to be packaged corresponding to the front end through a storage module to obtain a resource package to be processed, and storing the resource package to be processed to a target storage position corresponding to the historical front end resources, wherein the resource package to be processed comprises a sub-resource package to be updated and a sub-resource package to be combined. And calling the sub-resource packet to be updated through the target sub-resource packet determining module, and updating the configuration content to be changed in the sub-resource packet to be updated into the target configuration content to obtain the target sub-resource packet. The target resource package is obtained through the target resource package determining module based on the target sub-resource package and the sub-resource package to be combined, so that the application program is operated based on the target resource package, the resources of the front end and the back end are automatically fused after the front end and the back end are independently developed, the resource package after fusion processing is deployed in an operation environment, the problem that cross-domain exists in calling of the front end program and the back end program when deployment is carried out respectively is avoided, and the technical effects of resource deployment efficiency and calling efficiency are improved.

Optionally, the historical front-endresource deleting module 410 is configured to determine that the historical front-end resource is stored in the target storage location in the back-end project when an instruction for fusing the front-end developed resource and the back-end developed resource is received; deleting the historical front-end resources in the target storage location.

Optionally, thestorage module 420 is configured to divide the resources to be packaged updated at the front end into at least two types based on the packaging tool and the preset resource type, so as to obtain the sub-resource package to be updated and the sub-resource package to be combined; and storing the sub-resource packet to be updated and the sub-resource packet to be combined to the target storage position.

Optionally, thestorage module 420 is configured to store the resource package to be updated under a first sub-directory of the target storage location, and store the sub-resource package to be combined under a second sub-directory of the target storage location.

Optionally, thestorage module 420 is configured to obtain the resource package to be updated from the first sub-directory, and determine the configuration content to be changed in the sub-resource package to be updated according to a preset change variable; and updating the configuration content to be changed into target configuration content adapted to the current deployment environment, and generating the target sub-resource package based on the updated target configuration content.

Optionally, the target resourcepackage determining module 440 is configured to obtain the target resource package by performing fusion processing on the target sub-resource package, the sub-resource package to be combined, and the back-end resource package corresponding to the back-end engineering.

Optionally, the target resourcepackage determining module 440 is configured to perform fusion processing on the target sub-resource package, the sub-resource package to be combined, and the back-end resource package corresponding to the back-end engineering, and convert the resource package after the fusion processing into a target format to obtain the target resource package.

The resource processing device provided by the embodiment of the invention can execute the resource processing method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.

It should be noted that, the units and modules included in the apparatus are merely divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the embodiment of the invention.

EXAMPLE five

Fig. 8 is a schematic structural diagram of an electronic device according to a fifth embodiment of the present invention. FIG. 8 illustrates a block diagram of an exemplaryelectronic device 50 suitable for use in implementing embodiments of the present invention. Theelectronic device 50 shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiment of the present invention.

As shown in fig. 8,electronic device 50 is embodied in the form of a general purpose computing device. The components of theelectronic device 50 may include, but are not limited to: one or more processors orprocessing units 501, asystem memory 502, and abus 503 that couples the various system components (including thesystem memory 502 and the processing unit 501).

Bus 503 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures. By way of example, such 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.

Electronic device 50 typically includes a variety of computer system readable media. Such media may be any available media that is accessible byelectronic device 50 and includes both volatile and nonvolatile media, removable and non-removable media.

Thesystem memory 502 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)504 and/orcache memory 505. Theelectronic device 50 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only,storage system 506 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 8, and commonly referred to as a "hard drive"). Although not shown in FIG. 8, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to thebus 503 by one or more data media interfaces.Memory 502 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

A program/utility 508 having a set (at least one) ofprogram modules 507 may be stored, for instance, inmemory 502,such program modules 507 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment.Program modules 507 generally perform the functions and/or methodologies of embodiments of the invention as described herein.

Theelectronic device 50 may also communicate with one or more external devices 509 (e.g., keyboard, pointing device,display 510, etc.), with one or more devices that enable a user to interact with theelectronic device 50, and/or with any devices (e.g., network card, modem, etc.) that enable theelectronic device 50 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 511. Also, theelectronic device 50 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet) via thenetwork adapter 512. As shown, thenetwork adapter 512 communicates with the other modules of theelectronic device 50 over thebus 503. It should be appreciated that although not shown in FIG. 8, other hardware and/or software modules may be used in conjunction withelectronic device 50, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

Theprocessing unit 501 executes various functional applications and data processing, for example, implementing a resource processing method provided by an embodiment of the present invention, by executing a program stored in thesystem memory 502.

EXAMPLE six

An embodiment of the present invention also provides a storage medium containing computer-executable instructions, which when executed by a computer processor, perform a resource processing method.

The method comprises the following steps:

when an instruction for fusing front and rear end resources is received, deleting historical front end resources stored in a rear end project;

packaging resources to be packaged corresponding to a front end to obtain a resource package to be processed, and storing the resource package to be processed to a target storage position corresponding to the history front end resource; the resource packet to be processed comprises a sub-resource packet to be updated and a sub-resource packet to be combined;

calling the sub resource packet to be updated, and updating the configuration content to be changed in the sub resource packet to be updated into target configuration content to obtain a target sub resource packet;

and obtaining a target resource packet based on the target sub-resource packet and the sub-resource packet to be combined so as to run an application program based on the target resource packet.

Computer storage media for embodiments of the invention may employ 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. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for embodiments of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (10)

1. A method for processing resources, comprising:

when an instruction for fusing front and rear end resources is received, deleting historical front end resources stored in a rear end project;

packaging resources to be packaged corresponding to a front end to obtain a resource package to be processed, and storing the resource package to be processed to a target storage position corresponding to the history front end resource; the resource packet to be processed comprises a sub-resource packet to be updated and a sub-resource packet to be combined;

calling the sub resource packet to be updated, and updating the configuration content to be changed in the sub resource packet to be updated into target configuration content to obtain a target sub resource packet;

and obtaining a target resource packet based on the target sub-resource packet and the sub-resource packet to be combined so as to run an application program based on the target resource packet.

2. The method according to claim 1, wherein deleting the historical front-end resource stored in the back-end project when receiving the instruction to fuse the front-end resource and the back-end resource comprises:

when an instruction of fusing resources developed by a front end and resources developed by a rear end is received, determining that the history front end resources are stored to a target storage position in the rear end project;

deleting the historical front-end resources in the target storage location.

3. The method according to claim 1, wherein the packing the resource to be packed corresponding to the front end to obtain a resource packet to be processed and storing the resource packet to be processed to a target storage location corresponding to the history front end resource comprises:

dividing resources to be packaged updated at the front end into at least two types based on a packaging tool and a preset resource type to obtain a sub-resource package to be updated and a sub-resource package to be combined;

and storing the sub-resource packet to be updated and the sub-resource packet to be combined to the target storage position.

4. The method according to claim 3, wherein the storing the sub-resource package to be updated and the sub-resource package to be combined to the target storage location comprises:

and storing the sub-resource packages to be updated under a first sub-directory of the target storage position, and storing the sub-resource packages to be combined under a second sub-directory of the target storage position.

5. The method according to claim 4, wherein the retrieving the sub-resource package to be updated and updating the configuration content to be changed in the sub-resource package to be updated to the target configuration content to obtain the target sub-resource package comprises:

acquiring a resource package to be updated from the first subdirectory, and determining configuration content to be changed in the sub-resource package to be updated according to a preset change variable;

and updating the configuration content to be changed into target configuration content adapted to the current deployment environment, and generating the target sub-resource package based on the updated target configuration content.

6. The method according to claim 1, wherein the obtaining a target resource packet based on the target sub-resource packet and the sub-resource packet to be combined comprises:

and obtaining the target resource packet by fusing the target sub-resource packet, the sub-resource packet to be combined and the back-end resource packet corresponding to the back-end engineering.

7. The method according to claim 6, wherein the obtaining the target resource package by performing fusion processing on the target sub-resource package, the sub-resource package to be combined, and the backend resource package corresponding to the backend engineering comprises:

and performing fusion processing on the target sub-resource packet, the sub-resource packet to be combined and the back-end resource packet corresponding to the back-end project, and converting the resource packet subjected to fusion processing into a target format to obtain the target resource packet.

8. A resource processing apparatus, configured for web development, comprising:

the history front-end resource deleting module is used for deleting the history front-end resources stored in the back-end engineering when receiving an instruction for fusing the front-end and back-end resources;

the storage module is used for packaging the resources to be packaged corresponding to the front end to obtain resource packages to be processed and storing the resource packages to be processed to a target storage position corresponding to the history front end resources; the resource packet to be processed comprises a sub-resource packet to be updated and a sub-resource packet to be combined;

the target sub-resource packet determining module is used for calling the sub-resource packet to be updated and updating the configuration content to be changed in the sub-resource packet to be updated into target configuration content to obtain a target sub-resource packet;

and the target resource packet determining module is used for obtaining a target resource packet based on the target sub-resource packet and the sub-resource packet to be combined so as to run an application program based on the target resource packet.

9. An electronic device, characterized in that the electronic device comprises:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the resource handling method of any of claims 1-7.

10. A storage medium containing computer-executable instructions for performing the resource processing method of any one of claims 1-7 when executed by a computer processor.

Images