Browser page data storage method, device and equipment and storage medium

Abstract

The invention discloses a browser page data storage method, device and equipment and a storage medium, and relates to the technical field of internet and the field of financial science and tech, the browser page data storage method comprises the steps of setting a resource backup directory for a front-end container, and synchronously mounting the resource backup directory to a file system of target equipment; periodically backing up the static resource data in the static resource data directory of the front-end container, and storing the backed-up static resource data to a file system of the target equipment; based on the backup time information, performing file cleaning on static resource data backed up in a file system of the target equipment to generate a target backup file; and storing the target backup file in a resource backup directory, and copying the static resource data in the resource backup directory to a static resource data directory in the newly deployed front-end container. According to the technical scheme, the stability of the browser in the page jumping process is ensured, and the use experience of a user is improved.

Description

Technical Field

[0001] The present invention relates to the fields of Internet technology and financial technology, and in particular to a method, device, equipment and storage medium for storing browser page data. Background Art

[0002] In the banking operating system, when users use browsers to access the front-end system, due to network performance considerations, the front-end system usually does not load the static resource data of all front-end pages at once. It usually only loads the static resource data required by the current page, and dynamically loads the corresponding static resource data of the new page when the page jump is triggered.

[0003] In the current banking operating system, there is inconsistency in the life cycle management of static resource data between the browser and the front-end container, resulting in file life cycle conflicts in certain specific scenarios. For example, a user accesses the front-end system on a browser and keeps browsing page A. Page A saves the resource file address for jumping to page B, but the action of jumping to page B has not been triggered. At this time, the server deploys a new front-end container, and all the resource data in the front-end container is refreshed. If the user triggers the jump to page B after the new front-end container is deployed, the resource data corresponding to the resource address of page B originally saved in page A is no longer in the new container, resulting in failure to access page B. Summary of the invention

[0004] The present invention provides a method, device, equipment and storage medium for storing browser page data, so as to improve the stability during the browser page jump process.

[0005] According to one aspect of the present invention, a method for storing browser page data is provided, the method comprising:

[0006] A resource backup directory is set for the front-end container, and the resource backup directory is synchronously mounted to the file system of the target device; wherein the resource backup directory is used to back up the static resource data displayed by the browser page in the current front-end container; the target device refers to the back-end server device running the browser;

[0007] Periodically back up the static resource data in the static resource data directory of the front-end container, and store the backed-up static resource data in the file system of the target device;

[0008] Based on the backup time information, the static resource data backed up in the file system of the target device is cleaned up to generate a target backup file;

[0009] The target backup file is stored in a resource backup directory, and the static resource data in the resource backup directory is copied to the static resource data directory in the newly deployed front-end container.

[0010] According to another aspect of the present invention, there is provided a device for storing browser page data, the device comprising:

[0011] A directory mounting module is used to set a resource backup directory for the front-end container and synchronously mount the resource backup directory to the file system of the target device; wherein the resource backup directory is used to back up the static resource data displayed by the browser page in the current front-end container; the target device refers to the back-end server device running the browser;

[0012] A file backup module, used to periodically back up the static resource data in the static resource data directory of the front-end container, and store the backed-up static resource data in the file system of the target device;

[0013] A backup cleaning module is used to clean up the static resource data backed up in the file system of the target device based on the backup time information to generate a target backup file;

[0014] The backup deployment module is used to store the target backup file in a resource backup directory, and copy the static resource data in the resource backup directory to the static resource data directory in the newly deployed front-end container.

[0015] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0016] at least one processor; and

[0017] a memory communicatively connected to the at least one processor; wherein,

[0018] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the browser page data storage method described in any embodiment of the present invention.

[0019] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the browser page data storage method described in any embodiment of the present invention when executed.

[0020] According to another aspect of the present invention, a computer program product is provided. The computer program product includes a computer program. When the computer program is executed by a processor, the method for storing browser page data according to any embodiment of the present invention is implemented.

[0021] The technical solution of the embodiment of the present invention sets a shared resource backup directory in the file system of the front-end container and the target device, and uses the file system of the target device to periodically back up the static resource data in the front-end container and store it in the resource backup directory, and copies the files in the resource backup directory to the newly deployed front-end container, so that the front-end container not only stores the latest deployed front-end resource data, but also stores all static resource data within the backup cycle, avoiding the problem of inconsistent life cycle management of the same file by the browser and the front-end container, ensuring the stability of the browser during page jumps, and improving the user experience.

[0022] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0024] Figure 1 is a flowchart of a method for storing browser page data provided according to Embodiment 1 of the present invention;

[0025] Figure 2 is a flow chart of a method for storing browser page data provided according to Embodiment 2 of the present invention;

[0026] Figure 3 is a schematic diagram of the structure of a storage device for browser page data provided according to Embodiment 3 of the present invention;

[0027] Figure 4 It is a structural schematic diagram of an electronic device for implementing the browser page data storage method according to an embodiment of the present invention. DETAILED DESCRIPTION

[0028] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0029] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0030] Embodiment 1

[0031] Figure 1 A flowchart of a method for storing browser page data is provided for the first embodiment of the present invention. This embodiment is applicable to the case where a page is displayed through a browser. The method can be executed by a storage device for browser page data. The storage device for browser page data can be implemented in the form of hardware and / or software. The storage device for browser page data can be configured in various general-purpose computing devices, such as server devices. Figure 1 As shown, the method includes:

[0032] S110: Set a resource backup directory for the front-end container, and synchronously mount the resource backup directory to the file system of the target device.

[0033] The resource backup directory may be used to back up static resource data displayed by the browser page in the current front-end container; the target device may refer to a back-end server device running the browser.

[0034] In an embodiment of the present invention, whenever a new front-end container is deployed in the target device, a new resource backup directory will be created in the front-end container, and the resource file directory will be mounted to the host file system outside the container (i.e., the file system of the target device, or the database system of the target device), so that both the front-end container and the host file system outside the container generate a mount point (i.e., the resource backup directory). In this way, the mount point in the front-end container is associated with the mount point of the host file system outside the container, and any modification of the content in the mount point by either party, whether inside the front-end container or on the host file system outside the container, will be synchronized to the other party. It should be noted that the resource backup directory in the newly deployed front-end container is empty, and if the resource backup directory already exists in the host file system outside the container, a mapping relationship between the resource backup directory in the front-end container and the resource backup directory in the host file system outside the container can be established. Optionally, the mounting method of the resource file directory can be adaptively set according to those skilled in the art.

[0035] S120: Periodically back up the static resource data in the static resource data directory of the front-end container, and store the backed-up static resource data in the file system of the target device.

[0036] Specifically, for a newly deployed front-end container, the front-end container only contains the latest version of static resource data for page display. In the front-end container, the static resource data directory can be used to store static resource data. The static resource data directory is the location of the static resources of the page that the browser actually accesses. The static resource data in the static resource data directory can be periodically backed up and the backed-up static resource data can be stored in the file system of the target device. Optionally, the backup period of static resource data can be adaptively set according to those skilled in the art.

[0037] S130: Based on the backup time information, clean up the static resource data backed up in the file system of the target device to generate a target backup file.

[0038] Specifically, since the static resource data in the front-end container needs to be backed up periodically in the file system of the target device, and in the embodiment of the present invention, only the latest backed-up static resource data is meaningful, it is necessary to clean up the backup data in the file system of the target device according to the backup time information of the backup data in the file system of the target device, and only retain the static resource data within the current backup cycle to generate the target backup file.

[0039] S140: Store the target backup file in the resource backup directory, and copy the static resource data in the resource backup directory to the static resource data directory in the newly deployed front-end container.

[0040] In an embodiment of the present invention, the target backup file can be stored in the resource backup directory in the file system of the target device. Since there is already a mapping relationship between the resource backup directory in the front-end container and the system resource backup directory in the file system of the target device, the data in the resource backup directory in the file system of the target device will be synchronously updated to the resource backup directory of the front-end container. It should be noted that when the front-end container is deployed on the target device for the first time, only the static resource data in the front-end container will be backed up. When the front-end container is deployed from the target device for the second time, the static resource data directory in the front-end container will be updated according to the static resource data backed up in the resource backup directory, and the static resource data backed up in the resource backup directory will be copied to the static resource data directory in the front-end container. At this time, the front-end container deployed for the second time not only stores the latest version of the static resource data, but also stores the historical static resource data in the historical front-end container.

[0041] Optionally, the file identifier of the target backup file can be the version number of the front-end container to which the backed-up static resource data belongs. Only when the file identifier of the target backup file is inconsistent with the version number of the current front-end container, the target backup file in the resource backup directory will be copied to the static resource data directory in the newly deployed front-end container. It should be noted that the above-mentioned version number consistency judgment step will be performed every time a new front-end container is deployed.

[0042] Optionally, in an embodiment of the present invention, the target backup file is stored in a resource backup directory, including: when the resource backup directory is empty, all target backup files are copied to the resource backup directory; when the resource backup directory is not empty, incrementally copying the target backup files in the resource backup directory.

[0043] Specifically, if the resource backup directory is empty, it means that the static resource data is backed up for the first time. At this time, the target backup file can be stored in the resource backup directory as a whole. If the resource backup directory is not empty, it means that it is not the first time to back up the static resource data. In this case, according to the static resource data in the resource backup directory, only the incremental data of the resource backup directory is copied from the target backup file and stored in the resource backup directory.

[0044] By performing full or incremental storage on the target backup file, the validity of the static resource data stored in the resource backup directory is ensured, and the data quality of the backed-up static resource data is improved.

[0045] The technical solution of the embodiment of the present invention sets a shared resource backup directory in the file system of the front-end container and the target device, and uses the file system of the target device to periodically back up the static resource data in the front-end container and store it in the resource backup directory, and copies the files in the resource backup directory to the newly deployed front-end container, so that the front-end container not only stores the latest deployed front-end resource data, but also stores all static resource data within the backup cycle, avoiding the problem of inconsistent life cycle management of the same file by the browser and the front-end container, ensuring the stability of the browser during page jumps, and improving the user experience.

[0046] Embodiment 2

[0047] Figure 2 This is a flowchart of a method for storing browser page data provided in the second embodiment of the present invention. This embodiment further refines the above embodiment and provides specific steps for periodically backing up the static resource data in the static resource data directory of the front-end container and storing the backed-up static resource data in the file system of the target device. It should be noted that for the undetailed parts of the embodiment of the present invention, please refer to the relevant descriptions of other embodiments, which will not be repeated here. Figure 2 As shown, the method includes:

[0048] S210: Set a resource backup directory for the front-end container, and synchronously mount the resource backup directory to the file system of the target device.

[0049] S220: During the backup cycle, a temporary backup folder identified by a version number is created in the file system of the target device.

[0050] S230: Copy all static resource data in the static resource data directory of the front-end container to a temporary backup folder, and generate a backup index for the temporary backup folder.

[0051] Among them, the backup index can be a key-value pair index; the key position of the key-value pair index can be used to represent the data backup time and the version number of the data container; the value position of the key-value pair index can be in data form, used to save the static resource file name list backed up in the current backup cycle.

[0052] Specifically, during the current backup cycle, a temporary backup folder identified by the version number of the currently requested container can be created in the file system of the target device, and all static resource data in the static resource data directory in the current front-end container can be copied to the temporary backup folder and stored in the form of sub-files, and a backup index can be established for the sub-files.

[0053] S240: Based on the backup time information, clean up the static resource data backed up in the file system of the target device to generate a target backup file.

[0054] Optionally, based on the backup time information, the static resource data backed up in the file system of the target device is cleaned up to generate a target backup file, including: after completing the data backup of the static resource data in the static resource data directory of the front-end container in the file system of the target device, the backup data is cleaned up in the file system of the target device according to the backup time information of the current backup cycle and the data version of the backed up data in the current backup cycle.

[0055] The data version of the backup data may refer to the version number of the front-end container to which the backup data belongs. Optionally, the backup time information and the data version of the backup data may be determined by the backup index of the sub-file generated in the current backup cycle in the temporary backup folder stored in the file system of the target device.

[0056] Optionally, the data cleaning process may include: screening out backup data having different backup time information from the current backup cycle and / or data versions of the backup data in the current backup cycle according to the backup index of the backup data, and deleting the backup data.

[0057] In an embodiment of the present invention, since the static resource data of the front-end container will be backed up periodically, there will be many historical versions of static resource data in the file system of the target device; therefore, according to the backup time of the static resource data indicated by the backup index of the sub-file storing the static resource data and / or the version number of the data container, the historical sub-files that are not in the current backup cycle and / or the historical sub-files with different version numbers from the current front-end container can be screened out. After data cleaning, the file system of the target device only stores the static resource data backed up in the current backup cycle.

[0058] By cleaning the backup data in the file system of the target device, only the backup data within the current backup cycle is retained and the useless historical backup data is deleted, thus reducing the memory usage of the backup data.

[0059] S250: Store the target backup file in the resource backup directory, and copy the static resource data in the resource backup directory to the static resource data directory in the newly deployed front-end container.

[0060] The technical solution of the embodiment of the present invention, by first storing the static resource data backed up from the front-end container in a temporary backup folder and generating a backup index for the backup folder, facilitates the subsequent data cleaning of the backup data of the temporary backup folder based on the backup index, and only retains the backup data within the current backup cycle, thereby ensuring the validity of the backup data and improving the data quality of the backup data.

[0061] Embodiment 3

[0062] Figure 3 This is a schematic diagram of the structure of a storage device for browser page data provided by Embodiment 3 of the present invention. Figure 3 As shown, the device comprises:

[0063] The directory mounting module 310 is used to set a resource backup directory for the front-end container and synchronously mount the resource backup directory to the file system of the target device; wherein the resource backup directory is used to back up the static resource data displayed by the browser page in the current front-end container; the target device refers to the back-end server device running the browser;

[0064] The file backup module 320 is used to periodically back up the static resource data in the static resource data directory of the front-end container and store the backed-up static resource data in the file system of the target device;

[0065] The backup cleaning module 330 is used to clean up the static resource data backed up in the file system of the target device based on the backup time information to generate a target backup file;

[0066] The backup deployment module 340 is used to store the target backup file in a resource backup directory, and copy the static resource data in the resource backup directory to the static resource data directory in the newly deployed front-end container.

[0067] The technical solution of the embodiment of the present invention sets a shared resource backup directory in the file system of the front-end container and the target device, and uses the file system of the target device to periodically back up the static resource data in the front-end container and store it in the resource backup directory, and copies the files in the resource backup directory to the newly deployed front-end container, so that the front-end container not only stores the latest deployed front-end resource data, but also stores all static resource data within the backup cycle, avoiding the problem of inconsistent life cycle management of the same file by the browser and the front-end container, ensuring the stability of the browser during page jumps, and improving the user experience.

[0068] Optionally, the file backup module 320 includes:

[0069] A temporary folder unit is used to create a temporary backup folder identified by a version number in the file system of the target device during the backup cycle;

[0070] The backup unit is used to copy all static resource data in the static resource data directory of the front-end container to a temporary backup folder and generate a backup index for the temporary backup folder.

[0071] Optionally, the backup index is a key-value pair index; the key position of the key-value pair index is used to represent the backup time of the data and the version number of the data container; the value position of the key-value pair index is in data form, which is used to save the list of static resource file names backed up in the current backup cycle.

[0072] Optionally, the backup cleaning module 330 includes:

[0073] The data cleaning unit is used to clean the backup data of the file system of the target device according to the backup time information of the current backup cycle and the data version of the backed up data in the current backup cycle after completing the data backup of the static resource data in the static resource data directory of the front-end container in the file system of the target device.

[0074] Optionally, the data cleaning unit may be specifically configured to: filter out backup data having different backup time information from the current backup cycle and / or data versions of the backup data in the current backup cycle according to the backup index of the backup data, and delete the backup data.

[0075] Optionally, the backup deployment module 340 includes:

[0076] The backup deployment unit is used to: when the resource backup directory is empty, copy all target backup files to the resource backup directory; when the resource backup directory is not empty, make incremental copies of the target backup files in the resource backup directory.

[0077] The storage device for browser page data provided in the embodiment of the present invention can execute the storage method for browser page data provided in any embodiment of the present invention, and has the functional modules and beneficial effects corresponding to the execution method.

[0078] Embodiment 4

[0079] Figure 4A schematic diagram of an electronic device 410 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0080] like Figure 4 As shown, the electronic device 410 includes at least one processor 411, and a memory connected to the at least one processor 411 in communication, such as a read-only memory (ROM) 412, a random access memory (RAM) 413, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 411 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 412 or the computer program loaded from the storage unit 418 to the random access memory (RAM) 413. In the RAM 413, various programs and data required for the operation of the electronic device 410 can also be stored. The processor 411, the ROM 412, and the RAM 413 are connected to each other via a bus 414. An input / output (I / O) interface 415 is also connected to the bus 414.

[0081] Multiple components in the electronic device 410 are connected to the I / O interface 415, including: an input unit 416, such as a keyboard, a mouse, etc.; an output unit 417, such as various types of displays, speakers, etc.; a storage unit 418, such as a disk, an optical disk, etc.; and a communication unit 419, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 419 allows the electronic device 410 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0082] Processor 411 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of processor 411 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. Processor 411 performs the various methods and processes described above, such as a method for storing browser page data.

[0083] In some embodiments, the storage method of browser page data can be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as storage unit 418. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 410 via ROM 412 and / or communication unit 419. When the computer program is loaded into RAM 413 and executed by processor 411, one or more steps of the storage method of browser page data described above can be performed. Alternatively, in other embodiments, processor 411 can be configured to execute the storage method of browser page data by any other appropriate means (e.g., by means of firmware).

[0084] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0085] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0086] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0087] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0088] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0089] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0090] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0091] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for storing browser page data, characterized in that: include: A resource backup directory is set for the front-end container, and the resource backup directory is synchronously mounted to the file system of the target device; wherein the resource backup directory is used to back up the static resource data displayed by the browser page in the current front-end container; the target device refers to the back-end server device running the browser; Periodically back up the static resource data in the static resource data directory of the front-end container, and store the backed-up static resource data in the file system of the target device; Based on the backup time information, the static resource data backed up in the file system of the target device is cleaned up to generate a target backup file; The target backup file is stored in a resource backup directory, and the static resource data in the resource backup directory is copied to the static resource data directory in the newly deployed front-end container.

2. The method according to claim 1, characterized in that Periodically back up the static resource data in the static resource data directory of the front-end container, and store the backed-up static resource data in the file system of the target device, including: During the backup cycle, a temporary backup folder identified by a version number is created in the file system of the target device; Copy all static resource data in the static resource data directory of the front-end container to a temporary backup folder, and generate a backup index for the temporary backup folder.

3. The method according to claim 2, characterized in that The backup index is a key-value pair index; the key position of the key-value pair index is used to represent the data backup time and the version number of the data container; the value position of the key-value pair index is in data form, which is used to save the static resource file name list backed up in the current backup cycle.

4. The method according to claim 1, characterized in that: Based on the backup time information, clean up the static resource data backed up in the file system of the target device to generate a target backup file, including: After completing the data backup of the static resource data in the static resource data directory of the front-end container in the file system of the target device, the backup data is cleaned for the file system of the target device according to the backup time information of the current backup cycle and the data version of the backed up data in the current backup cycle.

5. The method according to claim 4, characterized in that The data cleaning process includes: According to the backup index of the backup data, the backup data having different backup time information from the current backup cycle and / or data version of the backup data in the current backup cycle is screened out and deleted.

6. The method according to claim 1, characterized in that Storing the target backup file in the resource backup directory includes: If the resource backup directory is empty, copy all target backup files to the resource backup directory; When the resource backup directory is not empty, an incremental copy of the target backup file is performed in the resource backup directory.

7. A storage device for browser page data, characterized in that: include: A directory mounting module is used to set a resource backup directory for the front-end container and synchronously mount the resource backup directory to the file system of the target device; wherein the resource backup directory is used to back up the static resource data displayed by the browser page in the current front-end container; the target device refers to the back-end server device running the browser; A file backup module, used to periodically back up the static resource data in the static resource data directory of the front-end container, and store the backed-up static resource data in the file system of the target device; A backup cleaning module is used to clean up the static resource data backed up in the file system of the target device based on the backup time information to generate a target backup file; The backup deployment module is used to store the target backup file in a resource backup directory, and copy the static resource data in the resource backup directory to the static resource data directory in the newly deployed front-end container.

8. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the browser page data storage method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the browser page data storage method according to any one of claims 1 to 6 when executed.

10. A computer program product, characterized in that The invention comprises a computer program, which implements the method for storing browser page data according to any one of claims 1 to 6 when executed by a processor.

Images