CN110209983B - Method and device for deploying web project of webpage - Google Patents
Method and device for deploying web project of webpage Download PDFInfo
- Publication number
- CN110209983B CN110209983B CN201910457441.7A CN201910457441A CN110209983B CN 110209983 B CN110209983 B CN 110209983B CN 201910457441 A CN201910457441 A CN 201910457441A CN 110209983 B CN110209983 B CN 110209983B
- Authority
- CN
- China
- Prior art keywords
- web
- file
- folder
- target
- target file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the application provides a method and a device for deploying a web project of a webpage, which relate to the technical field of computers, wherein the web project comprises a web front end and a first web back end, and the method comprises the following steps: the method comprises the steps of obtaining target files in the web front end, wherein each target file comprises a configuration file and a static resource file, determining a target folder corresponding to each target file in the first web rear end according to a file type corresponding to the target file and a preset moving rule, moving the target file to the target folder, modifying an access path corresponding to the static resource file in the moved configuration file, obtaining a second web rear end integrated with the web front end, and deploying the second web rear end. By the adoption of the method and the device, the stability of the server can be improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for deploying a web project.
Background
At present, technicians usually develop and deploy a web page (web) project in a front-end and back-end separation manner, that is, the technicians separately develop and deploy a web front end and a web back end in the web project. The front-end and back-end separation mode is adopted to develop and deploy the web project, development, test, deployment and optimization of the front end and the back end of the web can be guaranteed to be independent and not influenced mutually, and therefore development efficiency is improved.
Based on the front-end and back-end separation manner, when a technician deploys a web project, the technician needs to install environments required for the operation of the front end and the back end of the web on the server, and deploy the front end service and the back end service of the web in the respective environments.
However, for a server with poor performance, two different environments and services are installed at the same time, which may seriously occupy the resources of the server, resulting in poor stability of the server.
Disclosure of Invention
The embodiment of the application aims to provide a method and a device for deploying a web project, which can improve the stability of a server. The specific technical scheme is as follows:
in a first aspect, a method of deploying a web project, the web project comprising a web front end and a first web back end, the method comprising:
acquiring each target file in the web front end, wherein each target file comprises a configuration file and a static resource file;
for each target file in the target files, determining a target folder corresponding to the target file in the first web back end according to the file type corresponding to the target file and a preset moving rule, and moving the target file to the target folder;
modifying an access path corresponding to the static resource file in the moved configuration file to obtain a second web back end integrating the web front end;
deploying the second web backend.
Optionally, the file type includes a configuration type, a compilation type, a page type, a code type, and a static resource type.
Optionally, the determining, according to the file type corresponding to the target file and a preset moving rule, a target folder corresponding to the target file in the first web backend, and moving the target file to the target folder includes:
when the file type of the target file is the configuration type or the compiling type, determining that a target folder corresponding to the target file in the first web back end is a root directory folder, and moving the target file to the root directory folder of the first web back end;
when the file type of the target file is the page type or the code type, determining that a target folder corresponding to the target file in the first web backend is a web application folder in a root directory folder, and moving the target file to the web application folder of the root directory folder of the first web backend;
and when the file type of the target file is the static resource type, determining that the target file corresponds to the static folder of the resource folder of which the target folder in the first web backend is the root directory folder, and moving the target file to the static folder of the resource folder of the root directory folder in the first web backend.
Optionally, the deploying the second web backend includes:
compiling and packaging the second web back end to obtain an executable file;
and running the executable file in a running environment of the first web backend.
In a second aspect, an apparatus for deploying a web project, the web project comprising a web front end and a first web back end, the apparatus comprising:
the acquisition module is used for acquiring each target file in the web front end, wherein each target file comprises a configuration file and a static resource file;
a moving module, configured to determine, for each of the target files, a target folder corresponding to the target file in the first web backend according to a file type corresponding to the target file and a preset moving rule, and move the target file to the target folder;
the modification module is used for modifying the access path corresponding to the static resource file in the moved configuration file to obtain a second web back end integrating the web front end;
and the deployment module is used for deploying the second web backend.
Optionally, the file type includes a configuration type, a compilation type, a page type, a code type, and a static resource type.
Optionally, the moving module is specifically configured to:
when the file type of the target file is the configuration type or the compiling type, determining that a target folder corresponding to the target file in the first web back end is a root directory folder, and moving the target file to the root directory folder of the first web back end;
when the file type of the target file is the page type or the code type, determining that a target folder corresponding to the target file in the first web backend is a web application folder in a root directory folder, and moving the target file to the web application folder of the root directory folder of the first web backend;
and when the file type of the target file is the static resource type, determining that the target file corresponds to the static folder of the resource folder of which the target folder in the first web backend is the root directory folder, and moving the target file to the static folder of the resource folder of the root directory folder in the first web backend.
Optionally, the deployment module is specifically configured to:
compiling and packaging the second web back end to obtain an executable file;
and running the executable file in a running environment of the first web backend.
In a third aspect, an electronic device is provided, which includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete communication with each other through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of any of the first aspect when executing a program stored in the memory.
In a fourth aspect, a computer-readable storage medium is provided, having stored thereon a computer program which, when being executed by a processor, carries out the method steps of any of the first aspects.
In a fifth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any of the first aspects above.
According to the method and the device for deploying the web project, the server acquires each target file in the web front end. Wherein, each target file comprises a configuration file and a static resource file. Then, aiming at each target file in the target files, the server determines a target folder corresponding to the target file in the first web back end according to the file type corresponding to the target file and a preset moving rule, moves the target file into the target folder, and modifies an access path corresponding to a static resource file in the moved configuration file to obtain a second web back end integrated with the web front end. The server then deploys the second web backend. Therefore, when the server deploys the web project, the target file in the web front end is integrated into the web back end for uniform deployment, and only the environment required by the operation of the web back end is required to be installed in the server and the web back end service is required to be installed in the environment, so that the number of the environment and the service in the server is reduced, the occupation of the environment and the service in the server on resources is reduced, and the stability of the server is improved.
Of course, not all advantages described above need to be achieved at the same time in the practice of any one product or method of the present application.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.
FIG. 1 is a flow chart of a method for deploying a web project according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a deployment apparatus for a web project according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.
The embodiment of the application provides a method for deploying a web project, which can be applied to a web system. In particular, the method may be applied to a server for deploying a web project in a web system. The web project may include, among other things, a web front end and a web back end. The web front end can be an vue frame, a reacact frame or other types of frames; the web backend may be a spring boot frame, or may be other types of frames, and the embodiments of the present application are not limited. Among these, the vue framework is a set of progressive frameworks for building user interfaces, unlike other large frameworks, the vue framework is designed to be applied layer by layer from the bottom up. In addition, the Spring boot framework is a brand new framework designed for simplifying Spring Web development, and compared with the traditional framework, the Spring boot framework reduces a lot of configurations and increases development efficiency. Both the vue frame and the spring boot frame are existing frames and will not be described herein.
The following describes, in detail, a method for deploying a web project provided in an embodiment of the present application, with reference to a specific embodiment, where the web project includes a web front end and a first web back end, as shown in fig. 1, and the specific steps are as follows:
step 101, obtaining each target file in the web front end.
Wherein, each target file at least comprises a configuration file and a static resource file.
In implementation, when the server needs to deploy the web project, in order to reduce occupation of server resources by the web project, the server may integrate the web front end into the first web back end for uniform deployment. Thus, the server may obtain the file to be integrated (i.e., the target file) in the web front end. Each target file at least comprises a configuration file and a static resource file, and can also comprise other files.
Step 102, for each target file in each target file, determining a target folder corresponding to the target file in the first web backend according to the file type corresponding to the target file and a preset moving rule, and moving the target file to the target folder.
In implementation, the server may store a movement rule in advance, where the movement rule may be a correspondence between a file type of each file in the web front end and a folder in the first web back end. The movement rules may be set by a technician according to the frame types of the web front end and the web back end. Wherein the technician can set the movement rule based on the following principle: (1) ensuring that the files of the web front end and the first web back end are separately stored so as to be convenient for developers to carry out independent iterative development and code warehouse management on the web front end and the first web back end respectively; (2) the calling of the compiling tools of the web front end and the first web back end to respective code files is not influenced, so that the code files in the web front end and the first web back end can be normally compiled; (3) the deployment is convenient.
After the server obtains each target file in the web front end, for each target file in each target file, the server may determine a target folder corresponding to the target file in the first web back end according to a file type corresponding to the target file and a preset movement rule. The server may then move the target file into the target folder.
Optionally, the file type corresponding to the target file in the web front end may include a configuration type, a compilation type, a page type, a code type, and a static resource type. For web front ends with different frame types, file types corresponding to target files in the web front ends are also different, and therefore, the file types corresponding to the target files in the web front ends are not limited in the embodiments of the present application.
Optionally, the movement rule set in the server may be different according to different types of the web front end framework and the first web back end framework. The embodiment of the present application provides a feasible implementation manner, and the processing procedure is that when the file type of the target file is a configuration type or a compilation type, the server may determine that a target folder corresponding to the target file in the first web backend is a root directory folder, and move the target file to the root directory folder in the first web backend. When the file type of the target file is a page type or a code type, the server may determine that the target folder corresponding to the target file in the first web backend is a web application folder in the root directory folder, and move the target file to the web application folder of the root directory folder in the first web backend. When the file type of the target file is a static resource type, the server may determine that a target folder corresponding to the target file in the first web backend is a static folder of a resource folder of the root directory folder, and move the target file to the static folder of the resource folder of the root directory folder of the first web backend.
For example, assuming that the front end of the web is an vue frame and the back end of the web is a spring boot frame, the server may move the compiled files and configuration files in the vue frame to the root directory folder of the spring boot frame, i.e., the src folder and the pot file of the spring boot frame are in the root directory folder. The server may move the page file and the code file in the vue frame to the web application (i.e., web app) folder of the root directory file of the spring boot frame, and the server may move the static resource file in the vue frame to the static (i.e., static) file of the resource (i.e., recourse) folder of the root directory folder of the spring boot frame.
It should be noted that, a technician may modify the webpack-related configuration file to implement a function of automatically moving the target file of the front web end to the target folder of the back web end.
And 103, modifying the access path corresponding to the static resource file in the moved configuration file to obtain a second web back end of the integrated web front end.
In implementation, after the server moves the target file in the web front end to the target folder in the first web back end, in order to ensure that some target files (such as page files and code files) after moving in the web front end can correctly call the static resource file, the server may further modify an access path corresponding to the static resource file in the moved configuration file. That is, for a static resource file in the moved configuration file, the server may modify the original access path in the configuration file to a storage path corresponding to a folder in the first web backend storing the moved static resource file.
And 104, deploying the second web backend.
In implementation, after obtaining the second web backend integrated with the web front end, the server may deploy the second web backend. In this way, a technician only needs to install the environment required by the operation of the web backend in the server and operate the web backend service in the environment, so that the number of the environments and the services in the server is reduced, the occupation of the environments and the services in the server on server resources is reduced, and the stability of the server is improved.
Optionally, the process of the server deploying the second web backend is as follows: and compiling and packaging the second web back end to obtain an executable file, and running the executable file in the running environment of the first web back end.
In implementation, the server may be pre-installed with a runtime environment of the first web backend. After the server obtains the second web back end of the integrated web front end, the server can start a compiling and packaging program in the second web back end, and the compiling and packaging processing is carried out on the second web back end to obtain the executable file. The server may then run the executable file in a runtime environment of the first web backend to provide the web service.
In the embodiment of the application, the server acquires each target file in the web front end. Wherein, each target file comprises a configuration file and a static resource file. Then, aiming at each target file in the target files, the server determines a target folder corresponding to the target file in the first web back end according to the file type corresponding to the target file and a preset moving rule, moves the target file into the target folder, and modifies an access path corresponding to a static resource file in the moved configuration file to obtain a second web back end integrated with the web front end. The server then deploys the second web backend. Therefore, when the server deploys the web project, the target file in the web front end is integrated into the web back end for uniform deployment, and only the environment required by the operation of the web back end is required to be installed in the server and the web back end service is required to be installed in the environment, so that the number of the environment and the service in the server is reduced, the occupation of the environment and the service in the server on resources is reduced, and the stability of the server is improved.
Based on the same technical concept, an embodiment of the present application further provides a deployment apparatus for a web project, as shown in fig. 2, the deployment apparatus includes:
an obtaining module 210, configured to obtain each target file in the web front end, where each target file includes a configuration file and a static resource file;
a moving module 220, configured to determine, for each target file in the target files, a target folder corresponding to the target file in the first web backend according to a file type corresponding to the target file and a preset moving rule, and move the target file to the target folder;
a modifying module 230, configured to modify, in the moved configuration file, an access path corresponding to the static resource file, to obtain a second web backend integrated with the web front end;
and the deployment module 240 is configured to deploy the second web backend.
Optionally, the file type includes a configuration type, a compilation type, a page type, a code type, and a static resource type.
Optionally, the moving module 220 is specifically configured to:
when the file type of the target file is the configuration type or the compiling type, determining that a target folder corresponding to the target file in the first web back end is a root directory folder, and moving the target file to the root directory folder of the first web back end;
when the file type of the target file is the page type or the code type, determining that a target folder corresponding to the target file in the first web backend is a web application folder in a root directory folder, and moving the target file to the web application folder of the root directory folder of the first web backend;
and when the file type of the target file is the static resource type, determining that the target file corresponds to the static folder of the resource folder of which the target folder in the first web backend is the root directory folder, and moving the target file to the static folder of the resource folder of the root directory folder in the first web backend.
Optionally, the deployment module 240 is specifically configured to:
compiling and packaging the second web back end to obtain an executable file;
the executable file is run in a runtime environment of the first web backend.
In the embodiment of the application, the server acquires each target file in the web front end. Wherein, each target file comprises a configuration file and a static resource file. Then, aiming at each target file in the target files, the server determines a target folder corresponding to the target file in the first web back end according to the file type corresponding to the target file and a preset moving rule, moves the target file into the target folder, and modifies an access path corresponding to a static resource file in the moved configuration file to obtain a second web back end integrated with the web front end. The server then deploys the second web backend. Therefore, when the server deploys the web project, the target file in the web front end is integrated into the web back end for uniform deployment, and only the environment required by the operation of the web back end is required to be installed in the server and the web back end service is required to be installed in the environment, so that the number of the environment and the service in the server is reduced, the occupation of the environment and the service in the server on resources is reduced, and the stability of the server is improved.
Based on the same technical concept, the embodiment of the present application further provides an electronic device, as shown in fig. 3, including a processor 301, a communication interface 302, a memory 303, and a communication bus 304, where the processor 301, the communication interface 302, and the memory 303 complete mutual communication through the communication bus 304,
a memory 303 for storing a computer program;
the processor 301, when executing the program stored in the memory 303, implements the following steps:
acquiring each target file in the web front end, wherein each target file comprises a configuration file and a static resource file;
for each target file in the target files, determining a target folder corresponding to the target file in the first web back end according to the file type corresponding to the target file and a preset moving rule, and moving the target file to the target folder;
modifying an access path corresponding to the static resource file in the moved configuration file to obtain a second web back end integrating the web front end;
deploying the second web backend.
Optionally, the file type includes a configuration type, a compilation type, a page type, a code type, and a static resource type.
Optionally, the determining, for each target file in the target files, a target folder corresponding to the target file in the first web backend according to a file type corresponding to the target file and a preset moving rule, and moving the target file to the target folder includes:
when the file type of the target file is the configuration type or the compiling type, determining that a target folder corresponding to the target file in the first web back end is a root directory folder, and moving the target file to the root directory folder of the first web back end;
when the file type of the target file is the page type or the code type, determining that a target folder corresponding to the target file in the first web backend is a web application folder in a root directory folder, and moving the target file to the web application folder of the root directory folder of the first web backend;
and when the file type of the target file is the static resource type, determining that the target file corresponds to the static folder of the resource folder of which the target folder in the first web backend is the root directory folder, and moving the target file to the static folder of the resource folder of the root directory folder in the first web backend.
Optionally, the deploying the second web backend includes:
compiling and packaging the second web back end to obtain an executable file;
and running the executable file in a running environment of the first web backend.
The communication bus mentioned in the electronic device may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface is used for communication between the electronic equipment and other equipment.
The Memory may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other Programmable logic devices, discrete Gate or transistor logic devices, or discrete hardware components.
Based on the same technical concept, the embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the deployment method of the web project described above.
Based on the same technical concept, the embodiment of the present application also provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the above-mentioned method for deploying the web project.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only for the preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application are included in the protection scope of the present application.
Claims (6)
1. A method of deploying a web project of a web page, the web project comprising a web front end and a first web back end, the method comprising:
acquiring each target file in the web front end, wherein each target file comprises a configuration file and a static resource file;
for each target file in the target files, determining a target folder corresponding to the target file in the first web back end according to the file type corresponding to the target file and a preset moving rule, and moving the target file to the target folder;
modifying an access path corresponding to the static resource file in the moved configuration file to obtain a second web back end integrating the web front end;
deploying the second web backend;
the file types comprise configuration types, compiling types, page types, code types and static resource types;
the determining, according to the file type corresponding to the target file and a preset moving rule, a target folder corresponding to the target file in the first web backend, and moving the target file to the target folder includes:
when the file type of the target file is the configuration type or the compiling type, determining that a target folder corresponding to the target file in the first web back end is a root directory folder, and moving the target file to the root directory folder of the first web back end;
when the file type of the target file is the page type or the code type, determining that a target folder corresponding to the target file in the first web backend is a web application folder in a root directory folder, and moving the target file to the web application folder of the root directory folder of the first web backend;
and when the file type of the target file is the static resource type, determining that the target file corresponds to the static folder of the resource folder of which the target folder in the first web backend is the root directory folder, and moving the target file to the static folder of the resource folder of the root directory folder in the first web backend.
2. The method of claim 1, wherein deploying the second web backend comprises:
compiling and packaging the second web back end to obtain an executable file;
and running the executable file in a running environment of the first web backend.
3. An apparatus for deploying a web project of a web page, the web project comprising a web front end and a first web back end, the apparatus comprising:
the acquisition module is used for acquiring each target file in the web front end, wherein each target file comprises a configuration file and a static resource file;
a moving module, configured to determine, for each of the target files, a target folder corresponding to the target file in the first web backend according to a file type corresponding to the target file and a preset moving rule, and move the target file to the target folder;
the modification module is used for modifying the access path corresponding to the static resource file in the moved configuration file to obtain a second web back end integrating the web front end;
the deployment module is used for deploying the second web backend;
the file types comprise configuration types, compiling types, page types, code types and static resource types;
the moving module is specifically configured to:
when the file type of the target file is the configuration type or the compiling type, determining that a target folder corresponding to the target file in the first web back end is a root directory folder, and moving the target file to the root directory folder of the first web back end;
when the file type of the target file is the page type or the code type, determining that a target folder corresponding to the target file in the first web backend is a web application folder in a root directory folder, and moving the target file to the web application folder of the root directory folder of the first web backend;
and when the file type of the target file is the static resource type, determining that the target file corresponds to the static folder of the resource folder of which the target folder in the first web backend is the root directory folder, and moving the target file to the static folder of the resource folder of the root directory folder in the first web backend.
4. The apparatus according to claim 3, wherein the deployment module is specifically configured to:
compiling and packaging the second web back end to obtain an executable file;
and running the executable file in a running environment of the first web backend.
5. An electronic device is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing mutual communication by the memory through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of any of claims 1-2 when executing a program stored in the memory.
6. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method steps of any one of the claims 1-2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910457441.7A CN110209983B (en) | 2019-05-29 | 2019-05-29 | Method and device for deploying web project of webpage |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910457441.7A CN110209983B (en) | 2019-05-29 | 2019-05-29 | Method and device for deploying web project of webpage |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110209983A CN110209983A (en) | 2019-09-06 |
| CN110209983B true CN110209983B (en) | 2021-06-04 |
Family
ID=67789276
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910457441.7A Active CN110209983B (en) | 2019-05-29 | 2019-05-29 | Method and device for deploying web project of webpage |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110209983B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112463324A (en) * | 2020-11-25 | 2021-03-09 | 银盛支付服务股份有限公司 | Method for realizing front-end and back-end separation, computer equipment and storage medium |
| CN112487339B (en) * | 2020-12-11 | 2023-05-26 | 杭州安恒信息技术股份有限公司 | Response method, device, equipment and storage medium for Web page request |
| CN112559180B (en) * | 2020-12-16 | 2024-03-26 | 微医云(杭州)控股有限公司 | Resource processing method and device, electronic equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108062330A (en) * | 2016-11-09 | 2018-05-22 | 湖南移商动力网络技术有限公司 | A kind of solution based on O2O system electric business platforms |
| CN109656617A (en) * | 2018-11-30 | 2019-04-19 | 武汉烽火信息集成技术有限公司 | A kind of front end Web Service dispositions method, storage medium, electronic equipment and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7693841B1 (en) * | 2004-10-14 | 2010-04-06 | A9.Com, Inc. | Providing parallel generic web site supporting anonymous or semi-anonymous internet activity |
-
2019
- 2019-05-29 CN CN201910457441.7A patent/CN110209983B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108062330A (en) * | 2016-11-09 | 2018-05-22 | 湖南移商动力网络技术有限公司 | A kind of solution based on O2O system electric business platforms |
| CN109656617A (en) * | 2018-11-30 | 2019-04-19 | 武汉烽火信息集成技术有限公司 | A kind of front end Web Service dispositions method, storage medium, electronic equipment and system |
Non-Patent Citations (1)
| Title |
|---|
| 《springboot+vue的前后端分离与合并方案》;我在代码…;《http://zhuanlan.zhihu,con/p/31720281?utm_source=wechat_session》;20171205;第1-6页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110209983A (en) | 2019-09-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107025559B (en) | Service processing method and device | |
| CN110209983B (en) | Method and device for deploying web project of webpage | |
| US10430172B2 (en) | Re-configuration in cloud computing environments | |
| US11481200B1 (en) | Checking source code validity at time of code update | |
| CN106648755B (en) | Method and device for dynamically loading dex in android art environment | |
| US8615743B2 (en) | Adaptive compiled code | |
| CN111124480B (en) | Method and device for generating application program package, electronic equipment and storage medium | |
| CN107273126B (en) | Application development method and device | |
| CN111240987B (en) | Method and device for detecting migration program, electronic equipment and computer readable storage medium | |
| CN110334031B (en) | Memory allocation code detection method and device, computer equipment and storage medium | |
| CN113094085A (en) | Component integration method and device, computer-readable storage medium and electronic equipment | |
| CN113778477A (en) | File processing method and device, computer readable storage medium and electronic device | |
| CN111385661B (en) | Method, device, terminal and storage medium for voice control of full screen playing | |
| CN110968333B (en) | Configuration information replacement method and device, machine-readable storage medium and processor | |
| CN109756948B (en) | Method and device for connecting wireless access point through application in user equipment | |
| CN111443920B (en) | Frame migration method and device | |
| US11947966B2 (en) | Identifying computer instructions enclosed by macros and conflicting macros at build time | |
| US9369352B1 (en) | Method of capturing server and operating system metrics for virtual to physical topology reporting | |
| CN113986744A (en) | Method and device for testing warehouse and table components and storage medium | |
| CN114490103A (en) | Operating system interface calling method and device and electronic equipment | |
| CN110704295A (en) | Data calling method, device, equipment and system | |
| US20240103853A1 (en) | Code maintenance system | |
| CN111736847B (en) | Script language mapping method, electronic device and readable storage medium | |
| CN102262545A (en) | Program installing method and device | |
| CN117311792A (en) | Version number updating method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |