CN115562718B - Method and device for constructing pure front-end static resource content publishing platform - Google Patents
Method and device for constructing pure front-end static resource content publishing platform Download PDFInfo
- Publication number
- CN115562718B CN115562718B CN202211470122.8A CN202211470122A CN115562718B CN 115562718 B CN115562718 B CN 115562718B CN 202211470122 A CN202211470122 A CN 202211470122A CN 115562718 B CN115562718 B CN 115562718B
- Authority
- CN
- China
- Prior art keywords
- modification data
- platform
- version
- data
- deployment
- 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
- 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
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Data Mining & Analysis (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method and a device for constructing a pure front-end static resource content publishing platform, wherein the method is applied to a content management platform of a CMS (content management system), and comprises the following steps: receiving and storing version modification data sent by a content maintainer; triggering a version modification data pulling function of the code warehouse so that the code warehouse pulls the version modification data by using a GIT tool and stores the version modification data; triggering a deployment platform to carry out environment deployment, and constructing a content display platform according to the version modification data; the content display platform is a pure front-end static resource content publishing platform. Therefore, the SEO effect can be indirectly improved, and the influence on data acquisition when the network is unstable is avoided.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a method and a device for constructing a pure front-end static resource content publishing platform.
Background
The traditional CMS system comprises a content display platform and a content management background, wherein the content display platform is responsible for content display and is used by users. And the content management background is responsible for data maintenance. Specifically, the content management background has its front and back ends for content management personnel to maintain the content and support version control. When a user accesses the display platform, after the corresponding content data is acquired from the content management background through a network request, the display platform performs page rendering according to the data content so as to be viewed by the user. When the content needs to be changed, the change is edited in the content management background. After the approval is passed, the content display platform does not need to be published and online, and the content is the latest content after being revisited.
However, the above technical solution has the following disadvantages: the page rendering can be performed only after the corresponding content data is acquired from the content management background through a network request, the influence of the network is large, the speed is unstable, the display platform is a post-rendering platform, blank processing is required before the data is not available, and the SEO (Search Engine Optimization) effect can be influenced.
Disclosure of Invention
The embodiment of the invention provides a method and a device for constructing a pure front-end static resource content publishing platform, which are used for solving the technical problems that in a CMS system, page rendering can be performed only after corresponding content data are acquired from a content management background through a network request, so that the influence of the network is large, the speed is unstable, and the SEO effect is influenced.
The following were used:
in a first aspect, an embodiment of the present invention provides a method for constructing a pure front-end static resource content publishing platform, where the method is applied to a content management platform of a CMS, and the method includes:
receiving and storing version modification data sent by a content maintainer;
triggering a version modification data pulling function of the code warehouse so that the code warehouse utilizes a GIT tool to pull the version modification data and store the version modification data;
triggering a deployment platform to carry out environment deployment, and constructing a content display platform according to the version modification data; the content display platform is a pure front-end static resource content publishing platform.
Preferably, triggering a version modification data pull function of the code repository to cause the code repository to pull the version modification data using a GIT tool, and storing the version modification data comprises:
creating a new branch on a main branch of a version to be modified in the code repository;
automatically triggering a CI flow of the code repository to cause the code repository to pull the version modification data to the content management platform and store the version modification data in the new branch.
Preferably, triggering the deployment platform to perform environmental deployment includes:
sending a first deployment instruction to a deployment platform, wherein the first deployment instruction is used for instructing the deployment platform to pull the version modification data from the new branch and issue the version modification data to a test environment, so that a content auditor accesses the test environment and audits the version modification data;
receiving an auditing passing instruction sent by the content auditor;
creating a tag on the primary branch to trigger a data pull function of the code repository to cause the code repository to pull the version of the most recent data from the content management platform and store the most recent data in the primary branch;
sending a second deployment instruction to the deployment platform, wherein the second deployment instruction is used for instructing the deployment platform to pull the latest data from the main branch;
and releasing the latest data to a production environment.
Preferably, triggering a version modification data pull function of the code repository to cause the code repository to pull the version modification data using a GIT tool, and storing the version modification data comprises:
and triggering a version modification data pulling function of the code warehouse, so that the code warehouse utilizes a GIT tool to pull the version modification data through an OpenApi interface of the content management platform and store the version modification data.
In a second aspect, an embodiment of the present invention provides an apparatus for constructing a pure front-end static resource content publishing platform, where the apparatus includes:
the version modification data receiving module is used for receiving and storing the version modification data sent by the content maintainer;
the trigger module is used for triggering the version modification data pulling function of the code warehouse so that the code warehouse utilizes a GIT tool to pull the version modification data and store the version modification data;
the triggering module is also used for triggering a deployment platform to carry out environment deployment and constructing a content display platform according to the version modification data; the content display platform is a pure front-end static resource content publishing platform.
Preferably, the triggering module is further configured to create a new branch on a main branch of the version to be modified in the code repository; automatically triggering a CI flow of the code repository to cause the code repository to pull the version modification data to the content management platform and store the version modification data in the new branch.
Preferably, the triggering module is further configured to send a first deployment instruction to a deployment platform, where the first deployment instruction is used to instruct the deployment platform to pull the version modification data from the new branch and issue the version modification data to a test environment, so that a content auditor accesses the test environment and audits the version modification data;
receiving an audit passing instruction sent by the content auditor;
creating a tag on the main branch, triggering a data pull function of the code repository, so that the code repository pulls the latest data of the version from the content management platform and stores the latest data into the main branch;
sending a second deployment instruction to the deployment platform, wherein the second deployment instruction is used for instructing the deployment platform to pull the latest data from the main branch;
and releasing the latest data to a production environment.
Preferably, the triggering module is further configured to trigger a version modification data pulling function of the code repository, so that the code repository uses a GIT tool to pull the version modification data through an OpenApi interface of the content management platform, and store the version modification data.
In a third aspect, an embodiment of the present invention provides an electronic device, including: a processor, a memory and a program stored on the memory and executable on the processor, the program, when executed by the processor, implementing the steps of the method of constructing a pure front-end static resource content publishing platform according to the first aspect.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when executed by a processor, the computer program implements the steps of the method for constructing a pure front-end static resource content publishing platform according to the first aspect.
Therefore, the embodiment of the invention solves the problems that the prior art needs to rely on a network request to acquire data and the SEO effect is influenced. The data request is preposed on the premise of ensuring that data maintenance is carried out on the content management platform and technical personnel are not required to participate in the change, so that the aim of maintaining the display platform data of the pure static resources on the content management background is fulfilled, the SEO effect can be indirectly improved, and the influence on data acquisition when the network is unstable is avoided.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 is a flowchart of a method for constructing a pure front-end static resource content publishing platform according to an embodiment of the present invention;
fig. 2 is an architecture diagram of a system to which a method for constructing a pure front-end static resource content publishing platform according to an embodiment of the present invention is applied;
fig. 3 is a schematic diagram illustrating interaction directions of steps of a method for constructing a pure front-end static resource content publishing platform according to an embodiment of the present invention;
fig. 4 is a block diagram of a structure of a device for constructing a pure front-end static resource content publishing platform according to an embodiment of the present invention;
fig. 5 is a block diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The embodiment of the invention provides a method for constructing a pure front-end static resource content publishing platform, which is applied to a content management platform of a CMS (content management system), and as shown in figure 1, the method comprises the following steps:
step S101, receiving and storing version modification data sent by a content maintainer;
step S102, triggering a version modification data pulling function of the code warehouse so that the code warehouse pulls the version modification data by using a GIT tool and stores the version modification data;
and S103, triggering a deployment platform to carry out environment deployment, and constructing a content display platform according to the version modification data.
The content display platform is a pure front-end static resource content publishing platform.
In step S101, version modification data sent by a content maintainer may be received and stored on a content management platform. Specifically, the content maintainer, upon receiving the modification scheme, can create a version submission on the content management platform. The embodiment of the invention reserves a content management platform, so that non-technical personnel such as a content maintainer in the market department can directly edit the concurrent version of the data to take effect.
In step S102, a version modification data pull function of the code repository may be triggered, so that the code repository utilizes the GIT tool to pull the version modification data and store the version modification data. In particular, a new branch may be created in the code repository, on the main branch of the version to be modified; and automatically triggering the CI flow of the code warehouse to enable the code warehouse to pull the version modification data to the content management platform and store the version modification data to the new branch. Therefore, the content display platform contains all data, when a user accesses the content display platform, the data do not need to be acquired from the content management platform through a network request in real time, the influence caused by unstable network is avoided, and the technical effects of high response speed, high rendering speed and no time delay are achieved.
In step S103, the deployment platform may be triggered to perform environment deployment, and a content display platform is constructed according to the version modification data; the content display platform is a pure front-end static resource content publishing platform. Specifically, a first deployment instruction may be sent to the deployment platform, where the first deployment instruction is used to instruct the deployment platform to pull the version modification data from the new branch and issue the version modification data to the test environment, so that the content auditor accesses the test environment and audits the version modification data, and after receiving an audit pass instruction sent by the content auditor, a tag may be created on the main branch to trigger a data pull function of the code repository, so that the code repository pulls the latest version data from the content management platform and stores the latest version data into the main branch, where the latest version data includes original version data and modified version data. Then, a second deployment instruction may be sent to the deployment platform, the second deployment instruction instructing the deployment platform to pull up the latest data from the main branch and to publish the latest data to the production environment. In the embodiment of the invention, the content display platform is a pure static resource, namely html contains all data, the SEO effect can be indirectly improved, non-technical personnel such as a content maintainer in the market department can directly edit the data concurrent version to take effect, technical personnel are not required to participate in the process, and the content maintainer can finish changing the version by self.
In one possible implementation, triggering the versioning data pull function of the code repository to cause the code repository to pull versioning data using the GIT tool, and storing the versioning data comprises: and triggering a version modification data pulling function of the code warehouse so that the code warehouse utilizes a GIT tool to pull the version modification data through an OpenApi interface of the content management platform and store the version modification data.
In summary, in the embodiment of the present invention, the content management platform interfaces with the code repository, and each version change is equivalent to the content display platform sending a new version. Specifically, the characteristic CI of the code warehouse can be used for data pulling and triggering the deployment platform to perform testing or deployment of the production environment, the testing environment for auditing and the formal outward production environment deployment are realized by the docking deployment platform, and the embodiment of the invention acquires data in the process of edition sending operation and constructs a purely static content display platform so as to move the data acquisition opportunity forward. Because the data acquisition request is preposed, a data interface does not need to be opened for a public network, and only an interface is provided in the intranet of the company, rather than the content data is acquired through a network request in real time when a user accesses a content display platform as in the prior art. Therefore, the access speed can be increased. Meanwhile, the display platform is guaranteed to be purely static resources, post-acquisition of network requests is not involved, and the data interface of the content management platform is hidden from the public network, so that the data can be prevented from being attacked and tampered, and the safety is greatly improved.
Fig. 2 is a system architecture diagram to which a method for constructing a pure front-end static resource content publishing platform according to an embodiment of the present invention is applied.
As shown in fig. 2, the content management platform is divided into a front end and a back end, the content management platform is in butt joint with the code warehouse, the code warehouse is in butt joint with the self-service deployment platform, the self-service deployment platform is in butt joint with the content display platform, and data can be stored on the content display platform. And the content management platform can trigger the deployment of a test environment and a production environment, and the code warehouse can pull data from the content management platform through an interface.
Fig. 3 is a schematic step interaction diagram illustrating a method for building a pure front-end static resource content publishing platform according to an embodiment of the present invention, and the method illustrated in fig. 3 may be applied to the system architecture diagram illustrated in fig. 2, and as illustrated in fig. 3, the method includes:
step 1: the content maintainer receives the modification scheme and creates a version for submission;
step 2: the management platform docking code warehouse creates a branch of the changed version based on a version issuing branch (rc);
and step 3: after the new branch is created, the CI is triggered, data of a corresponding version is actively pulled to the data management platform in the CI (pulled once), and the data are stored in the corresponding branch;
and 4, step 4: triggering a deployment platform to perform test environment deployment after data is pulled in the CI;
and 5: the deployment platform pulls the branch code;
step 6: packaging, constructing and releasing a test environment;
and 7: the operation is passed after the content auditor accesses the test environment to audit without errors, and the content management platform takes the modified content into effect;
and 8: the content management platform creates Tag on the publishing branch;
and step 9: after the Tag is created, the CI which also executes response pulls the latest data from the default interface;
step 10: triggering a deployment platform to deploy a production environment after data in the CI is pulled;
step 11: the deployment platform pulls the release branch (rc) code;
step 12: and packaging, constructing and releasing the formal environment.
Therefore, on the premise of keeping the advantages of the traditional CMS, the data acquisition is preposed, pure front-end static resources are realized, the data are acquired in the releasing process, the new version content display platform is deployed and released according to data compiling, the content data are acquired through a network request in real time when the new version content display platform is not accessed, and the access speed is increased. Meanwhile, the display platform is guaranteed to be purely static resources, network request post-acquisition is not involved, a data interface of the content management platform is hidden from a public network, and data tampering by attack is prevented. The safety is greatly improved.
Fig. 4 shows an apparatus 40 for building a pure front-end static resource content publishing platform according to an embodiment of the present invention, where the apparatus 40 includes:
a version modification data receiving module 401, configured to receive and store version modification data sent by a content maintainer;
a triggering module 402, configured to trigger a pull function of the version modification data of the code repository, so that the code repository pulls the version modification data by using the GIT tool and stores the version modification data;
the triggering module 402 is further configured to trigger the deployment platform to perform environment deployment, and construct a content display platform according to the version modification data; the content display platform is a pure front-end static resource content publishing platform.
In a possible implementation manner, the triggering module 402 is further configured to create a new branch on a main branch of the version to be modified in the code repository; and automatically triggering the CI flow of the code warehouse to enable the code warehouse to pull the version modification data to the content management platform and store the version modification data to the new branch.
In a possible implementation manner, the triggering module 402 is further configured to send a first deployment instruction to the deployment platform, where the first deployment instruction is used to instruct the deployment platform to pull the version modification data from the new branch and issue the version modification data to the test environment, so that the content auditor accesses the test environment and audits the version modification data;
receiving an auditing passing instruction sent by a content auditor;
creating a label on the main branch, and triggering a data pulling function of the code warehouse so that the code warehouse pulls the latest data of the version from the content management platform and stores the latest data into the main branch;
sending a second deployment instruction to the deployment platform, wherein the second deployment instruction is used for instructing the deployment platform to pull the latest data from the main branch;
and releasing the latest data to the production environment.
In a possible implementation manner, the triggering module is further configured to trigger a version modification data pulling function of the code repository, so that the code repository utilizes a GIT tool to pull the version modification data through an OpenApi interface of the content management platform and store the version modification data.
Therefore, on the premise of keeping the advantages of the traditional CMS, the data acquisition is preposed, pure front-end static resources are realized, the data are acquired in the releasing process, the new version content display platform is deployed and released according to data compiling, content data are acquired through a network request in real time when the new version content display platform is not accessed, and the access speed is increased. Meanwhile, the display platform is guaranteed to be purely static resources, network request post-acquisition is not involved, a data interface of the content management platform is hidden from a public network, and data tampering by attack is prevented. The safety is greatly improved.
An embodiment of the present invention further provides an electronic device 50, as shown in fig. 5, including: a processor 501, a memory 502 and a program stored in the memory 502 and capable of running on the processor 501, wherein the program when executed by the processor implements the steps of the method for constructing a pure front-end static resource content distribution platform as shown in fig. 1.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the embodiment of the method for constructing a pure front-end static resource content publishing platform shown in fig. 1, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
It should be noted that, in this document, 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 a … …" does not exclude the presence of another identical element in a process, method, article, or apparatus that comprises the element.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
While the present invention has been described with reference to the particular illustrative embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but is intended to cover various modifications, equivalent arrangements, and equivalents thereof, which may be made by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (6)
1. A method for constructing a pure front-end static resource content publishing platform is applied to a content management platform of a CMS, and comprises the following steps:
receiving and storing version modification data sent by a content maintainer;
triggering a version modification data pulling function of a code warehouse, so that the code warehouse utilizes a GIT tool to pull the version modification data and store the version modification data;
triggering a deployment platform to carry out environment deployment, and constructing a content display platform according to the version modification data; the content display platform is a pure front-end static resource content publishing platform;
triggering a version modification data pull function of a code repository to cause the code repository to pull the version modification data using a GIT tool, and storing the version modification data comprises:
creating a new branch on a main branch of a version to be modified in the code repository;
automatically triggering a CI flow of the code repository to cause the code repository to pull the version modification data to the content management platform and store the version modification data into the new branch;
triggering the deployment platform to perform environmental deployment comprises the following steps:
sending a first deployment instruction to a deployment platform, wherein the first deployment instruction is used for instructing the deployment platform to pull the version modification data from the new branch and issue the version modification data to a test environment, so that a content auditor accesses the test environment and audits the version modification data;
receiving an audit passing instruction sent by the content auditor;
creating a tag on the primary branch to trigger a data pull function of the code repository to cause the code repository to pull the version of the most recent data from the content management platform and store the most recent data into the primary branch;
sending a second deployment instruction to the deployment platform, wherein the second deployment instruction is used for instructing the deployment platform to pull the latest data from the main branch;
and releasing the latest data to a production environment.
2. The method of claim 1, wherein triggering a version modification data pull function of a code repository to cause the code repository to pull the version modification data using a GIT tool and store the version modification data comprises:
and triggering a version modification data pulling function of the code warehouse, so that the code warehouse utilizes a GIT tool to pull the version modification data through an OpenApi interface of the content management platform and store the version modification data.
3. An apparatus for constructing a pure front-end static resource content publishing platform, the apparatus comprising:
the version modification data receiving module is used for receiving and storing the version modification data sent by the content maintainer;
the trigger module is used for triggering a version modification data pulling function of the code warehouse so that the code warehouse utilizes a GIT tool to pull the version modification data and store the version modification data;
the triggering module is also used for triggering a deployment platform to carry out environment deployment and constructing a content display platform according to the version modification data; the content display platform is a pure front-end static resource content publishing platform;
the trigger module is also used for creating a new branch on the main branch of the version to be modified in the code warehouse; automatically triggering a CI flow of the code repository to cause the code repository to pull the version modification data to the content management platform and store the version modification data into the new branch;
the trigger module is further configured to send a first deployment instruction to a deployment platform, where the first deployment instruction is used to instruct the deployment platform to pull the version modification data from the new branch and issue the version modification data to a test environment, so that a content auditor accesses the test environment and audits the version modification data;
receiving an audit passing instruction sent by the content auditor;
creating a tag on the main branch, triggering a data pull function of the code repository, so that the code repository pulls the latest data of the version from the content management platform and stores the latest data into the main branch;
sending a second deployment instruction to the deployment platform, wherein the second deployment instruction is used for instructing the deployment platform to pull the latest data from the main branch;
and releasing the latest data to a production environment.
4. The apparatus of claim 3,
the trigger module is further configured to trigger a version modification data pull function of the code repository, so that the code repository pulls the version modification data through an OpenApi interface of the content management platform by using a GIT tool, and stores the version modification data.
5. An electronic device, comprising: processor, memory and a program stored on the memory and executable on the processor, which program, when executed by the processor, carries out the steps of the method of building a front-end-only static resource content publishing platform according to any of claims 1 to 2.
6. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a computer program which, when being executed by a processor, realizes the steps of the method for building a pure front-end static resource content publishing platform according to any one of claims 1 to 2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211470122.8A CN115562718B (en) | 2022-11-23 | 2022-11-23 | Method and device for constructing pure front-end static resource content publishing platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211470122.8A CN115562718B (en) | 2022-11-23 | 2022-11-23 | Method and device for constructing pure front-end static resource content publishing platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115562718A CN115562718A (en) | 2023-01-03 |
| CN115562718B true CN115562718B (en) | 2023-02-28 |
Family
ID=84770869
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211470122.8A Active CN115562718B (en) | 2022-11-23 | 2022-11-23 | Method and device for constructing pure front-end static resource content publishing platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115562718B (en) |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9916158B2 (en) * | 2016-07-20 | 2018-03-13 | International Business Machines Corporation | Cognitive feature analytics |
| US10827036B2 (en) * | 2016-09-19 | 2020-11-03 | Palantir Technologies Inc. | Version control machine |
| CN111552644A (en) * | 2020-04-28 | 2020-08-18 | 成都库珀区块链科技有限公司 | Micro-service architecture-based software continuous integration method |
| US11392360B2 (en) * | 2020-12-21 | 2022-07-19 | Atlassian Pty Ltd. | Systems and methods for redeploying source code builds |
| CN114237698A (en) * | 2021-12-23 | 2022-03-25 | 上海太翼数字健康管理有限公司 | Automatic deployment method based on GitLab and Harbor |
| CN114329297A (en) * | 2021-12-29 | 2022-04-12 | 深圳晶泰科技有限公司 | Content management system, static page management method, device and storage medium |
| CN115220779A (en) * | 2022-06-23 | 2022-10-21 | 浪潮软件集团有限公司 | Code base management method and device and computer medium |
| CN115080060A (en) * | 2022-07-20 | 2022-09-20 | 中国工商银行股份有限公司 | Application program distribution method, device, equipment, storage medium and program product |
-
2022
- 2022-11-23 CN CN202211470122.8A patent/CN115562718B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN115562718A (en) | 2023-01-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210287152A1 (en) | Workflow project design systems, apparatuses, and methods | |
| CN108279932B (en) | Method and device for dynamically configuring user interface of mobile terminal | |
| Xanthopoulos et al. | A comparative analysis of cross-platform development approaches for mobile applications | |
| CN101484894B (en) | Method for inheriting a wiki page layout for a wiki page | |
| US8510371B2 (en) | Method and system for creating IT-oriented server-based web applications | |
| WO2018082562A1 (en) | Method and device for compiling page data and rendering page, and storage medium | |
| CN106897053B (en) | Code publishing method and device | |
| US6948120B1 (en) | Computer-implemented system and method for hosting design-time controls | |
| WO2022121971A1 (en) | Front-end project processing method and apparatus, device, management system, and storage medium | |
| CN113641591B (en) | Test case generation method and device and test method and device | |
| CN113703893B (en) | Page rendering method, device, terminal and storage medium | |
| US20150121198A1 (en) | Style sheet speculative preloading | |
| US20160103815A1 (en) | Generating mobile web browser views for applications | |
| CN112835568A (en) | Project construction method and device | |
| WO2011136768A1 (en) | Processing content in a plurality of languages | |
| CN115562718B (en) | Method and device for constructing pure front-end static resource content publishing platform | |
| US20130067432A1 (en) | Application development toolkit | |
| CN112632333A (en) | Query statement generation method, device, equipment and computer readable storage medium | |
| US20230229671A1 (en) | Web services having live data updates | |
| US8726152B2 (en) | Automated detection and implementation of state and object modifications | |
| US20140337284A1 (en) | Synchronizing folders using a shadow folder hierarchy | |
| US20220334817A1 (en) | Cross platform configuration domain translation | |
| CN107077484B (en) | Generating a web browser view of an application | |
| CN113377375A (en) | Page processing method | |
| US10133758B2 (en) | Cell-based database management system |
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 |