CN115408303A - Method and device for maintaining front-end static resources, electronic equipment and storage medium - Google Patents
Method and device for maintaining front-end static resources, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115408303A CN115408303A CN202211355857.6A CN202211355857A CN115408303A CN 115408303 A CN115408303 A CN 115408303A CN 202211355857 A CN202211355857 A CN 202211355857A CN 115408303 A CN115408303 A CN 115408303A
- Authority
- CN
- China
- Prior art keywords
- content
- data
- maintenance
- branch
- platform
- 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.)
- Pending
Links
- 230000003068 static effect Effects 0.000 title claims abstract description 67
- 238000000034 method Methods 0.000 title claims abstract description 51
- 238000003860 storage Methods 0.000 title claims abstract description 11
- 238000012423 maintenance Methods 0.000 claims abstract description 167
- 238000007726 management method Methods 0.000 claims abstract description 144
- 238000011161 development Methods 0.000 claims abstract description 54
- 238000012360 testing method Methods 0.000 claims abstract description 43
- 238000012550 audit Methods 0.000 claims abstract description 26
- 238000012545 processing Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 22
- 230000008859 change Effects 0.000 description 14
- 230000008569 process Effects 0.000 description 8
- 230000008901 benefit Effects 0.000 description 5
- 230000000694 effects Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000005457 optimization Methods 0.000 description 4
- 238000004806 packaging method and process Methods 0.000 description 4
- 238000007796 conventional method Methods 0.000 description 3
- 238000009877 rendering Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000003032 molecular docking Methods 0.000 description 2
- 230000000717 retained effect Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- 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/3664—Environments for testing or debugging software
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method and a device for maintaining front-end static resources, electronic equipment and a storage medium, wherein the method comprises the following steps: acquiring data to be maintained from a code warehouse of the content display platform, and sending the data to be maintained to a content maintenance party; receiving a maintenance completion instruction sent by a content maintainer, creating a target branch in a code warehouse, and pushing maintenance completion data to the target branch; sending a deployment instruction to a deployment platform, wherein the deployment instruction is used for instructing the deployment platform to acquire maintenance completion data from a target branch and issue the maintenance completion data in a test environment; the deployment instructions are further used for instructing the deployment platform to obtain maintenance completion data from the development branch after the content management platform merges the target branch into the development branch and to issue the maintenance completion data to the real environment; and receiving an audit passing instruction sent by a content auditor, and merging the target branch to the development branch. The maintenance method of the front-end static resource has high maintenance efficiency.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a method and a device for maintaining front-end static resources, electronic equipment and a storage medium.
Background
The Content Management System (CMS) is a software System located between the front end of the WEB (WEB server) and the back end office System or process (Content creation, editing). The content creators, editors, publishers use the content management system to submit, modify, approve, and publish content.
In the first existing static resource management method, a CMS system is divided into a content display platform and a content management platform, the display platform is responsible for content display for users, the content management platform is responsible for data maintenance and is maintained by a content manager, and the content management platform has its own front and back ends for the manager to perform content maintenance and needs to support version control.
On the basis of the above scheme, currently, the following method two also exists for maintaining the front-end static resources:
and storing all the content data in a content display platform, wherein only the content display platform is arranged, and the content management platform is not provided, which is equivalent to the content data solidified in the code by the display platform. When the content is changed, the front-end code is directly modified to realize the change, and the changed front-end code is released on line again. Although the method is a pure front-end static resource, the data does not need a network request to be beneficial to SEO (Search Engine Optimization), a content management platform is not used for maintaining the content, and only codes can be directly modified (equivalent to developing a new version display platform) when the maintenance is needed; so that the content maintainer cannot independently complete the content maintenance, namely: when the content maintenance party maintains the content, technical personnel are always needed to assist in modifying the codes, and the maintenance efficiency is low.
Disclosure of Invention
Embodiments of the present invention provide a method and an apparatus for maintaining front-end static resources, an electronic device, and a storage medium, to solve the problem that in the second existing method, a content management platform is not available to maintain content, a content maintainer cannot independently complete content maintenance, and the content maintainer always needs technical staff to participate in content maintenance, which results in low maintenance efficiency.
In order to solve the technical problem, the invention is realized as follows:
in a first aspect, an embodiment of the present invention provides a method for maintaining front-end static resources, which is applied to a content management platform, and includes:
acquiring data to be maintained from a code warehouse of a content display platform, and sending the data to be maintained to a content maintainer, so that the content maintainer can maintain the data to be maintained;
receiving a maintenance completion instruction sent by the content maintainer, creating a target branch in the code warehouse, and pushing maintenance completion data to the target branch;
sending a deployment instruction to a deployment platform, wherein the deployment instruction is used for instructing the deployment platform to acquire the maintenance completion data from the target branch and issue the maintenance completion data in a test environment, so that a content auditor can audit the maintenance completion data in the test environment; the deployment instructions are further to instruct the deployment platform to obtain the completed maintenance data from a development branch and to publish the completed maintenance data to a real environment after the content management platform merges the target branch to the development branch;
and receiving an audit passing instruction sent by the content auditor, and merging the target branch to the development branch.
Alternatively, the first and second liquid crystal display panels may be,
the content management platform is a front-end content management platform of a content management system CMS.
Alternatively,
obtaining data to be maintained from a code repository of a display platform, comprising:
acquiring path configuration information;
and acquiring data to be maintained from a code warehouse through an OpenApi interface of the code warehouse according to the path configuration information, wherein the path configuration information is used for indicating an OpenApi interface path for acquiring the data to be maintained from the code warehouse.
Alternatively,
and pushing the completion maintenance data to the target branch by adopting a commit mode.
In a second aspect, an embodiment of the present invention provides a method for maintaining front-end static resources, which is applied to a deployment platform, and includes:
receiving a deployment instruction sent by a content management platform, acquiring maintenance completion data from a target branch, and issuing the maintenance completion data in a test environment, so that a content auditor can audit the maintenance completion data in the test environment; the target branch is created in a code warehouse of a content display platform after the content management platform receives a maintenance completion instruction sent by a content maintainer, the content management platform pushes maintenance completion data to the target branch, and the content management platform acquires data to be maintained from the code warehouse and sends the data to be maintained to the content maintainer, so that the content maintainer can maintain the data to be maintained; the content management platform merges the target branch to a development branch after receiving the auditing pass instruction sent by the content auditor;
and after merging the target branch to the development branch, the content management platform acquires the maintenance completion data from the development branch and issues the maintenance completion data to a real environment.
Alternatively,
the content management platform is a front-end content management platform of a content management system CMS.
In a third aspect, an embodiment of the present invention provides a device for managing front-end static resources, including:
the system comprises an acquisition module, a code warehouse and a content maintenance party, wherein the acquisition module is used for acquiring data to be maintained from the code warehouse of a display platform and sending the data to be maintained to the content maintenance party so that the content maintenance party can maintain the data to be maintained;
the first execution module is used for receiving a maintenance completion instruction sent by the content maintainer, creating a target branch in the code warehouse and pushing maintenance completion data to the target branch;
a second execution module, configured to send a deployment instruction to a deployment platform, where the deployment instruction is used to instruct the deployment platform to obtain the maintenance completion data from the target branch and issue the maintenance completion data in a test environment, so that a content auditor can audit the maintenance completion data in the test environment; the deployment instructions are further to instruct the deployment platform to obtain the completed maintenance data from a development branch and to publish the completed maintenance data to a real environment after the content management platform merges the target branch to the development branch;
the first execution module is further configured to receive an audit pass instruction sent by the content auditor, and merge the target branch to the development branch.
In a fourth aspect, an embodiment of the present invention provides an apparatus for managing front-end static resources, including:
the system comprises a receiving module, a content auditing module and a processing module, wherein the receiving module is used for receiving a deployment instruction sent by a content management platform, acquiring maintenance completion data from a target branch and issuing the maintenance completion data in a test environment, so that a content auditing party can audit the maintenance completion data in the test environment; the target branch is created in a code warehouse of a content display platform after the content management platform receives a maintenance completion instruction sent by a content maintainer, the content management platform pushes maintenance completion data to the target branch, and the content management platform acquires data to be maintained from the code warehouse and sends the data to be maintained to the content maintainer, so that the content maintainer can maintain the data to be maintained; the content management platform merges the target branch to a development branch after receiving the auditing pass instruction sent by the content auditor;
and the third execution module is used for acquiring the maintenance completion data from the development branch and issuing the maintenance completion data to a real environment after the content management platform merges the target branch to the development branch.
In a fifth aspect, an embodiment of the present invention provides an electronic device, which includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, where the program or instructions, when executed by the processor, implement the steps in the method for maintaining a front-end static resource according to any one of the first aspect or the second aspect.
In a sixth aspect, an embodiment of the present invention provides a readable storage medium, on which a program or instructions are stored, where the program or instructions, when executed by a processor, implement the steps in the method for maintaining front-end static resources according to any one of the first aspect or the second aspect.
In the embodiment of the invention, data to be maintained is obtained through a code warehouse of a content display platform, and the data to be maintained is sent to a content maintenance party, so that the content maintenance party can maintain the data to be maintained; receiving a maintenance completion instruction sent by the content maintainer, creating a target branch in the code warehouse, and pushing maintenance completion data to the target branch; sending a deployment instruction to a deployment platform, wherein the deployment instruction is used for instructing the deployment platform to acquire the maintenance completion data from the target branch and issue the maintenance completion data in a test environment, so that a content auditor can audit the maintenance completion data in the test environment; the deployment instructions are further to instruct the deployment platform to obtain the completed maintenance data from a development branch and to publish the completed maintenance data to a real environment after the content management platform merges the target branch to the development branch; the code warehouse is used for maintaining and releasing the codes to be maintained, the content maintainer does not need to modify the codes when maintaining the codes, the content maintainer can independently complete content maintenance, and the content maintainer does not need technical personnel to assist in modifying the codes when maintaining the contents, so that the maintenance efficiency is high.
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 diagram illustrating a conventional static resource management architecture;
FIG. 2 is a second schematic diagram of a conventional static resource management architecture;
FIG. 3 is a flowchart illustrating a method for maintaining front-end static resources according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a static resource management architecture to which the method for maintaining front-end static resources according to the embodiment of the present invention is applied;
FIG. 5 is a diagram illustrating a content change process corresponding to the static resource management architecture of FIG. 4;
FIG. 6 is a diagram illustrating a content maintenance flow corresponding to the static resource management architecture of FIG. 4;
FIG. 7 is a second flowchart illustrating a method for maintaining front-end static resources according to an embodiment of the present invention;
FIG. 8 is a schematic block diagram of a front-end static resource management apparatus according to an embodiment of the present invention;
FIG. 9 is a second schematic block diagram of an apparatus for managing front-end static resources according to an embodiment of the present invention;
FIG. 10 is a functional 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 Content Management System (CMS) is a software System located between the front end of the WEB (WEB server) and the back end office System or process (Content creation, editing). The content creators, editors, publishers use the content management system to submit, modify, approve, and publish content. The "content" referred to herein may include all information that you want to publish to Internet, intranet and Extranet sites, such as files, tables, pictures, data in databases and even videos.
Referring to fig. 1, fig. 1 is a schematic diagram of an existing static resource management architecture (a first existing method), a CMS system is divided into a content display platform and a content management platform, the display platform is responsible for displaying content for users, the content management platform is responsible for maintaining data and is maintained by a content manager, and the content management platform has its own front end and back end for the manager to maintain content and needs to support version control. When the display platform is accessed, the data acquires corresponding content data from the content management platform through a network request, and the display platform performs page rendering according to the data content for a user to check. When the content needs to be changed, the change can be edited in the management background, and after the approval is passed, the content display platform does not need to develop a version online and only needs to access again, namely the latest content.
On the basis of the above solution, referring to fig. 2, fig. 2 is a schematic diagram of a conventional static resource management architecture, and currently, the following method (conventional method two) also exists for maintaining front-end static resources:
and storing all content data in a content display platform, wherein the content display platform is only arranged, and the CMS content management platform is not arranged, which is equivalent to the content data being solidified in the code by the display platform. When the content is changed, the front-end code is directly modified to realize the change, and the changed front-end code is released online again. Although the method is a pure front-end static resource, the data does not need a network request to be beneficial to SEO (Search Engine Optimization), a content management platform is not used for maintaining the content, and only codes can be directly modified (equivalent to developing a new version display platform) when the maintenance is needed; so that the content maintainer cannot independently complete the content maintenance, namely: when the content maintenance party maintains the content, technical personnel are always needed to assist in modifying the codes, and the maintenance efficiency is low.
An embodiment of the present invention provides a method for maintaining a front-end static resource, which is applied to a content management platform, and referring to fig. 3, fig. 3 is a schematic flow diagram of the method for maintaining a front-end static resource according to the embodiment of the present invention, and includes:
step 11: acquiring data to be maintained from a code warehouse of a content display platform, and sending the data to be maintained to a content maintainer, so that the content maintainer can maintain the data to be maintained;
step 12: receiving a maintenance completion instruction sent by the content maintainer, creating a target branch in the code warehouse, and pushing maintenance completion data to the target branch;
step 13: sending a deployment instruction to a deployment platform, wherein the deployment instruction is used for instructing the deployment platform to acquire the maintenance completion data from the target branch and issue the maintenance completion data in a test environment, so that a content auditor can audit the maintenance completion data in the test environment; the deployment instructions are further to instruct the deployment platform to obtain the completed maintenance data from a development branch and to publish the completed maintenance data to a real environment after the content management platform merges the target branch to the development branch;
step 14: and receiving an audit passing instruction sent by the content auditor, and merging the target branch to the development branch.
Exemplarily, referring to fig. 4, fig. 4 is a schematic diagram of a static resource management architecture to which a maintenance method of front-end static resources according to an embodiment of the present invention is applied, where the architecture layers (a-E):
A. on the basis of the second conventional method shown in fig. 2, a CMS management background is introduced, but only a front end (which is equivalent to a front-end content management platform of a CMS of a content management system in the embodiment of the present invention) is provided, and a server is not required;
B. taking a code warehouse of a content display platform as a 'server side', and providing interface service for a CMS management background through OpenApi of the code warehouse;
C. the method comprises the following steps of creating a version, editing content, and publishing (development version), namely creating branches of a code warehouse, submitting the branches by using commit, and performing actions such as branch combination and Tag creation;
D. the test environment for auditing and the formal outward production environment are deployed through a docking deployment platform;
E. version management is implemented using git branches.
Illustratively, referring to fig. 5, fig. 5 is a schematic diagram of a content change flow corresponding to the static resource management architecture in fig. 4, and includes the following steps (F-H):
F. proposing a modification to a content (i.e., selecting data to be maintained);
G. the content maintainer accesses the management background;
H. the management background pulls json data (json data, which is equivalent to data to be maintained in the embodiment of the invention) to the code warehouse through an OpenApi and displays the json data (which is equivalent to sending the data to be maintained to a content maintenance party in the embodiment of the invention, so that the content maintenance party can maintain the data to be maintained).
Illustratively, referring to fig. 6, fig. 6 is a schematic diagram of a content maintenance flow corresponding to the static resource management architecture in fig. 4, which includes the following steps (1-10):
1: the content maintainer creates a modified version to change the content on the management platform;
2: submitting a change, namely creating a new branch (equivalent to a target branch in the embodiment of the invention) in a code warehouse through OpenApi based on a release branch (rc) and pushing a commit (equivalent to pushing the completion maintenance data to the target branch in the embodiment of the invention);
3: the management platform triggers the deployment platform to deploy the test environment;
4: the deployment platform pulls a new branch code (which is equivalent to the deployment platform acquiring the maintenance completion data from the target branch in the embodiment of the present invention);
5: packaging, constructing and issuing a test environment (which is equivalent to the deployment platform issuing the maintenance completion data in the test environment in the embodiment of the present invention, so that a content auditor can audit the maintenance completion data in the test environment);
6: the content auditor accesses the test environment to audit and pass the operation after no error;
7: the management background merges the branches into a publishing branch (rc, which is equivalent to a development branch in the embodiment of the invention);
8: after the merging is finished, triggering a deployment platform to deploy a formal environment (equivalent to a real environment in the embodiment of the invention);
9: the deployment platform pulls a release branch (rc) code (which is equivalent to acquiring the completion maintenance data from the development branch in the embodiment of the present invention);
10: packaging and constructing a deployment formal environment (which is equivalent to publishing the completion maintenance data to a real environment in the embodiment of the present invention).
The method can maintain the data in the content management platform, realize pure front-end static resources and extract technicians from the content changing process; the advantages of the two prior methods in fig. 1 and 2 are retained, and the following technical effects ((a) - (d)) are achieved:
(a) The CMS platform is simple to develop, has no service end, and only needs to be docked with a code warehouse of the content display platform to realize data change;
(b) Websites are static resources, the displayed content does not need to be acquired by a network request, the access rendering is fast, and SEO (Search Engine Optimization) is facilitated;
(c) The content maintainer can operate without the participation of technicians when the content is changed;
(d) And by using Git as version control, the development workload of the CMS platform is greatly reduced.
In the embodiment of the invention, the data to be maintained is obtained through a code warehouse of a content display platform, and the data to be maintained is sent to a content maintainer, so that the content maintainer can maintain the data to be maintained; receiving a maintenance completion instruction sent by the content maintainer, creating a target branch in the code warehouse, and pushing maintenance completion data to the target branch; sending a deployment instruction to a deployment platform, wherein the deployment instruction is used for instructing the deployment platform to acquire the maintenance completion data from the target branch and issue the maintenance completion data in a test environment, so that a content auditor can audit the maintenance completion data in the test environment; the deployment instructions are further to instruct the deployment platform to obtain the completed maintenance data from a development branch and to publish the completed maintenance data to a real environment after the content management platform merges the target branch to the development branch; the method and the device for maintaining the code of the content have the advantages that the code to be maintained can be maintained and issued through the code warehouse, the code does not need to be modified when the code is maintained by the content maintainer, the content maintainer can independently complete content maintenance, technicians do not need to assist in modifying the code when the content maintainer maintains the content, time consumed by communicating with the technicians about maintenance matters and modifying the code according to the maintenance matters by the technicians is avoided, and the maintenance efficiency is high.
In some embodiments of the present invention, the first and second electrodes are, optionally,
the content management platform is a front-end content management platform of a content management system CMS.
In some embodiments of the present invention, the first and second electrodes are, optionally,
obtaining data to be maintained from a code repository of a display platform, comprising:
acquiring path configuration information;
and acquiring data to be maintained from a code warehouse through an OpenApi interface of the code warehouse according to the path configuration information, wherein the path configuration information is used for indicating an OpenApi interface path for acquiring the data to be maintained from the code warehouse.
Illustratively, referring to fig. 5, fig. 5 is a schematic diagram of a content change flow corresponding to the static resource management architecture in fig. 4, and includes the following steps (F-H):
F. proposing a modification to a content (i.e., selecting data to be maintained);
G. the content maintainer accesses the management background;
H. the management background pulls json data (json data, which is equivalent to data to be maintained in the embodiment of the present invention) to the code warehouse through the OpenApi by using a path of a data file (which is equivalent to path configuration information in the embodiment of the present invention; pulls json data to the code warehouse through the OpenApi, which is equivalent to "acquiring data to be maintained from the code warehouse through an OpenApi interface of the code warehouse according to the path configuration information") and displays the json data (which is equivalent to sending the data to be maintained to a content maintenance party in the embodiment of the present invention), so that the content maintenance party can maintain the data to be maintained).
In some embodiments of the present invention, the first and second electrodes are, optionally,
and pushing the maintenance completion data to the target branch by adopting a commit mode.
Illustratively, referring to fig. 6, fig. 6 is a schematic diagram of a content maintenance flow corresponding to the static resource management architecture in fig. 4, wherein step 2:
the change submitting, that is, the platform creates a new branch (equivalent to a target branch in the embodiment of the present invention) in the code repository through the OpenApi based on the release branch (rc) and pushes commit (equivalent to push the completion maintenance data to the target branch in the embodiment of the present invention in a commit manner).
An embodiment of the present invention provides a method for maintaining front-end static resources, which is applied to a deployment platform, and is shown in fig. 7, where fig. 7 is a second flowchart of the method for maintaining front-end static resources according to the embodiment of the present invention, and the method includes:
step 21: receiving a deployment instruction sent by a content management platform, acquiring maintenance completion data from a target branch, and issuing the maintenance completion data in a test environment, so that a content auditor can audit the maintenance completion data in the test environment; the target branch is created in a code warehouse of a content display platform after the content management platform receives a maintenance completion instruction sent by a content maintainer, the content management platform pushes maintenance completion data to the target branch, and the content management platform acquires data to be maintained from the code warehouse and sends the data to be maintained to the content maintainer, so that the content maintainer can maintain the data to be maintained; the content management platform merges the target branch to a development branch after receiving the auditing pass instruction sent by the content auditor;
step 22: and after merging the target branch to the development branch, the content management platform acquires the maintenance completion data from the development branch and issues the maintenance completion data to a real environment.
Exemplarily, referring to fig. 4, fig. 4 is a schematic diagram of a static resource management architecture to which a maintenance method of front-end static resources according to an embodiment of the present invention is applied, where the architecture layers (a-E):
A. based on the second conventional method shown in fig. 2, a CMS management background is introduced, but only a front end (which is equivalent to a front-end content management platform of a CMS of a content management system in the embodiment of the present invention) does not need a server;
B. taking a code warehouse of a content display platform as a 'server side', and providing interface service for a CMS management background through OpenApi of the code warehouse;
C. the method comprises the following steps of creating a version, editing content, publishing (development version), namely creating branches of a code warehouse, submitting the branches by adopting commit, and performing actions such as branch combination and Tag creation;
D. the test environment for auditing and the formal outward production environment are deployed through a docking deployment platform;
E. version management is implemented using the git branch.
Illustratively, referring to fig. 5, fig. 5 is a schematic diagram of a content change flow corresponding to the static resource management architecture in fig. 4, and includes the following steps (F-H):
F. to propose a modification to a content (i.e. to select data to be maintained);
G. the content maintainer accesses the management background;
H. a management background pulls json data (json data, which is equivalent to data to be maintained in the embodiment of the present invention) to a code warehouse through an OpenApi through a path of a data file maintained by the management background and displays the json data (which is equivalent to the content management platform in the embodiment of the present invention acquiring the data to be maintained from the code warehouse and sending the data to be maintained to the content maintainer, so that the content maintainer can maintain the data to be maintained).
Illustratively, referring to fig. 6, fig. 6 is a schematic diagram of a content maintenance flow corresponding to the static resource management architecture in fig. 4, including the following steps (1-10):
1: the content maintainer creates a modified version to change the content on the management platform;
2: submitting a change, namely creating a new branch (equivalent to a target branch in the embodiment of the invention) in the code warehouse through OpenApi on the basis of a release branch (rc) by the platform, and pushing a commit (equivalent to pushing the completion maintenance data to the target branch by the content management platform in the embodiment of the invention);
3: the management platform triggers the deployment platform to deploy the test environment;
4: the deployment platform pulls a new branch code (which is equivalent to obtaining the maintenance completion data from the target branch in the embodiment of the present invention);
5: packaging, constructing and issuing a test environment (which is equivalent to issuing the maintenance completion data in the test environment in the embodiment of the invention, so that a content auditor can audit the maintenance completion data in the test environment);
6: the content auditor accesses the test environment to audit and pass the operation after no error;
7: the management background merges the branches into a publishing branch (rc, which is equivalent to a development branch in the embodiment of the invention);
8: after the merging is finished, triggering a deployment platform to deploy a formal environment (equivalent to a real environment in the embodiment of the invention);
9: a deployment platform pulls a release branch (rc) code (which is equivalent to obtaining completion maintenance data from the development branch in the embodiment of the present invention);
10: packaging construction deploys a formal environment (which is equivalent to publishing the completion maintenance data to a real environment in embodiments of the invention).
The method can maintain the data in the content management platform, realize pure front-end static resources and extract technicians from the content changing process; the advantages of the two prior art solutions in fig. 1 and 2 are retained, and the following technical effects ((a) - (d)) are achieved:
(a) The CMS platform is simple to develop, has no service end, and only needs to be docked with a code warehouse of the content display platform to realize data change;
(b) Websites are static resources, the displayed content does not need to be acquired by a network request, the access rendering is fast, and SEO (Search Engine Optimization) is facilitated;
(c) When the content is changed, a content maintainer can operate without the participation of technicians;
(d) And by using Git as version control, the development workload of the CMS platform is greatly reduced.
In the embodiment of the invention, by receiving a deployment instruction sent by a content management platform, the maintenance completion data is obtained from a target branch and is issued in a test environment, so that a content auditor can audit the maintenance completion data in the test environment; the target branch is created in a code warehouse of a content display platform after the content management platform receives a maintenance completion instruction sent by a content maintainer, the content management platform pushes maintenance completion data to the target branch, and the content management platform acquires data to be maintained from the code warehouse and sends the data to be maintained to the content maintainer, so that the content maintainer can maintain the data to be maintained; the content management platform merges the target branch to a development branch after receiving the auditing pass instruction sent by the content auditor; the content management platform merges the target branch to the development branch, acquires the maintenance completion data from the development branch and issues the maintenance completion data to a real environment.
In some embodiments of the present invention, the first and second electrodes are, optionally,
the content management platform is a front-end content management platform of a content management system CMS.
An embodiment of the present invention provides a front-end static resource management device, referring to fig. 8, where fig. 8 is a schematic block diagram of the front-end static resource management device according to the embodiment of the present invention, and the front-end static resource management device 80 includes:
the acquisition module 81 is configured to acquire data to be maintained from a code repository of a display platform and send the data to be maintained to a content maintainer, so that the content maintainer can maintain the data to be maintained;
a first execution module 82, configured to receive a maintenance completion instruction sent by the content maintainer, create a target branch in the code warehouse, and push maintenance completion data to the target branch;
a second execution module 83, configured to send a deployment instruction to a deployment platform, where the deployment instruction is used to instruct the deployment platform to obtain the maintenance completion data from the target branch and issue the maintenance completion data in a test environment, so that a content auditor can audit the maintenance completion data in the test environment; the deployment instructions are further to instruct the deployment platform to obtain the completed maintenance data from a development branch after a content management platform merges the target branch to the development branch and to publish the completed maintenance data to a real environment;
the first execution module 82 is further configured to receive an audit passing instruction sent by the content auditor, and merge the target branch to the development branch.
In some embodiments of the present invention, the first and second electrodes are, optionally,
the obtaining module 81 is further configured to obtain path configuration information;
the obtaining module 81 is further configured to obtain, according to the path configuration information, data to be maintained from the code repository through an OpenApi interface of the code repository, where the path configuration information is used to indicate an OpenApi interface path for obtaining the data to be maintained from the code repository.
In some embodiments of the present invention, the first and second electrodes may, optionally,
the first executing module 82 is further configured to push the maintenance completion data to the target branch in a commit manner.
The management device 80 for front-end static resources provided in this embodiment of the application can implement each process implemented in the method embodiments of fig. 1 to fig. 6, and achieve the same technical effect, and is not described here again to avoid repetition.
An embodiment of the present invention provides a front-end static resource management device, referring to fig. 9, where fig. 9 is a schematic block diagram of a front-end static resource management device according to a second embodiment of the present invention, and the front-end static resource management device 90 includes:
the receiving module 91 is configured to receive a deployment instruction sent by the content management platform, acquire maintenance completion data from a target branch, and issue the maintenance completion data in a test environment, so that a content auditor can audit the maintenance completion data in the test environment; the target branch is created in a code warehouse of a content display platform after the content management platform receives a maintenance completion instruction sent by a content maintainer, the content management platform pushes maintenance completion data to the target branch, and the content management platform acquires data to be maintained from the code warehouse and sends the data to be maintained to the content maintainer, so that the content maintainer can maintain the data to be maintained; the content management platform merges the target branch to a development branch after receiving the auditing pass instruction sent by the content auditor;
a third executing module 92, configured to, after the content management platform merges the target branch to the development branch, obtain the maintenance completion data from the development branch and issue the maintenance completion data to a real environment.
The management device 90 for front-end static resources provided in this embodiment of the present application can implement each process implemented in the method embodiments of fig. 1 to fig. 6, and achieve the same technical effect, and is not described here again to avoid repetition.
Referring to fig. 10, fig. 10 is a schematic block diagram of an electronic device 100 according to an embodiment of the present invention, and includes a processor 101, a memory 102, and a program or an instruction stored in the memory 102 and executable on the processor 101, where the program or the instruction implements steps in any front-end static resource management method according to the present invention when executed by the processor.
The embodiment of the present invention provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the foregoing embodiment of the front-end static resource management method, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.
The readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (10)
1. A method for maintaining front-end static resources is applied to a content management platform and is characterized by comprising the following steps:
acquiring data to be maintained from a code warehouse of a content display platform, and sending the data to be maintained to a content maintainer, so that the content maintainer can maintain the data to be maintained;
receiving a maintenance completion instruction sent by the content maintainer, creating a target branch in the code warehouse, and pushing maintenance completion data to the target branch;
sending a deployment instruction to a deployment platform, wherein the deployment instruction is used for instructing the deployment platform to acquire the maintenance completion data from the target branch and issue the maintenance completion data in a test environment, so that a content auditor can audit the maintenance completion data in the test environment; the deployment instructions are further to instruct the deployment platform to obtain the completed maintenance data from a development branch and to publish the completed maintenance data to a real environment after the content management platform merges the target branch to the development branch;
and receiving an audit passing instruction sent by the content auditor, and merging the target branch to the development branch.
2. The method for maintaining front-end static resources according to claim 1, wherein:
the content management platform is a front-end content management platform of a content management system CMS.
3. The method for maintaining front-end static resources according to claim 1, wherein:
obtaining data to be maintained from a code repository of a display platform, comprising:
acquiring path configuration information;
and acquiring data to be maintained from a code warehouse through an OpenApi interface of the code warehouse according to the path configuration information, wherein the path configuration information is used for indicating an OpenApi interface path for acquiring the data to be maintained from the code warehouse.
4. The method for maintaining front-end static resources according to claim 1, wherein:
and pushing the maintenance completion data to the target branch by adopting a commit mode.
5. A maintenance method of front-end static resources is applied to a deployment platform and is characterized by comprising the following steps:
receiving a deployment instruction sent by a content management platform, acquiring maintenance completion data from a target branch, and issuing the maintenance completion data in a test environment, so that a content auditor can audit the maintenance completion data in the test environment; the target branch is created in a code warehouse of a content display platform after the content management platform receives a maintenance completion instruction sent by a content maintainer, the content management platform pushes maintenance completion data to the target branch, and the content management platform acquires data to be maintained from the code warehouse and sends the data to be maintained to the content maintainer, so that the content maintainer can maintain the data to be maintained; the content management platform merges the target branch to a development branch after receiving the auditing pass instruction sent by the content auditor;
and after merging the target branch to the development branch, the content management platform acquires the maintenance completion data from the development branch and issues the maintenance completion data to a real environment.
6. The method for maintaining front-end static resources of claim 5, wherein:
the content management platform is a front-end content management platform of a content management system CMS.
7. An apparatus for managing front-end static resources, comprising:
the system comprises an acquisition module, a display module and a management module, wherein the acquisition module is used for acquiring data to be maintained from a code warehouse of a display platform and sending the data to be maintained to a content maintenance party so that the content maintenance party can maintain the data to be maintained;
the first execution module is used for receiving a maintenance completion instruction sent by the content maintainer, creating a target branch in the code warehouse and pushing maintenance completion data to the target branch;
a second execution module, configured to send a deployment instruction to a deployment platform, where the deployment instruction is used to instruct the deployment platform to obtain the maintenance completion data from the target branch and issue the maintenance completion data in a test environment, so that a content auditor can audit the maintenance completion data in the test environment; the deployment instructions are further to instruct the deployment platform to obtain the completed maintenance data from a development branch and to publish the completed maintenance data to a real environment after a content management platform merges the target branch to the development branch;
the first execution module is further configured to receive an audit passing instruction sent by the content auditor, and merge the target branch to the development branch.
8. An apparatus for managing front-end static resources, comprising:
the system comprises a receiving module, a content auditing module and a processing module, wherein the receiving module is used for receiving a deployment instruction sent by a content management platform, acquiring maintenance completion data from a target branch and issuing the maintenance completion data in a test environment, so that a content auditing party can audit the maintenance completion data in the test environment; the target branch is created in a code warehouse of a content display platform after the content management platform receives a maintenance completion instruction sent by a content maintainer, the content management platform pushes maintenance completion data to the target branch, and the content management platform acquires data to be maintained from the code warehouse and sends the data to be maintained to the content maintainer, so that the content maintainer can maintain the data to be maintained; the content management platform merges the target branch to a development branch after receiving the auditing pass instruction sent by the content auditor;
and the third execution module is used for acquiring the maintenance completion data from the development branch and issuing the maintenance completion data to a real environment after the content management platform merges the target branch to the development branch.
9. An electronic device, characterized in that: comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, which program or instructions, when executed by the processor, implement the steps in the method for maintaining front-end static resources according to any one of claims 1 to 6.
10. A readable storage medium, characterized by: the readable storage medium stores thereon a program or instructions which, when executed by a processor, implement the steps in the method for maintaining front-end static resources of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211355857.6A CN115408303A (en) | 2022-11-01 | 2022-11-01 | Method and device for maintaining front-end static resources, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211355857.6A CN115408303A (en) | 2022-11-01 | 2022-11-01 | Method and device for maintaining front-end static resources, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115408303A true CN115408303A (en) | 2022-11-29 |
Family
ID=84169138
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211355857.6A Pending CN115408303A (en) | 2022-11-01 | 2022-11-01 | Method and device for maintaining front-end static resources, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115408303A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180060065A1 (en) * | 2016-09-01 | 2018-03-01 | Dropbox, Inc. | Advanced packaging techniques for improving work flows |
| CN109284225A (en) * | 2018-08-22 | 2019-01-29 | 深圳点猫科技有限公司 | A kind of quality determining method and electronic equipment of multi-person synergy exploitation programming code |
| CN110851355A (en) * | 2019-10-28 | 2020-02-28 | 腾讯科技（深圳）有限公司 | Front-end engineering implementation method and device, storage medium and electronic equipment |
| US20200125485A1 (en) * | 2018-10-17 | 2020-04-23 | Servicenow, Inc. | Environment for continuous testing and integration of software |
| CN111610967A (en) * | 2020-04-08 | 2020-09-01 | 曙光信息产业(北京)有限公司 | Continuous integration and deployment method and device based on cloud management platform |
| CN112631564A (en) * | 2020-12-18 | 2021-04-09 | 微民保险代理有限公司 | Content management system-based interface generation method, device, equipment and storage medium |
| CN113448837A (en) * | 2020-11-03 | 2021-09-28 | 北京新氧科技有限公司 | Development and test environment deployment method, system, electronic device, and medium |
| CN114329297A (en) * | 2021-12-29 | 2022-04-12 | 深圳晶泰科技有限公司 | Content management system, static page management method, device and storage medium |
-
2022
- 2022-11-01 CN CN202211355857.6A patent/CN115408303A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180060065A1 (en) * | 2016-09-01 | 2018-03-01 | Dropbox, Inc. | Advanced packaging techniques for improving work flows |
| CN109284225A (en) * | 2018-08-22 | 2019-01-29 | 深圳点猫科技有限公司 | A kind of quality determining method and electronic equipment of multi-person synergy exploitation programming code |
| US20200125485A1 (en) * | 2018-10-17 | 2020-04-23 | Servicenow, Inc. | Environment for continuous testing and integration of software |
| CN110851355A (en) * | 2019-10-28 | 2020-02-28 | 腾讯科技（深圳）有限公司 | Front-end engineering implementation method and device, storage medium and electronic equipment |
| CN111610967A (en) * | 2020-04-08 | 2020-09-01 | 曙光信息产业(北京)有限公司 | Continuous integration and deployment method and device based on cloud management platform |
| CN113448837A (en) * | 2020-11-03 | 2021-09-28 | 北京新氧科技有限公司 | Development and test environment deployment method, system, electronic device, and medium |
| CN112631564A (en) * | 2020-12-18 | 2021-04-09 | 微民保险代理有限公司 | Content management system-based interface generation method, device, equipment and storage medium |
| CN114329297A (en) * | 2021-12-29 | 2022-04-12 | 深圳晶泰科技有限公司 | Content management system, static page management method, device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9940127B1 (en) | System and method for providing real-time execution of source code in a collaborative online software development environment | |
| CN106027330B (en) | A kind of front end system message test method and simulation baffle system | |
| US8127237B2 (en) | Active business client | |
| US8813024B2 (en) | System and a method for cross-platform porting of business application and making them contextually-aware on target platforms | |
| DE112018002872T5 (en) | INTEGRATED SYSTEM FOR RULING, SIMULATION, VERSION CONTROL AND BUSINESS PROCESS MANAGEMENT | |
| US7877731B2 (en) | Formatting and viewing source objects | |
| US20090319981A1 (en) | System and method for generating implementation artifacts for contextually-aware business applications | |
| US8495559B2 (en) | Extracting platform independent models from composite applications | |
| US20080102422A1 (en) | Method of and systems for business and narrative development | |
| US20090327002A1 (en) | Automated workflow for content localization management | |
| CN112131504B (en) | Webpage editing and displaying method, device, equipment and storage medium | |
| US8752002B2 (en) | Automatically generating artifacts for service delivery | |
| US8234570B2 (en) | Harvesting assets for packaged software application configuration | |
| EP3518161A1 (en) | System and method for distributing ar content | |
| US20230418835A1 (en) | Systems and methods for presenting web application content | |
| US20130067432A1 (en) | Application development toolkit | |
| CN104980313A (en) | System and method for testing executable instruction | |
| US20230229671A1 (en) | Web services having live data updates | |
| CN114756228A (en) | Page processing method, device, equipment and storage medium | |
| EP3819760A1 (en) | Methods and apparatus for generating a platform-agnostic mobile application configuration data structure with a dynamic quiz | |
| CN117291517A (en) | Method and device for constructing approval process | |
| CN113378346A (en) | Method and device for model simulation | |
| CN115408303A (en) | Method and device for maintaining front-end static resources, electronic equipment and storage medium | |
| CN113253991A (en) | Task visualization processing method and device, electronic equipment and storage medium | |
| Kroiß | From backend to frontend: Case study on adopting Mmcro frontends from a single page ERP application monolith |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20221129 |
|
| RJ01 | Rejection of invention patent application after publication |