CN110825426A - Webpage development method, preview method, release method and development system - Google Patents
Webpage development method, preview method, release method and development system Download PDFInfo
- Publication number
- CN110825426A CN110825426A CN201810904005.5A CN201810904005A CN110825426A CN 110825426 A CN110825426 A CN 110825426A CN 201810904005 A CN201810904005 A CN 201810904005A CN 110825426 A CN110825426 A CN 110825426A
- Authority
- CN
- China
- Prior art keywords
- source code
- code file
- server
- packaging
- webpage
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/73—Program documentation
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Library & Information Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Information Transfer Between Computers (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses webpage development system includes: editing a client and a packaging server; the editing client is used for providing an editor for editing the webpage source code file for an editing user, obtaining the webpage source code file edited by the editing user through the editor, and providing a packaging request aiming at the webpage source code file to a packaging server; the packaging request comprises the webpage source code file; the packaging server is used for obtaining the packaging request aiming at the webpage source code file, packaging the webpage source code file according to the packaging request and the environment configuration which is set on the packaging server and aims at the packaging request aiming at the webpage source code file, generating an object code, and storing the object code in a first storage system. By adopting the system, the requirement that the front-end developer automatically publishes the webpage to the server is met.
Description
Technical Field
The application relates to the field of webpage development, in particular to a webpage development system. The application also relates to a webpage development method. The application also relates to a webpage previewing method and a webpage publishing method.
Background
When cloud computing is started, the concept of severless (without a server) gradually deepens into each development platform, more and more front-end developers deploy service API codes to a Faas-like platform, but no mature scheme is provided for web page development to achieve Serverless after compiling, packaging and releasing to a server. Even today when engineering is so sophisticated, front-end developers still need to expend a lot of effort on the compilation and packaging tools, while also needing to be concerned about how web pages are published on the server. Increasingly complex business requirements and faster iteration speeds make it overwhelming for countless front-end developers.
Thus, front-end developers have a need to automatically publish web pages to servers.
Disclosure of Invention
The application provides a webpage development system to meet the requirement that a front-end developer automatically releases a webpage to a server.
The application provides a web page development system, including: editing a client and a packaging server;
the editing client is used for providing an editor for editing the webpage source code file for an editing user, obtaining the webpage source code file edited by the editing user through the editor, and providing a packaging request aiming at the webpage source code file to a packaging server;
the packaging server is used for obtaining the packaging request aiming at the webpage source code file, packaging the webpage source code file according to the packaging request and the environment configuration which is set on the packaging server and aims at the packaging request aiming at the webpage source code file, generating an object code, and storing the object code in a first storage system.
Optionally, the packaging request includes: issue requests and test requests.
Optionally, the system further comprises a control server;
the editing client is also used for sending a storage request aiming at the webpage source code file to a control server; the storage request comprises the webpage source code file;
the control server is used for receiving a saving request aiming at the webpage source code file sent by the editing client, and storing the webpage source code file contained in the saving request to a second storage system for storing the webpage source code file.
Alternatively to this, the first and second parts may,
the editing client is also used for sending a publishing request aiming at the webpage source code file to the control server;
the control server is further configured to obtain the publishing request provided by the editing client, and send the publishing request to the packaging server;
the packaging server is specifically configured to obtain the publishing request provided by the control server, obtain the web page source code file from the second storage system according to the publishing request and an environment configuration set on the packaging server for the web page source code file publishing request, package the web page source code file, generate a formal code for formal publishing, and store the formal code for formal publishing in the first storage system.
Optionally, the packaging server is specifically configured to monitor the web page source code file in the second storage system, generate a test code for testing a web page according to the web page source code file when it is monitored that the web page source code file is stored in the second storage system, and store the test code for testing the web page in the first storage system for storing the packaging file.
Optionally, the method further includes: a product server and a product client;
the product server is used for acquiring the formal codes for formal release from the first storage system, receiving a request for acquiring a page generated after the formal codes for formal release are operated and sent by a product client, and providing the generated page for the product client;
and the product client is used for sending a request for obtaining the page generated after the running of the formal code for formal release to a product server, and displaying the page generated after the running of the formal code for formal release to a product user through a production page.
Optionally, the product client is further configured to provide a configuration interface for configuring the middleware to a product user, obtain a configuration result of the product user for the middleware through the configuration interface, and send the configuration result for the middleware to the product server;
the product server is further configured to obtain the configuration result for the middleware provided by the product client, and perform corresponding processing according to the configuration result.
Optionally, the system further includes: a preview server and a preview client;
the preview server is used for obtaining the test codes for testing the web pages stored in the first storage system, running the test codes for testing the web pages, receiving a request for obtaining a running result of the test codes for testing the web pages sent by a preview client, and providing the running result to the preview client;
the preview client is used for sending a request for obtaining the running result of the test code for the test webpage to the preview server, and displaying the running result of the test code for the test webpage to a preview user through the preview page.
Optionally, the preview server is further configured to obtain the web page source code file from the first storage system, and provide a source code in the web page source code file to the preview client;
the preview client is also used for displaying the source code to a preview user, acquiring debugging requirement information of the preview user on the source code, and sending the debugging requirement information to the preview server;
and the preview server is also used for debugging the source code according to the debugging requirement information to obtain a debugging result.
Optionally, the preview client is further configured to provide a configuration interface for configuring the middleware to a preview user, obtain a configuration result of the preview user for the middleware through the configuration interface, and send the configuration result for the middleware to the preview server;
the preview server is further configured to obtain the configuration result for the middleware provided by the preview client, and perform corresponding processing according to the configuration result.
The application also provides a webpage development method, which comprises the following steps:
obtaining a packaging request aiming at a first webpage source code file; the packaging request comprises the first webpage source code file;
packaging the first webpage source code file according to the obtained packaging request and environment configuration set on a packaging server aiming at the packaging request of the first webpage source code file to generate a target code;
storing the object code in a first storage system.
Optionally, the packaging request includes: issue requests and test requests.
Optionally, the method further includes:
monitoring whether a second webpage source code file is stored;
when it is monitored that a second webpage source code file is stored, generating a test code for testing a webpage according to the second webpage source code file and a development environment configuration set for the second webpage source code file, and storing the test code for testing the webpage into the first storage system.
The application also provides a webpage previewing method, which comprises the following steps:
obtaining test code for testing a webpage aiming at a first webpage source code file from a first storage system;
running the test code for testing the webpage;
and providing the running result of the test code for testing the webpage to a preview client.
The present application further provides a method for publishing a web page, including:
obtaining formal codes for formal publishing aiming at a first webpage source code file from a first storage system;
and providing the page generated after the formal codes for formal release are operated to a product client.
Compared with the prior art, the method has the following advantages:
according to the webpage development system, the packaging server obtains the packaging request aiming at the webpage source code file, the webpage source code file is packaged according to the packaging request and the environment configuration which is set on the packaging server and aims at the packaging request aiming at the webpage source code file, the target code is generated, and the target code is stored in the first storage system, so that the automatic packaging of the webpage source code file on the server is realized, and the requirement that a front-end developer automatically releases a webpage to the server is met.
Drawings
Fig. 1 is a schematic diagram of a web page development system according to a first embodiment of the present application.
Fig. 2 is a flowchart of a web page development method according to a second embodiment of the present application.
Fig. 3 is a flowchart of a web page preview method according to a third embodiment of the present application.
Fig. 4 is a flowchart of a method for publishing a web page according to a fourth embodiment of the present application.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein, but rather construed as limited to the embodiments set forth herein.
The first embodiment of the application provides a webpage development system. Referring to fig. 1, a schematic diagram of a web page development system provided according to a first embodiment of the present application is shown. This is explained in detail below with reference to fig. 1.
The web page development system comprises: an editing client 101 and a packaging server 102.
The editing client 101 is configured to provide an editor for editing a web page source code file to an editing user, obtain the web page source code file edited by the editing user through the editor, and provide a packaging request for the web page source code file to a packaging server; the packaging request comprises the webpage source code file.
The web pages include dynamic web pages and static web pages.
The packed requests include issue requests and test requests. The packaging request can be a packaging request provided by an editing user for a webpage source code file, or a packaging request provided by an editing client to a packaging server at regular time.
The system further comprises a control server 103.
Providing a packaging request for the webpage source code file to a packaging server, wherein the packaging request comprises two conditions: one is to provide the packaging request to the packaging server directly through the editing client, and the other is to provide the packaging request to the control server through the editing client, and then the packaging request is provided to the packaging server through the control server.
The editing client 101 is further configured to send a storage request for the web page source code file to a control server; the storage request comprises the webpage source code file; the storage request comprises the webpage source code file.
The editing client can be an online editor which provides editing user with webpage source code files, the editing user can select the webpage source code files to be written in the online editor, and then the webpage source code files are written, wherein the webpage source code files comprise js, ccs and other files. For example, the source code file of the web page is 1.js, and the editing user can edit the 1.js file in an online editor.
Specifically, the saving request for the webpage source code file is sent to the control server, a saving button can be set on the online editor, and the editing client can obtain the saving request for the webpage source code file by obtaining the click operation of the editing user on the saving button and send the saving request to the control server. For example, after the editing user edits the 1.js file in the online editor, the user may click a save button to send a save request to the control server, where the save request includes information such as the source code content and the file path of the 1.js file.
In specific implementation, when the packaging request is a publishing request provided by an editing user for a web page source code file, the editing client needs to obtain the publishing request provided by the editing user for the web page source code file, which may include the following two cases: one situation is that an editing user directly issues after editing a webpage source code file, buttons for representing issuing requests can be arranged on an online editor, and an editing client can obtain the issuing requests provided by the editing user for the webpage source code file by obtaining the clicking operation of the editing user on the issuing request buttons; the other situation is that the editing user publishes the webpage source code file after testing the webpage source code file, a right mouse button is clicked after the webpage source code file is selected, a publishing menu item is displayed, and the editing client can obtain a publishing request provided by the editing user and aiming at the webpage source code file by obtaining the clicking operation of the editing user on the publishing menu item. When an editing user needs to publish the edited webpage source code file, a publishing request button or a publishing menu item can be clicked on the online editor, and the publishing request is sent to the control server. For example, when the editing user wants to deploy a 1.js file to the server, the publishing menu item may be clicked to send a publishing request to the control server. The release request may include information such as content of the web page source code file, a path of the web page source code file, and the like.
The packaging server 102 is configured to obtain the packaging request for the web page source code file, package the web page source code file according to the packaging request and an environment configuration set on the packaging server for the packaging request for the web page source code file, generate an object code, and store the object code in a first storage system.
The object code, comprising: test code for testing the web page and formal code for formal release.
The packaging server provides a set of mature packaging environment configuration, the packaging environment configuration comprises development environment configuration (aiming at a test request) and production environment configuration (aiming at a release request), and supports mainstream format file packaging, after the packaging server obtains the packaging request directly or indirectly (forwarded by a control server) provided by an editing client, the packaging server packages the webpage source code file according to the packaging request and the environment configuration which is set on the packaging server and aims at the packaging request of the webpage source code file, generates an object code, and stores the object code into the first storage system. By configuring the production environment on the packaging server, the problem that the editing user needs to perform complicated configuration in the prior art is solved, so that a front-end developer (editing user) does not need to pay attention to the configuration problem of a project when developing a webpage, and only needs to pay attention to a service.
As an embodiment, when the packaging request is an issue request, the packaging server 102 may obtain the issue request provided by the control server 103, obtain the web page source code file from the second storage system according to the issue request and an environment configuration (production environment configuration) set on the packaging server for the web page source code file issue request, package the web page source code file, generate a formal code for formal issue, and store the formal code for formal issue in the first storage system.
As an embodiment, when the packaging request is a test request, the packaging server 102 may obtain the test request provided by the control server 103, obtain the web page source code file from the second storage system according to the test request and an environment configuration (development environment configuration) set on the packaging server for the web page source code file test request, package the web page source code file, generate a test code for testing a web page, and store the test code for testing a web page in the first storage system.
The packaging server 102 is further configured to monitor the web page source code file in the second storage system, generate a test code for testing a web page according to the web page source code file when it is monitored that the web page source code file is stored in the second storage system, and store the test code for testing the web page in the first storage system for storing the packaging file.
The packaging server can package according to the change of the monitored webpage source code file besides packaging according to the test request. When the packaging server monitors that the webpage source code file is stored in the second storage system, the webpage source code file can be considered to be changed, the webpage source code file is packaged according to the development environment configuration set on the packaging server and aiming at the webpage source code file, a test code for testing the webpage is generated, and the test code for testing the webpage is stored in the first storage system for storing the packaging file. By configuring the development environment on the packaging memory, the automatic packaging of the edition of the editing user when the edition of the webpage source code file is stored after the edition of the webpage source code file is realized, and the problem that the complicated configuration is required when the edition user packs the webpage source code file and generates the test code for testing the webpage in the prior art is solved, so that a front-end developer (the editing user) does not need to concern about the configuration of the project when developing the webpage, and only needs to concern about the service.
The control server 103 is configured to receive a saving request for the web page source code file sent by the editing client, and store the web page source code file included in the saving request to a second storage system for storing the web page source code file.
The control server 103 is further configured to obtain the publishing request provided by the editing client, and send the publishing request to the packaging server.
The second storage system may be a distributed file storage system.
After receiving a saving request aiming at the webpage source code file sent by the editing client, the control server stores the webpage source code file contained in the saving request to a second storage system for storing the webpage source code file according to the webpage source code file content and the file path contained in the saving request, the webpage source code file is not stored locally any more, and the control server directly stores the webpage source code file to a storage address on the distributed file storage system. For example, after the editing user sends a save request for the 1.js file to the control server, the control server updates the content of the 1.js file in the save request to the storage address corresponding to the file path.
The web page development system also includes a product server 104 and a product client 105.
The product server 104 is configured to obtain the formal code for formal release from the first storage system, receive a request sent by a product client to obtain a page generated after the formal code for formal release is executed, and provide the generated page to the product client.
The product server can obtain the formal codes for formal release sent by the first storage system, receive a request for obtaining the page generated after the formal codes for formal release are run and sent by the product client, and provide the generated page for the product client to display.
The product client 105 is configured to send a request for obtaining a page generated after the running of the formal code for formal issue to a product server, and display the page generated after the running of the formal code for formal issue to a product user through a production page.
The product client 105 is further configured to provide a configuration interface for configuring middleware to a product user, obtain a configuration result of the product user for the middleware through the configuration interface, and send the configuration result for the middleware to the product server 104; the product server is further configured to obtain the configuration result for the middleware provided by the product client, and perform corresponding processing according to the configuration result of the middleware.
The product user refers to a user of a product client.
The middleware refers to simple back-end processing of a request for specifying a url template, such as login authentication jump or proxy pointing.
The product server supports the product user to customize the middleware configuration has the advantages that the product user can simply interfere with the processing logic of the back-end request, and if the customized middleware configuration is not provided, the interaction mode of the product client and the product server is limited (for example, login cannot be verified, and the request cannot be proxied).
The web page development system may further include: a preview server 106 and a preview client 107.
The preview server 106 is configured to obtain the test code for testing the web page stored in the first storage system, run the test code for testing the web page, receive a request sent by the preview client to obtain a running result of the test code for testing the web page, and provide the running result to the preview client.
The preview client 107 is configured to send a request for obtaining an operation result of the test code for the test web page to a preview server, and show the operation result of the test code for the test web page to a preview user through a preview page.
The preview server 106 is further configured to obtain the web page source code file from the first storage system, and provide a source code in the web page source code file to the preview client;
the preview client 107 is further configured to display the source code to a preview user, obtain debugging requirement information of the preview user for the source code, and send the debugging requirement information to the preview server;
the preview server 106 is further configured to debug the source code according to the debugging requirement information, so as to obtain a debugging result.
The preview client 107 is further configured to provide a configuration interface for configuring the middleware to a preview user, obtain a configuration result of the preview user for the middleware through the configuration interface, and send the configuration result for the middleware to the preview server;
the preview server 106 is further configured to obtain the configuration result for the middleware provided by the preview client, and perform corresponding processing according to the configuration result.
The preview user refers to a user who previews the client. It should be noted that the editing user, the product user, and the preview user may be the same user or different users.
The middleware refers to simple back-end processing of a request for specifying a url template, such as login authentication jump or proxy pointing.
The advantage of the product server supporting the product user-defined middleware configuration is that the preview user can simply interfere with the processing logic of the back-end request, and if the user-defined middleware configuration is not provided, the interaction mode between the preview client and the preview server is greatly limited (for example, login cannot be verified, and the request cannot be proxied).
Now, an implementation of the web page development system according to the first embodiment of the present application is described in detail. The first embodiment of the application solves the problem that a product user needs to perform complicated configuration in the prior art by configuring the production environment on the packaging server, so that a front-end developer does not need to concern about the configuration problem of engineering when developing a webpage, and only needs to concern about a service; by configuring the development environment on the packaging server, the editing of an editing user is automatically packaged when the editing user edits the webpage source code file and then saves the webpage source code file, the problem that in the prior art, the editing user needs to perform complicated configuration when packaging the webpage source code file and generating a test code for testing a webpage is solved, and a front-end developer (the editing user) does not need to care about the configuration of a project when developing the webpage and only needs to pay attention to a service.
The second embodiment of the application provides a webpage development method. The web page development method is deployed on a packaging server of the web page development system provided by the first embodiment, and is described in detail below with reference to fig. 2.
As shown in fig. 2, in step S201, a packaging request for a first web page source code file is obtained.
The packaging request includes: issue requests and test requests. The packaging request comprises the first webpage source code file.
The packaging request for the first webpage source code file can be sent to a packaging server through a control server. For example, when the editing user needs to publish the first webpage to the server, the editing user sends a publishing request of the first webpage source code file to the control server, and the control server receives the publishing request and then sends the publishing request to the packaging server. The first web page source code file in the request for publication may be a tested state web page source code file. The publishing request may include information such as a file path of the first web page source code file, content of the web page source code file, and the like.
The packaging request for the first webpage source code file can also be sent to a packaging server through an editing client.
As shown in fig. 2, in step S202, the first webpage source code file is packaged according to the obtained packaging request and the environment configuration set on the packaging server for the packaging request of the first webpage source code file, so as to generate an object code.
The object code, comprising: test code for testing the web page and formal code for formal release.
According to the method, the first webpage source code file is packaged according to the obtained packaging request and the environment configuration which is set on the packaging server and aims at the packaging request of the first webpage source code file, so that the first webpage source code file is automatically packaged, and the problem that a front-end developer needs to perform complicated configuration when deploying the webpage source code file to a production server and generating a test code for testing the webpage is solved.
As shown in fig. 2, in step S203, the object code is stored in the first storage system.
In the step, the object code is stored in a first storage system, and preconditions are provided for displaying the webpage corresponding to the first webpage source code file to a production client or a preview client.
The method further comprises:
monitoring whether a second webpage source code file is stored;
when it is monitored that a second webpage source code file is stored, generating a test code for testing a webpage according to the second webpage source code file and development environment configuration set for the second webpage source code file, and storing the test code for testing the webpage into the first storage system.
By configuring the development environment on the packaging server, the editing of an editing user is realized, the webpage source code file is automatically packaged after being edited, the problem that in the prior art, the editing user needs to carry out complicated configuration when packaging the webpage source code file and generating a test code for testing a webpage is solved, and a front-end developer (the editing user) does not need to care about the configuration of a project when developing the webpage, and only needs to pay attention to a service.
A third embodiment of the present application provides a web page preview method, where the web page preview method is deployed on a preview server, and is described in detail below with reference to fig. 3.
As shown in fig. 3, in step S301, test code for testing a web page with respect to a web page source code file is obtained from a second storage system.
As shown in fig. 3, in step S302, the test code for testing the web page is executed.
As shown in fig. 3, in step S303, the running result for the test code for testing the web page is provided to the preview client.
A fourth embodiment of the present application provides a web page publishing method, where the web page publishing method is deployed on a production server, and is described in detail below with reference to fig. 4.
As shown in fig. 4, in step S401, obtaining formal code for formal publishing for a web page source code file from a first storage system;
as shown in fig. 4, in step S402, the page generated after the formal code for formal release is executed is provided to the product client.
Although the present invention has been described with reference to the preferred embodiments, it is not intended to be limited thereto, and variations and modifications may be made by those skilled in the art without departing from the spirit and scope of the present invention.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Claims (15)
1. A web page development system, comprising: editing a client and a packaging server;
the editing client is used for providing an editor for editing the webpage source code file for an editing user, obtaining the webpage source code file edited by the editing user through the editor, and providing a packaging request aiming at the webpage source code file to a packaging server; the packaging request comprises the webpage source code file;
the packaging server is used for obtaining the packaging request aiming at the webpage source code file, packaging the webpage source code file according to the packaging request and the environment configuration which is set on the packaging server and aims at the packaging request aiming at the webpage source code file, generating an object code, and storing the object code in a first storage system.
2. The system of claim 1, the packaging request comprising: issue requests and test requests.
3. The system of claim 2, further comprising a control server;
the editing client is also used for sending a storage request aiming at the webpage source code file to a control server; the storage request comprises the webpage source code file;
the control server is used for receiving a saving request aiming at the webpage source code file sent by the editing client, and storing the webpage source code file contained in the saving request to a second storage system for storing the webpage source code file.
4. The system of claim 3,
the editing client is also used for sending a publishing request aiming at the webpage source code file to the control server;
the control server is further configured to obtain the publishing request provided by the editing client, and send the publishing request to the packaging server;
the packaging server is specifically configured to obtain the publishing request provided by the control server, obtain the web page source code file from the second storage system according to the publishing request and an environment configuration set on the packaging server for the web page source code file publishing request, package the web page source code file, generate a formal code for formal publishing, and store the formal code for formal publishing in the first storage system.
5. The system of claim 3, wherein the packaging server is further configured to monitor the web page source code file in the second storage system, generate a test code for testing the web page according to the web page source code file when it is monitored that the web page source code file is stored in the second storage system, and store the test code for testing the web page in the first storage system for storing the packaging file.
6. The system of claim 4, further comprising: a product server and a product client;
the product server is used for acquiring the formal codes for formal release from the first storage system, receiving a request for acquiring a page generated after the formal codes for formal release are operated and sent by a product client, and providing the generated page for the product client;
and the product client is used for sending a request for obtaining the page generated after the running of the formal code for formal release to a product server, and displaying the page generated after the running of the formal code for formal release to a product user through a production page.
7. The system of claim 6, wherein the product client is further configured to provide a configuration interface for configuring middleware to a product user, obtain a configuration result for the middleware by the product user through the configuration interface, and send the configuration result for the middleware to the product server;
the product server is further configured to obtain the configuration result for the middleware provided by the product client, and perform corresponding processing according to the configuration result.
8. The system of claim 5, further comprising: a preview server and a preview client;
the preview server is used for obtaining the test codes for testing the web pages stored in the first storage system, running the test codes for testing the web pages, receiving a request for obtaining a running result of the test codes for testing the web pages sent by a preview client, and providing the running result to the preview client;
the preview client is used for sending a request for obtaining the running result of the test code for the test webpage to the preview server, and displaying the running result of the test code for the test webpage to a preview user through the preview page.
9. The system of claim 8, wherein the preview server is further configured to obtain the web page source code file from the first storage system, and provide source code in the web page source code file to the preview client;
the preview client is also used for displaying the source code to a preview user, acquiring debugging requirement information of the preview user on the source code, and sending the debugging requirement information to the preview server;
and the preview server is also used for debugging the source code according to the debugging requirement information to obtain a debugging result.
10. The system of claim 8, wherein the preview client is further configured to provide a configuration interface for configuring the middleware to a preview user, obtain a configuration result of the preview user for the middleware through the configuration interface, and send the configuration result for the middleware to the preview server;
the preview server is further configured to obtain the configuration result for the middleware provided by the preview client, and perform corresponding processing according to the configuration result.
11. A method for web page development, comprising:
obtaining a packaging request aiming at a first webpage source code file; the packaging request comprises the first webpage source code file;
packaging the first webpage source code file according to the obtained packaging request and environment configuration set on a packaging server aiming at the packaging request of the first webpage source code file to generate a target code;
storing the object code in a first storage system.
12. The method of claim 11, wherein the packaging request comprises: issue requests and test requests.
13. The method of claim 11, further comprising:
monitoring whether a second webpage source code file is stored;
when it is monitored that a second webpage source code file is stored, generating a test code for testing a webpage according to the second webpage source code file and a development environment configuration set for the second webpage source code file, and storing the test code for testing the webpage into the first storage system.
14. A method for previewing a web page, comprising:
obtaining test code for testing a webpage aiming at a webpage source code file from a first storage system;
running the test code for testing the webpage;
and providing the running result of the test code for testing the webpage to a preview client.
15. A method for publishing a web page, comprising:
obtaining formal codes for formal publishing aiming at a webpage source code file from a first storage system;
and providing the page generated after the formal codes for formal release are operated to a product client.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810904005.5A CN110825426B (en) | 2018-08-09 | 2018-08-09 | Webpage development method, preview method, publishing method and development system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810904005.5A CN110825426B (en) | 2018-08-09 | 2018-08-09 | Webpage development method, preview method, publishing method and development system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110825426A true CN110825426A (en) | 2020-02-21 |
| CN110825426B CN110825426B (en) | 2023-06-23 |
Family
ID=69540946
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810904005.5A Active CN110825426B (en) | 2018-08-09 | 2018-08-09 | Webpage development method, preview method, publishing method and development system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110825426B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111949256A (en) * | 2020-08-12 | 2020-11-17 | 广州华多网络科技有限公司 | Webpage real-time preview editing method, device, equipment and storage medium |
| CN112035596A (en) * | 2020-08-31 | 2020-12-04 | 京东数字科技控股股份有限公司 | Text submission method, device, equipment and storage medium |
| CN112527378A (en) * | 2020-12-01 | 2021-03-19 | 国电南瑞科技股份有限公司 | Online updating method and system for power grid mobile application software page |
| CN112596714A (en) * | 2020-12-10 | 2021-04-02 | 车巴达（苏州）网络科技有限公司 | Webpage development method, device, terminal, server and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050240869A1 (en) * | 2004-04-23 | 2005-10-27 | Kalev Leetaru | Method and system for editable web browsing |
| US20050240864A1 (en) * | 2004-04-23 | 2005-10-27 | Kalev Leetaru | Method and system for retrieving information using an authentication web page |
| CN105808304A (en) * | 2016-03-29 | 2016-07-27 | 北京小米移动软件有限公司 | Code deployment method, device and system |
| CN107632826A (en) * | 2016-07-14 | 2018-01-26 | 腾讯科技（深圳）有限公司 | The Compilation Method and client of a kind of source code |
-
2018
- 2018-08-09 CN CN201810904005.5A patent/CN110825426B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050240869A1 (en) * | 2004-04-23 | 2005-10-27 | Kalev Leetaru | Method and system for editable web browsing |
| US20050240864A1 (en) * | 2004-04-23 | 2005-10-27 | Kalev Leetaru | Method and system for retrieving information using an authentication web page |
| CN105808304A (en) * | 2016-03-29 | 2016-07-27 | 北京小米移动软件有限公司 | Code deployment method, device and system |
| CN107632826A (en) * | 2016-07-14 | 2018-01-26 | 腾讯科技（深圳）有限公司 | The Compilation Method and client of a kind of source code |
Non-Patent Citations (1)
| Title |
|---|
| 李君等: ""基于组件的Web文本编辑器开发及其应用"" * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111949256A (en) * | 2020-08-12 | 2020-11-17 | 广州华多网络科技有限公司 | Webpage real-time preview editing method, device, equipment and storage medium |
| CN112035596A (en) * | 2020-08-31 | 2020-12-04 | 京东数字科技控股股份有限公司 | Text submission method, device, equipment and storage medium |
| CN112527378A (en) * | 2020-12-01 | 2021-03-19 | 国电南瑞科技股份有限公司 | Online updating method and system for power grid mobile application software page |
| CN112596714A (en) * | 2020-12-10 | 2021-04-02 | 车巴达（苏州）网络科技有限公司 | Webpage development method, device, terminal, server and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110825426B (en) | 2023-06-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110825426B (en) | Webpage development method, preview method, publishing method and development system | |
| US10185626B2 (en) | Automatic application error detection and rollback | |
| CN106559438B (en) | Program uploading method and device based on target network platform | |
| JP2021072089A (en) | Webpage rendering method, device, electronic equipment, storage medium, and program | |
| JP4988746B2 (en) | Method, system, and computer program for providing a portlet viewer for viewing drag and drop content in a portal environment (portlet viewer for viewing drag and drop content in a portal environment) Offer) | |
| US9384005B2 (en) | Systems and methods for dynamic configuration of client-side development environments through use of application servers | |
| US10209968B2 (en) | Application compiling | |
| US9218100B2 (en) | Method and system for partitioning asset management plugins | |
| US20100125826A1 (en) | Workflow engine for execution of web mashups | |
| US9588872B2 (en) | Discovery of code paths | |
| TW201814545A (en) | Multi-service integration method and apparatus, intelligent terminal, server and operating system | |
| CN106294113B (en) | creation method and device based on programmable test service | |
| US9645814B1 (en) | Generating and publishing applications for multiple platforms | |
| US20170242665A1 (en) | Generation of hybrid enterprise mobile applications in cloud environment | |
| CN110554874A (en) | Method and device for reusing webpage components of SaaS platform | |
| US9158520B2 (en) | Development of platform independent applications | |
| US10223078B2 (en) | Application-type independent dynamic plug-in evaluation tool | |
| CN107015903B (en) | Interface test program generation method and device and electronic equipment | |
| US20140282420A1 (en) | Test automation booster | |
| US9141363B2 (en) | Application construction for execution on diverse computing infrastructures | |
| US20150317405A1 (en) | Web Page Variation | |
| US9436445B2 (en) | Drag-and-drop functionality for scalable vector graphics | |
| US8959426B1 (en) | Loading customer-supplied network page generation code | |
| CN108255708A (en) | Method, apparatus, storage medium and the equipment of production file are accessed in test environment | |
| US20160248890A1 (en) | Hybrid native networked applications |
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 |