A method and apparatus for deploying a web project

Abstract

The application provides a web project deployment method and device, the method comprising: obtaining a web project package; unpacking the web project package to obtain web project content; creating an access site for storing the web project content and creating a static route corresponding to the access site; when a terminal network layer is successfully started, storing the web project content in the access site and adding a directory of the static route in front of a path in a front-end html page; wherein the access site is a shunt site of a back end. It can be seen that the method and device can perform maintenance work without a new site project, thereby reducing the time cost and labor cost of web project maintenance; meanwhile, the compatibility problem in the traditional method can be solved, thereby increasing work efficiency and guaranteeing the effect of site connection.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of Internet, in particular to a web project deployment method and device. BACKGROUND

[0002] With the rapid development of network technology, many users have upgraded from communication text, communication pictures to communication video. However, behind the convenience, there is interaction between many data sites.

[0003] Currently, when a new site interacts with a terminal site, the new site usually independently creates, generates and maintains the strategy configuration. However, once the terminal site is updated or optimized, the new site will also face the corresponding maintenance work. Specifically, this method makes the maintenance cost of the web project high and long, and also affects the compatibility between sites due to various modifications, so that the multiple sites cannot be effectively connected. SUMMARY

[0004] The purpose of the embodiments of the present application is to provide a web project deployment method and device, which can perform maintenance work without a new site project, thereby reducing the time cost and labor cost of web project maintenance; at the same time, it can also solve the compatibility problem in the traditional method, thereby increasing the work efficiency and ensuring the effect of site connection.

[0005] The first aspect of the embodiments of the present application provides a web project deployment method, comprising:

[0006] obtaining a web project package;

[0007] unpacking the web project package to obtain web project content;

[0008] creating an access site for storing the web project content, and creating a static route corresponding to the access site;

[0009] storing the web project content in the access site when the terminal network layer is successfully started, and adding the directory of the static route in front of the front-end html page introduction path; wherein the access site is a shunt site of the back end.

[0010] In the implementation process, the method can acquire the web project package first; it can be seen that the acquisition of the web project package is the premise of the deployment of the web project, and ensuring the implementation of this step can effectively guarantee the stable deployment of the web project. Then, the method unpacks the web project package to obtain the web project content; it can be seen that the method can run the uploaded web project package to obtain the corresponding web business code, thereby preparing data for subsequent deployment. Thereafter, the method creates an access site for storing the web project content and creates a static route corresponding to the access site; it can be seen that the method can create a corresponding folder and create a corresponding static route, thereby starting the terminal network layer and using it as a connection means between the front end and the back end, further facilitating the deployment of the web project. Finally, the method stores the web project content into the shunt site of the back end when the terminal network layer is successfully started, and adds the directory of the static route in front of the path in the front-end html page. It can be seen that the method can deploy based on the front end and the back end, thereby avoiding the maintenance of new site projects, and thus realizing the low-cost, high-compatibility, and high-efficiency web project deployment effect, and being conducive to guaranteeing the connection between sites.

[0011] Further, the method further comprises:

[0012] detecting whether a web project deployment request is received;

[0013] when the web project deployment request is received, performing the step of acquiring the web project package.

[0014] In the implementation process, the method can detect in advance whether a web project deployment request is received; and when the web project deployment request is received, the step of acquiring the web project package is performed. It can be seen that the method can carry out corresponding deployment operations based on the deployment request issued by the user, thereby making the method more convenient for users to use and operate.

[0015] Further, the step of acquiring the web project package comprises:

[0016] acquiring the web project package imported by the user on the terminal interface layer.

[0017] In the implementation process, the method can independently open a window on the interface layer of the terminal to receive the imported web project, wherein the web project can include js text, css text, html text, and back-end business processing code. It can be seen that the method can acquire the web project package based on the import operation, thereby being able to open an interface for custom deployment for the user, and thus realizing better deployment of the web project.

[0018] Further, after the step of creating the access site for storing the web project content and creating the static route corresponding to the access site, the method further comprises:

[0019] creating a network configuration file according to the access site and the static route through a terminal network layer;

[0020] starting the terminal network layer based on the network configuration file.

[0021] In the implementation process, the method can send the created access site and static route to the terminal network layer, so that the terminal network layer can create a network configuration file including a network protocol and configuration according to the access site and the static route, and further start the terminal network layer based on the network configuration file. It can be seen that the method can realize automatic configuration and starting of the terminal network layer, thereby providing convenience for deployment of the web project.

[0022] Further, after the step of storing the web project content in the access site and adding the directory of the static route in front of the path introduced in the front-end html page, the method further comprises:

[0023] outputting deployment completion information.

[0024] In the implementation process, the method can output corresponding deployment completion information after completing the deployment of the web project, so that the user knows that the deployment has been completed, thereby facilitating the user to carry out subsequent work.

[0025] A second aspect of the embodiments of the present application provides a web project deployment device, which comprises:

[0026] an acquisition unit configured to acquire a web project package;

[0027] a unpacking unit configured to unpack the web project package to obtain web project content;

[0028] a creating unit configured to create an access site for storing the web project content, and create a static route corresponding to the access site;

[0029] a deployment unit configured to, when a terminal network layer is successfully started, store the web project content in the access site, and add a directory of the static route in front of a path introduced in a front-end html page; wherein the access site is a shunt site of a back-end.

[0030] In the implementation process, the device can acquire a web project package through an acquisition unit; unpack the web project package through an unpacking unit to obtain web project content; create an access site for storing the web project content through a creating unit, and create a static route corresponding to the access site; then store the web project content in the access site when the terminal network layer is successfully started through a deploying unit, and add the directory of the static route before the path in the front-end html page; wherein the access site is a shunt site of the back end. It can be seen that the device can perform maintenance work without the need for a new site project, thereby reducing the time cost and labor cost of web project maintenance; at the same time, it can also solve the compatibility problem in the traditional method, thereby increasing work efficiency and ensuring the effect of site connection.

[0031] Further, the web project deployment device further comprises:

[0032] a detection unit configured to detect whether a web project deployment request is received;

[0033] The acquisition unit is specifically configured to acquire a web project package when the web project deployment request is received.

[0034] Further, the acquisition unit is specifically configured to acquire a web project package imported by a user on a terminal interface layer.

[0035] Further, the web project deployment device further comprises:

[0036] The creating unit is further configured to create a network configuration file according to the access site and the static route through the terminal network layer after creating the access site for storing the web project content and creating the static route corresponding to the access site.

[0037] The starting unit is further configured to start the terminal network layer based on the network configuration file.

[0038] Further, the web project deployment device further comprises:

[0039] The output unit is further configured to output deployment completion information.

[0040] The third aspect of the embodiments of the present application provides an electronic device comprising a memory and a processor, wherein the memory is configured to store a computer program, and the processor is configured to run the computer program to enable the electronic device to perform the web project deployment method of any one of the first aspect of the embodiments of the present application.

[0041] The fourth aspect of the embodiment of the present application provides a computer readable storage medium, which stores computer program instructions, and the computer program instructions are read and run by a processor to execute the web project deployment method in any one of the first aspect of the embodiment of the present application. BRIEF DESCRIPTION OF DRAWINGS

[0042] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments of the present application. It should be understood that the following drawings only show some embodiments of the present application, and therefore should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can also be obtained without creative labor on the basis of these drawings.

[0043] Figure 1 A flowchart of a web project deployment method provided by the embodiment of the present application is shown in FIG. 1.

[0044] Figure 2 A flowchart of another web project deployment method provided by the embodiment of the present application is shown in FIG. 2.

[0045] Figure 3 A structural diagram of a web project deployment device provided by the embodiment of the present application is shown in FIG. 3.

[0046] Figure 4 A structural diagram of another web project deployment device provided by the embodiment of the present application is shown in FIG. 4.

[0047] Figure 5 A responsibility diagram of a terminal site provided by the embodiment of the present application is shown in FIG. 5.

[0048] Figure 6 A responsibility diagram of a newly created site provided by the embodiment of the present application is shown in FIG. 6.

[0049] Figure 7 An example flowchart of a web project deployment method provided by the embodiment of the present application is shown in FIG. 7. DETAILED DESCRIPTION

[0050] The technical solutions of the embodiments of the present application will be described below in combination with the drawings in the embodiments of the present application.

[0051] It should be noted that: similar reference numerals and letters represent similar items in the following drawings, and therefore, once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings. Meanwhile, in the description of the present application, the terms "first", "second", etc. are only used for distinguishing description, and cannot be understood as indicating or implying relative importance.

[0052] Embodiment 1

[0053] Referring to Figure 1 , Figure 1 A flowchart of a web project deployment method is provided in this embodiment. The web project deployment method comprises:

[0054] S101, obtaining a web project package.

[0055] S102, unpacking the web project package to obtain web project content.

[0056] S103, creating an access site for storing the web project content and creating a static route corresponding to the access site.

[0057] S104, when the terminal network layer is successfully started, storing the web project content in the access site and adding the directory of the static route before the path in the front-end HTML page; wherein the access site is a shunt site of the back-end.

[0058] Referring to Figure 5 , Figure 5 A terminal site responsibility diagram is shown. The terminal node comprises a terminal front-end (built-in static page, including JS, CSS, HTML), a terminal back-end site (processing data, business processing, processing result returned to the front-end).

[0059] In this embodiment, the main responsibility of the front-end is to interact with the terminal back-end business layer and render interface information.

[0060] In this embodiment, the main responsibility of the back-end is to process business and return the processed result to the front-end.

[0061] Referring to Figure 6 , Figure 6 A new site responsibility diagram is shown.

[0062] In this embodiment, each web project has its own independent front-end site (JS, CSS, HTML content) and back-end business processing site. The new site is a small sandbox, and each time the web project interface is run, data is returned through the terminal site (business processing code), and then the interface is rendered again. The code running will not exceed the folder (web project), ensuring that the security problem of the new site will not affect the terminal itself. Even if the new web page replaces the front-end framework, it will not cause compatibility problems.

[0063] In this embodiment, the method provides a web site access mode that can be applied to the same device. Specifically, the new site maintenance work of the project can be more efficient, so there is no need to worry about the problem that the terminal modifies the business code, causing the new site to also update the business code.

[0064] In this embodiment, the execution subject of the method can be a computer, a server or the like computing device, and no limitation is made in this embodiment.

[0065] In this embodiment, the execution subject of the method can also be a smart phone, a tablet computer or the like smart device, and no limitation is made in this embodiment.

[0066] It can be seen that, by implementing the web project deployment method described in this embodiment, the configuration file of the terminal device can be configured and modified in the form of re-writing or modifying the corresponding business code, and the compatibility problem is avoided, thereby facilitating the improvement of the deployment efficiency of the web project. Meanwhile, only JS, CSS, HTML and static resource code exist in the web project front-end site, and no backend code of the web project exists, thereby ensuring that the web project front-end site has no attack point, and the security of the web project deployment is ensured. In addition, the new site only needs to put in the front-end content (such as JS, CSS, HTML), thereby not needing to worry about whether the business processing content is available, and the process only needs to be directed to the terminal site through the backend shunting site, thereby achieving a more convenient and efficient deployment effect.

[0067] Embodiment 2

[0068] Please refer to Figure 2 , Figure 2 A flowchart of a web project deployment method is provided in this embodiment. The web project deployment method includes the following steps.

[0069] S201, detecting whether a web project deployment request is received.

[0070] S202, when the web project deployment request is received, obtaining a web project package imported by a user on a terminal interface layer.

[0071] In this embodiment, the method can independently open a window on the interface layer of the terminal, and act on the import operation (including: js, css, html, backend business processing code) of the web project.

[0072] S203, unpacking the web project package to obtain web project content.

[0073] In this embodiment, the method can perform unpacking operation on the imported project package through the terminal controller layer after receiving the request.

[0074] S204, creating an access site for storing the web project content, and creating a static route corresponding to the access site.

[0075] In this embodiment, the method can create the access site of the current web project and the static route (the directory storing the web project) after the unpacking operation is successful, and send them to the terminal network layer.

[0076] S205, creating the network configuration file according to the access site and the static route through the terminal network layer.

[0077] S206, starting the terminal network layer based on the network configuration file.

[0078] In this embodiment, the method can store the site and the static route of the current web project in the network configuration file through the terminal network layer after the terminal network layer receives the request (independent start of two sites: one is the front-end site of the web project; one is the data service processing site of the web project), and simultaneously start the network simulator through the loading of the configuration file.

[0079] S207, when the terminal network layer is successfully started, storing the web project content in the access site, and adding the directory of the static route before the front-end html page introduction path; wherein the access site is the shunt site of the back end.

[0080] In this embodiment, the method can store the current web project (including: js, css, html, independent packaging) in the directory of the current static route when the terminal control layer receives the notification of the successful start of the terminal network layer, and add the directory of the static route before the js, css introduction path in all the html pages of the front end, and store the back-end service processing code in the shunt site.

[0081] S208, outputting the deployment completion information.

[0082] As can be seen, the method can create the successful notification of the terminal interface layer when the deployment is completed.

[0083] Please refer to the Figure 7 . Based on Figure 7 As can be seen, the method is based on the terminal system as the benchmark. Specifically, the method can deploy a new web project on this benchmark to achieve the effect of adding a new access webpage. Specifically, the benchmark has a terminal interface layer, a terminal controller layer, and a terminal network layer. The example process is as follows:

[0084] ① sending a request for uploading a web project package;

[0085] ② running the web project package business code;

[0086] ③ creating a folder A (static route);

[0087] (4) According to the created folder A (static route), create network protocol and configuration;

[0088] (5) Return request;

[0089] (6) Unpack the syntax package, add the path of folder A in front of the JS and CSS reference path of all HTML pages in the front end, create file A, and put the project into folder A;

[0090] (7) Return request.

[0091] It can be seen that the method can be applied to the scenario of creating a new web page. Specifically, if a new web page configuration needs to be added to the terminal machine, the method can import the web project of the new web page through the interface layer of the terminal, then create a new access site of the web project and a static route pointing to it, put the web project (html, css, js) into the static route directory, add the directory of the static route in front of the js and css reference path in the static page html, put the back-end data business processing code into the new back-end site, and uniformly point the back-end data business processing layer interaction interface to the back-end site in the terminal machine. The back-end site in the terminal machine uniformly returns the result.

[0092] Implementing this embodiment can ensure the security of the web project interface, so that the real interface will not be transmitted on the network; can also ensure that the modification of the web project code will not affect the normal operation of the terminal machine; and can also make the web project front-end site only have JS, CSS, HTML and static resource code, without any web project back-end, so as to ensure that the web project front-end site has no attack point.

[0093] In this embodiment, the execution subject of the method can be a computer, a server or other computing device, which is not limited in this embodiment.

[0094] In this embodiment, the execution subject of the method can also be a smart phone, a tablet computer or other smart device, which is not limited in this embodiment.

[0095] It can be seen that the method for deploying the web project described in the embodiment can avoid configuring and modifying the configuration file of the terminal device by re-writing or modifying the corresponding business code, avoid compatibility problems, and thus improve the deployment efficiency of the web project. Meanwhile, the web project front-end site only has JS, CSS, HTML and static resource code, and does not have any web project back-end code, so as to ensure that the web project front-end site has no attack point, and thus the security of the web project deployment is ensured. In addition, the new site only needs to put in the front-end content (such as JS, CSS, HTML), so as not to worry about whether the business processing content is available, and thus the process only needs to be directed to the terminal site through the back-end shunting site, so as to achieve a more convenient and efficient deployment effect.

[0096] Embodiment 3

[0097] Please refer to Figure 3 , Figure 3 A structure schematic diagram of a web project deployment device provided in the embodiment. As shown in the figure, Figure 3 The web project deployment device comprises:

[0098] The acquisition unit 310 is configured to acquire a web project package.

[0099] The unpacking unit 320 is configured to unpack the web project package to obtain web project content.

[0100] The creation unit 330 is configured to create an access site for storing the web project content, and create a static route corresponding to the access site.

[0101] The deployment unit 340 is configured to store the web project content in the access site when the terminal network layer is successfully started, and add a directory of the static route before a front-end html page introduction path; wherein the access site is a back-end shunting site.

[0102] In the embodiment, the main responsibility of the front-end is to interact with the terminal back-end business layer and render interface information.

[0103] In the embodiment, the main responsibility of the back-end is to process the business, and the processed result is returned to the front-end.

[0104] In this embodiment, each web project has its own independent front-end site (JS, CSS, HTML content) and back-end business processing site, the new site is a small sandbox, and each time the web project interface is run, data needs to be returned through the terminal site (business processing code), and then the interface is rendered again, and the code running will not exceed the folder (web project), ensuring that the security problem of the new site will not affect the terminal itself, even if the new webpage replaces the front-end framework, it will not cause compatibility problems.

[0105] In this embodiment, the deployment device for the web project can refer to the description in Embodiment 1 or Embodiment 2, and will not be described again in this embodiment.

[0106] It can be seen that the deployment device for the web project described in this embodiment can avoid configuring and modifying the configuration file of the terminal device by rewriting or modifying the corresponding business code, avoid compatibility problems, thereby improving the deployment efficiency of the web project. At the same time, only JS, CSS, HTML and static resource code exist in the web project front-end site, without any back-end code of the web project, thereby ensuring that the web project front-end site has no attack point, thereby ensuring the security of the web project deployment. In addition, the new site only needs to put in front-end content (such as JS, CSS, HTML), so there is no need to worry about whether the business processing content is available, thereby making the process only need to be directed to the terminal site through the back-end shunting site, achieving a more convenient and efficient deployment effect.

[0107] Embodiment 4

[0108] Please refer to Figure 4 , Figure 4 A structure diagram of a web project deployment device provided in this embodiment. As shown in Figure 4 , the web project deployment device comprises:

[0109] The acquisition unit 310 is configured to acquire a web project package;

[0110] The unpacking unit 320 is configured to unpack the web project package to obtain web project content;

[0111] The creation unit 330 is configured to create an access site for storing the web project content, and create a static route corresponding to the access site;

[0112] The deployment unit 340 is configured to store the web project content in the access site when the terminal network layer is successfully started, and add the directory of the static route in front of the front-end html page introduction path; wherein the access site is a back-end shunting site.

[0113] As an optional implementation, the deployment apparatus of the web project further comprises:

[0114] The detection unit 350 is configured to detect whether the web project deployment request is received.

[0115] The acquisition unit 310 is specifically configured to acquire the web project package when the web project deployment request is received.

[0116] As an optional implementation, the acquisition unit 310 is specifically configured to acquire the web project package imported by the user on the terminal interface layer.

[0117] As an optional implementation, the deployment apparatus of the web project further comprises:

[0118] The creation unit 330 is further configured to create a network configuration file according to the access site and the static route through the terminal network layer after the access site for storing the web project content and the static route corresponding to the access site are created.

[0119] The starting unit 360 is further configured to start the terminal network layer based on the network configuration file.

[0120] As an optional implementation, the deployment apparatus of the web project further comprises:

[0121] The output unit 370 is further configured to output the deployment completion information.

[0122] In this embodiment, the deployment apparatus of the web project can be explained and described with reference to the description in Embodiment 1 or Embodiment 2, and the description will not be repeated herein.

[0123] It can be seen that the deployment apparatus of the web project described in this embodiment can avoid configuring and modifying the configuration file of the terminal device in the form of re-writing or modifying the corresponding business code, and avoid compatibility problems, thereby facilitating to improve the deployment efficiency of the web project. Meanwhile, the web project front-end site only has JS, CSS, HTML and static resource code, and does not have any web project back-end code, thereby ensuring that the web project front-end site has no attack point, and further ensuring the security of the web project deployment. In addition, the new site only needs to put in the front-end content (such as JS, CSS, HTML), thereby not needing to worry about whether the business processing content is available, and further making the process only need to be directed to the terminal site through the back-end shunting site, thereby achieving a more convenient and efficient deployment effect.

[0124] The embodiment of the present application provides an electronic device, comprising a memory and a processor, the memory is used for storing a computer program, and the processor runs the computer program to make the electronic device execute the deployment method of the web project in the embodiment 1 or the embodiment 2 of the present application.

[0125] The embodiment of the present application provides a computer readable storage medium, which stores computer program instructions, when the computer program instructions are read and run by a processor, the deployment method of the web project in the embodiment 1 or the embodiment 2 of the present application is executed.

[0126] In several embodiments provided in the present application, it should be understood that the disclosed apparatus and method can also be implemented by other manners. The apparatus embodiment described above is only schematic, for example, the flow chart and block diagram in the drawings show the possible implementation architecture, function and operation of the apparatus, method and computer program product according to the embodiments of the present application. In this regard, each block in the flow chart or block diagram can represent a module, program segment or part of code, which contains one or more executable instructions for implementing the specified logical function. It should also be noted that, in some alternative implementation manners, the functions noted in the block can also occur in different order from that noted in the drawings. For example, two continuous blocks can actually be executed substantially in parallel, and sometimes they can be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flow chart, and the combination of blocks in the block diagram and / or flow chart, can be implemented by a dedicated hardware-based system for executing the specified function or action, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0127] In addition, each functional module in the various embodiments of the present application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0128] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts of the prior art that make contributions or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

[0129] The above merely provides an example of the present application and is not intended to limit the protection scope of the present application. For those skilled in the art, the present application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that similar reference numbers and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings.

[0130] The above merely provides an example of the present application and is not intended to limit the protection scope of the present application. For those skilled in the art, the present application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that similar reference numbers and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings.

[0131] It should be noted that, in the present document, the relationship terms such as first and second are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between the entities or operations. Moreover, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the processes, methods, articles or devices including a series of elements not only include those elements, but also include other elements not explicitly listed or inherent to such processes, methods, articles or devices. Without more limitations, the element defined by the statement "including a" does not exclude the presence of another identical element in the process, method, article or device including the element.

Claims

1. A method of deploying a web project, characterized by, The method comprises: obtaining a web project package; unpacking the web project package to obtain web project content; creating an access site for storing the web project content and creating a static route corresponding to the access site; the access site comprises a web project front-end site and a web project data service processing site; storing the web project content in the access site and adding a directory of the static route in front of a front-end html page import path when a terminal network layer is successfully started; wherein the access site is a shunt site of a back end.

2. The method of claim 1, wherein, The method further comprises: detecting whether a web project deployment request is received; when the web project deployment request is received, performing the step of obtaining the web project package.

3. The method of claim 1, wherein, The step of obtaining the web project package comprises: obtaining a web project package imported by a user in a terminal interface layer.

4. The method of claim 1, wherein, After the step of creating the access site for storing the web project content and creating the static route corresponding to the access site, the method further comprises: creating a network configuration file according to the access site and the static route through the terminal network layer; starting the terminal network layer based on the network configuration file.

5. The method of claim 1, wherein, After the step of storing the web project content in the access site and adding the directory of the static route in front of the front-end html page import path, the method further comprises: outputting deployment completion information.

6. An apparatus for deploying a web project, characterized by: The web project deployment apparatus comprises: an obtaining unit configured to obtain a web project package; an unpacking unit configured to unpack the web project package to obtain web project content; a creating unit configured to create an access site for storing the web project content and create a static route corresponding to the access site; the access site comprises a web project front-end site and a web project data service processing site; a deployment unit configured to store the web project content in the access site and add a directory of the static route in front of a front-end html page import path when a terminal network layer is successfully started; wherein the access site is a shunt site of a back end.

7. The apparatus for deploying a web project according to claim 6, wherein, The web project deployment apparatus further comprises: a detecting unit configured to detect whether a web project deployment request is received; the obtaining unit is specifically configured to obtain a web project package when the web project deployment request is received.

8. The apparatus for deploying a web project according to claim 6, wherein, The obtaining unit is specifically configured to obtain a web project package imported by a user in a terminal interface layer.

9. An electronic device, comprising: The electronic device comprises a memory and a processor, the memory is used to store a computer program, and the processor runs the computer program to make the electronic device execute the web project deployment method in any one of claims 1 to 5.

10. A readable storage medium, characterized by, The readable storage medium stores computer program instructions, and the computer program instructions are read and run by a processor to execute the web project deployment method in any one of claims 1 to 5.

Images