CN117632223A - Configuration file synchronization methods and related equipment - Google Patents

Abstract

The application provides a configuration file synchronization method and related equipment, wherein the method comprises the following steps: acquiring a first default configuration file of an original operating system and a second default configuration file of a target operating system, and generating a configuration description file; acquiring a configuration file of the electronic equipment under an original operating system; generating configuration difference information according to the first default configuration file, the second default configuration file, the configuration file and the configuration description file of the electronic equipment under the original operating system; generating a target configuration file according to the second default configuration file, the configuration description file and the configuration difference information; and synchronizing the configuration file of the electronic equipment under the target operating system according to the target configuration file. The method improves the efficiency of configuration file synchronization.

Description

Configuration file synchronization methods and related equipment

Technical field

The present application relates to computer software, and in particular, to a configuration file synchronization method and related equipment.

Background technique

When the operating system of an electronic device is changed (for example, the operating system is replaced or upgraded), the software in the electronic device needs to be redeployed. When redeploying software, the software configuration files need to be synchronized. The current configuration file synchronization is mostly implemented at the business layer, which is highly targeted. Different software has its own synchronization method, which is not universal and the synchronization efficiency is low.

Contents of the invention

Embodiments of the present application provide a configuration file synchronization method and related equipment, which can improve the efficiency of configuration file synchronization.

A first aspect of this application discloses a configuration file synchronization method. The method includes: obtaining the first default configuration file of the original operating system and the second default configuration file of the target operating system, and generating a configuration description file. The configuration description file includes a first default configuration file. Configuration description information of the first default configuration file and the second default configuration file; obtain the configuration file of the electronic device under the original operating system; according to the first default configuration file, the second default configuration file, the configuration file and configuration of the electronic device under the original operating system Description file, generates configuration difference information, the configuration difference information describes the differences between the first default configuration file and the second default configuration file, the configuration file of the electronic device under the original operating system, and whether the differences are synchronized; according to the second default configuration file, Configure the description file and configuration difference information to generate a target configuration file; synchronize the configuration file of the electronic device under the target operating system according to the target configuration file.

According to the configuration file synchronization method provided by the embodiment of the present application, when the operating system is changed (from the original operating system to the target operating system), the configuration file can be synchronized, thereby improving the efficiency of software redeployment. This configuration file synchronization method supports the identification of configuration files of various software under the operating system, does not require specific identification of the software, and is versatile for different software. This configuration file synchronization method can analyze the configuration files that have changed under the original operating system, without the need for manual investigation, reducing the workload and preventing leakage of analysis. This configuration file synchronization method can synchronize configurations in batches, improve configuration synchronization efficiency, and reduce the probability of manual synchronization configuration errors.

In some optional implementations, obtaining the first default configuration file of the original operating system and the second default configuration file of the target operating system, and generating the configuration description file includes: obtaining the first full software package of the original operating system and the target operating system. the second full software package; decompress the first full software package and the second full software package; search for the first default configuration file from the file decompressed by the first full software package, and decompress the second full software package Search the second default configuration file in the obtained file; write the configuration description information corresponding to the first default configuration file and the second default configuration file into the configuration description file.

According to the first full software package of the original operating system and the second full software package of the target operating system, the first default configuration file of the original operating system and the second default configuration file of the target operating system can be obtained. For the first default configuration file and The second default configuration file of the target operating system is analyzed to obtain the configuration description file.

In some optional implementations, searching for the first default configuration file from the files decompressed by the first full software package includes: searching for text files from the files decompressed by the first full software package; according to the preset file type Find the first default configuration file from a text file.

Search the text file from the file obtained by decompressing the first full software package, and search the first default configuration file from the text file according to the preset file type, so that the first default configuration file can be quickly found.

In some optional implementations, the method further includes: packaging the first default configuration file and the second default configuration file into a resource file.

Packing the first default configuration file and the second default configuration file into resource files can facilitate configuration file synchronization of the first default configuration file and the second default configuration file for different electronic devices.

In some optional implementations, generating configuration difference information based on the first default configuration file, the second default configuration file, the configuration file of the electronic device under the original operating system, and the configuration description file includes: comparing the first default configuration file according to the configuration description file. The first difference is obtained between the configuration file and the second default configuration file; the first default configuration file is compared with the configuration file of the electronic device under the original operating system according to the configuration description file, and the second difference is obtained; based on the first difference and the second difference, a generated Configuration difference information.

The configuration difference information describes the differences between the first default configuration file and the second default configuration file, the configuration files of the electronic device under the original operating system, and whether the differences are synchronized, by comparing the first default configuration file with the second default configuration file, and Configuration difference information can be obtained by comparing the first default configuration file with the configuration file of the electronic device under the original operating system.

In some optional implementations, the method further includes: generating a configuration file synchronization script based on the second default configuration file, the configuration description file, and the configuration difference information.

Based on the configuration file synchronization script, configuration files can be synchronized quickly.

In some optional implementations, generating the target configuration file and the configuration file synchronization script based on the second default configuration file, the configuration description file, and the configuration difference information include: reading the configuration difference information, the configuration description file, and the second default configuration file. ; For each difference item in the configuration difference information: if the difference item represents deletion of the configuration file, generate a deletion script; if the difference item represents a new configuration file, copy the newly added configuration file and generate a copy script; if the difference item represents a new addition , modify or delete configuration items, modify the second default configuration file according to the configuration description file, and generate a copy script.

Perform different processing according to different situations of the differences described in the configuration difference information, thereby obtaining the target configuration file and the configuration file synchronization script.

In some optional implementations, the configuration description information includes configuration file group, configuration file path, configuration file type, configuration file parsing rules, and configuration file synchronization rules.

In some optional implementations, the configuration difference information includes configuration file path, original operating system, target operating system, processor architecture, configuration file group, first default configuration value, second default configuration value, original configuration value, Whether there is a first difference, whether there is a second difference, and whether the differences are synchronized.

A second aspect of the present application discloses a computer-readable storage medium, which includes computer instructions. When the computer instructions are run on an electronic device, the electronic device causes the electronic device to execute the configuration file synchronization method as described in the first aspect.

A third aspect of this application discloses an electronic device. The electronic device includes a processor and a memory. The memory is used to store instructions. The processor is used to call instructions in the memory to cause the electronic device to execute Configuration file synchronization method as described in the first aspect.

The fourth aspect of this application discloses a chip system, which is applied to electronic equipment; the chip system includes an interface circuit and a processor; the interface circuit and the processor are interconnected through lines; the interface circuit is used to receive signals from the memory of the electronic equipment, and sends a signal to the processor, the signal includes a computer instruction stored in the memory; when the processor executes the computer instruction, the chip system executes the configuration file synchronization method as described in the first aspect.

It should be understood that the computer-readable storage medium of the second aspect, the electronic device of the third aspect and the chip system of the fourth aspect provided above all correspond to the method of the first aspect. Therefore, the beneficial effects they can achieve can be Refer to the beneficial effects of the corresponding methods provided above, which will not be described again here.

Description of drawings

Figure 1 is a schematic diagram of an application scenario of the configuration file synchronization method provided by the embodiment of the present application.

Figures 2 and 3 are flow charts of the configuration file synchronization method provided by the embodiment of the present application.

Figure 4 is a detailed flow chart of obtaining a configuration file provided by an embodiment of the present application.

Figure 5 is a schematic diagram of multiple configuration files provided by this embodiment of the application.

Figure 6 is a detailed flow chart for generating configuration difference information based on configuration files provided by an embodiment of the present application.

Figure 7 is a schematic diagram of configuration difference information provided by an embodiment of the present application.

Figure 8 is a detailed flow chart for generating a target configuration file and a configuration file synchronization script provided by an embodiment of the present application.

Figure 9 is a schematic diagram of a target configuration file and a configuration file synchronization script provided by an embodiment of the present application.

Figure 10 is a schematic diagram of structured storage of configuration file data provided by an embodiment of the present application.

Figure 11 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

Detailed ways

To facilitate understanding, some descriptions of concepts related to the embodiments of the present application are exemplarily provided for reference.

It should be noted that “at least one” in this application refers to one or more, and “multiple” refers to two or more than two. "And/or" describes the association of associated objects, indicating that there can be three relationships. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B Can be singular or plural. The terms "first", "second", "third", "fourth", etc. (if present) in the description, claims and drawings of this application are used to distinguish similar objects, rather than to Describe a specific order or sequence.

In order to better understand the configuration file synchronization method and related equipment provided by the embodiments of the present application, the application scenarios of the configuration file synchronization method of the present application are first described below.

Figure 1 is a schematic diagram of an application scenario of the configuration file synchronization method provided by the embodiment of the present application.

As shown in Figure 1, the configuration file synchronization method provided by the embodiment of the present application is applied to the electronic device 10. The electronic device 10 includes an operating system 11 and at least one piece of software 12 (only one is shown in the figure). Software 12 includes at least one configuration file 13 . Configuration file 13 provides information required for software 12 to operate. According to the configuration file synchronization method provided by the embodiment of the present application, when the operating system 11 is changed (from the original operating system to the target operating system), the configuration file 13 can be synchronized, thereby improving the efficiency of redeploying the software 12.

Changing the operating system 11 may be to replace the operating system. For example, the original operating system is CentOS 7.6 and the target operating system is openEuler 22.03. Changing the operating system 11 can also mean upgrading the operating system. For example, the original operating system is openEuler 21.03 and the target operating system is openEuler 22.03, or the original operating system is CentOS 6.8 and the target operating system is CentOS 7.6.

The electronic device 10 may be a tablet computer, a desktop computer, a notebook, a cloud server, etc.

Figures 2 and 3 are flow charts of the configuration file synchronization method provided by the embodiment of the present application. The methods shown in Figures 2 and 3 are applied to electronic devices (such as the electronic device 10 in Figure 1). Among them, Figure 2 focuses on describing the data processed or generated in each step, and Figure 3 focuses on describing the specific content of each step. In order to facilitate a clear and complete description of the detailed process of the configuration file synchronization method, the configuration file synchronization method provided by the embodiment of the present application will be described below with reference to FIG. 2 and FIG. 3 .

As shown in Figures 2 and 3, the configuration file synchronization method provided by the embodiment of this application specifically includes:

201. Obtain the default configuration file of the original operating system (for the convenience of distinction, hereinafter referred to as the "first default configuration file") and the default configuration file of the target operating system (for the convenience of the distinction, hereinafter referred to as the "second default configuration file") , generate the configuration description file.

The original operating system may be the operating system of the electronic device before the operating system is changed. The target operating system is the operating system of the electronic device after the operating system is changed.

The first default configuration file is the configuration file corresponding to the software supported by the original operating system. The second default configuration file is the configuration file corresponding to the software supported by the target operating system. You can obtain the full software package of the original operating system (for the convenience of distinction, hereinafter referred to as the "first full software package") and the full software package of the target operating system (for the convenience of distinction, hereinafter referred to as the "second full software package"), The first default configuration file is obtained according to the first full software package, and the second default configuration file is obtained according to the second full software package, and a configuration description file is generated (see 201 in Figure 2). In addition, in other embodiments, the pre-stored first default configuration file and second default configuration file may also be obtained directly from the storage device.

In some embodiments, the first default profile and the second default profile may be different for different processor architectures. For example, for X86 and ARM (for example, Advanced RISC Machine, Advanced Reduced Instruction Set Machine, where RISC is Reduced Instruction Set Computer) architectures, the first default configuration file and the second default configuration file are different. In order to achieve configuration file synchronization of the electronic device, it is necessary to obtain the first default configuration file and the second default configuration file according to the processor architecture of the electronic device, that is, to obtain the first default configuration file and the second default configuration file corresponding to the processor architecture of the electronic device. configuration file.

The configuration description file includes configuration description information of the first default configuration file and the second default configuration file. When generating a configuration description file, each configuration file pair is obtained, and a set of configuration description information is generated for each configuration file pair. Each profile pair includes a first default profile and a corresponding second default profile. For example, under the original operating system, software A includes the configuration file aa.conf. Under the target operating system, software A includes the configuration file aa'.conf corresponding to aa.conf. aa.conf and aa'.conf form a configuration file pair. .

In one embodiment of the present application, for user-defined configuration files, configuration description information corresponding to the customized configuration files can be added to the configuration description file, thereby supporting batch synchronization of customized configuration files.

In one embodiment of the present application, the configuration description information may include configuration file group, configuration file path, configuration file type, configuration file parsing rules, and configuration file synchronization rules.

The configuration file group indicates the software to which the configuration file belongs, for example, software A.

The configuration file path is used to describe the installation path of the configuration file pair. In the configuration file pair, if the installation paths of the first default configuration file and the corresponding second default configuration file are the same, the configuration file path may include an installation path (i.e., the installation path of the first default configuration file or the corresponding second default configuration file ), may also include two identical installation paths (ie, the installation paths of the first default configuration file and the corresponding second default configuration file). If the installation paths of the first default configuration file and the corresponding second default configuration file are different, the configuration file path includes two installation paths, which are the installation path of the first default configuration file and the installation path of the corresponding second default configuration file.

The configuration file type is used to describe the file type of the configuration file pair, such as .xml, .json, etc.

Configuration file parsing rules are used to define how to parse configuration items in configuration file pairs. If the names of the configuration items in the first default configuration file and the corresponding configuration items in the corresponding second default configuration file are different, the configuration file parsing rules define the names of the configuration items in the first default configuration file and the corresponding second default configuration file. The mapping relationship of the corresponding configuration items. For example, in the first default configuration file, the configuration item is a, in the corresponding second default configuration file, the corresponding configuration item is aa, and the configuration file parsing rules define the mapping relationship between a and aa.

Configuration file synchronization rules are used to define how to synchronize configuration items in a configuration file pair. For example, in the first default configuration file, a=b, in the corresponding second default configuration file, the corresponding configuration item is aa, and the configuration file parsing rules define how to synchronize aa, that is, how to assign a value to b.

The specific process of obtaining the first default configuration file and the second default configuration file and generating the configuration description file is described in Figure 4.

202. Obtain the configuration file of the electronic device under the original operating system.

The configuration file of the electronic device under the original operating system is the configuration file corresponding to the software installed on the electronic device under the original operating system, and is the configuration file actually included in the electronic device under the original operating system.

The electronic device can query the software installed on the electronic device under the original operating system, and obtain the configuration file of the electronic device under the original operating system based on the software installed on the electronic device under the original operating system.

The configuration file of the electronic device under the original operating system and the software corresponding to the first default configuration file can be the same. For example, the software corresponding to the configuration file of the electronic device under the original operating system (that is, the software installed on the electronic device under the original operating system) includes software A, software B, software C, software D, software E, and the software corresponding to the first default configuration file (That is, the software supported by the original operating system) includes software A, software B, software C, software D, and software E.

The configuration file of the electronic device under the original operating system and the software corresponding to the first default configuration file may also be different. The software corresponding to the configuration file of the electronic device under the original operating system includes software A, software B, software C, and software D. The software corresponding to the first default configuration file (that is, the software supported by the original operating system) includes software A, software B, software C. Software D. Software E.

For the same software, the configuration file of the electronic device under the original operating system and the first default configuration file can be the same. For example, for software A, the configuration file and first default configuration file of the electronic device under the original operating system include aa.conf, ab.ini, ac.xml, and the configuration items in aa.conf, ab.ini, ac.xml same.

For the same software, the configuration file of the electronic device under the original operating system and the first default configuration file can also be different (including whether the configuration file of the electronic device under the original operating system is compared with the first default configuration file, new configuration files, deleted configuration file, modification of configuration items in the configuration file, etc.). For example, for software A, the configuration files of the electronic device under the original operating system include aa.conf, ab.ini, and ac.xml, and the first default configuration file includes aa.conf and ab.ini.

The electronic device can query the software installed on the electronic device under the original operating system through a preset command. For example, you can use the "rpm-qa" command to query the software installed on the electronic device under the original operating system and obtain the directory of the software installed on the electronic device under the original operating system.

The electronic device can search for the configuration file from the directory of the software installed under the original operating system to obtain the configuration file of the electronic device under the original operating system.

203. Generate configuration difference information based on the first default configuration file, the second default configuration file, the configuration file of the electronic device under the original operating system, and the configuration description file.

The configuration difference information describes the difference between the first default configuration file and the second default configuration file, the configuration file of the electronic device under the original operating system, and whether to synchronize the differences.

When generating configuration difference information, the first default configuration value can be obtained from the first default configuration file according to the configuration file parsing rules, the second default configuration value can be obtained from the second default configuration file, and the configuration file of the electronic device under the original operating system can be obtained. Get the original configuration value. The electronic device compares the first difference between the second default configuration file and the first default configuration file, compares the second difference between the configuration file of the electronic device under the original operating system and the first default configuration file, and obtains the configuration based on the first difference and the second difference. Difference information.

In one embodiment of the present application, the configuration difference information includes configuration file path, original operating system, target operating system, processor architecture, configuration file group, first default configuration value, second default configuration value, original configuration value, Information such as whether there is a first difference, whether a second difference exists, whether the differences are synchronized, etc. Wherein, the configuration file path is the installation path of the first default configuration file and the second default configuration file.

When generating configuration difference information, a setting interface for the configuration difference information can be displayed. The generated configuration difference information is displayed on the setting interface, and the user can set the configuration difference information through the setting interface.

The generated configuration difference information is described in Figure 5 according to the configuration file, the first default configuration file, and the second default configuration file of the electronic device under the original operating system.

204. Generate a target configuration file and a configuration file synchronization script based on the configuration description file, configuration difference information and the second default configuration file.

A script is an executable file written in a certain format using a specific descriptive language. The configuration file synchronization script is a script used to synchronize configuration files.

After the electronic device generates the target configuration file and the configuration file synchronization script, the target configuration file and the configuration file synchronization script are copied to a preset location for configuration file synchronization after the electronic device changes the operating system and reinstalls the software. The default location can be other electronic devices, the cloud, etc.

For the specific process of generating the target configuration file and the configuration file synchronization script based on the configuration description file, configuration difference information and the second default configuration file, please refer to the detailed description in Figure 7 below.

205. Synchronize the configuration file of the electronic device under the target operating system according to the target configuration file and the configuration file synchronization script.

After the electronic device changes from the original operating system to the target operating system, the electronic device executes the configuration file synchronization script to synchronize the configuration file of the electronic device under the target operating system according to the target configuration file.

By executing the configuration file synchronization script to synchronize the configuration files of the electronic device under the target operating system, the efficiency of configuration file synchronization can be improved.

In other embodiments of the present application, the electronic device may generate a target configuration file without generating a configuration file synchronization script, and synchronize the configuration file of the electronic device under the target operating system according to the target configuration file.

According to the configuration file synchronization method provided by the embodiment of the present application, when the operating system is changed (from the original operating system to the target operating system), the configuration file can be synchronized, thereby improving the efficiency of software redeployment. This configuration file synchronization method supports the identification of configuration files of various software under the operating system, does not require specific identification of the software, and is versatile for different software. This configuration file synchronization method can analyze the configuration files that have changed under the original operating system, without the need for manual investigation, reducing the workload and preventing leakage of analysis. This configuration file synchronization method can synchronize configurations in batches, improve configuration synchronization efficiency, and reduce the probability of manual synchronization configuration errors.

In the case where the electronic device includes multiple operating systems, the configuration files of each operating system can be synchronized separately according to the configuration file synchronization method provided by the embodiments of the present application.

Figure 4 is a detailed flow chart of obtaining a configuration file provided by an embodiment of the present application. Specifically, FIG. 4 is a detailed flow chart of step 201 in FIGS. 2 and 3 .

401. Obtain the first full software package of the original operating system and the second full software package of the target operating system.

The first full software package of the original operating system is for all software packages provided by the original operating system, and the second full software package of the target operating system is for all software packages provided by the target operating system.

The electronic device can obtain the first full software package and the second full software package through preset commands.

The electronic device can obtain the first full software package and the second full software package from the official websites of the original operating system and the target operating system respectively.

Both the first full-scale software package and the second full-scale software package include multiple software packages. Each software package corresponds to a piece of software.

The software corresponding to the first full software package and the second full software package may be the same. For example, both the first full software package and the second full software package include software packages of software A, software B, software C, software D, and software E.

The software corresponding to the first full-scale software package and the second full-scale software package may also be different. For example, the first full software package includes software packages of software A, software B, software C, software D, and software E, and the second full software package includes software A, software B, software C, software D, software E, software F, Software package for software G.

402. Decompress the first full software package and the second full software package.

Decompressing the first full software package and the second full software package includes decompressing each of the first full software package and the second full software package.

For example, the first full-scale software package and the second full-scale software package both include software packages of software A, software B, software C, software D, and software E. For software A, software B, software C, software in the first full-scale software package, D. The software package of software E and the software packages of software A, software B, software C, software D and software E in the second full software package are decompressed respectively.

403. Search for the first default configuration file from the file decompressed by the first full software package, and search for the second default configuration file from the file decompressed by the second full software package.

You can find the configuration file from the decompressed file based on its file type. For example, configuration files can include .ini, .json, .xml, .yaml, .list, .kv and other types.

You can search for text files from the decompressed files and search for configuration files from the found text files. Searching for text files from decompressed files and searching for configuration files from the found text files can improve the efficiency of configuration file search.

404. Write the configuration description information corresponding to the first default configuration file and the second default configuration file into the configuration description file, and copy the first default configuration file and the second default configuration file to the specified directory.

In one embodiment of the present application, the configuration description information may include configuration file group, configuration file path, configuration file type, configuration file parsing rules, and configuration file synchronization rules.

This application does not limit the format of the configuration description file, for example, it can be a .json file, .xml file, etc.

405. After the first full software package and the second full software package are processed, obtain the first default configuration file and the second default configuration file from the specified directory, and package the first default configuration file and the second default configuration file into resource files. .

Obtaining the first default configuration file and the second default configuration file and generating the configuration description file are the preprocessing stages of configuration file synchronization. This step can be performed on the electronic device that requires configuration file synchronization, or can be performed on other devices. For example, it can be executed on a server. The server can obtain the corresponding first default configuration file and the second default configuration file for different processor architectures, different original operating systems and target operating systems, generate corresponding configuration description files, and be able to cope with Implement configuration file synchronization in different situations.

Figure 5 is a schematic diagram of multiple configuration files provided by this embodiment of the application. Specifically, FIG. 5 is a schematic diagram of step 201 in FIG. 2 and FIG. 3 .

As shown in Figure 5, the original operating system and the target operating system include software A, B, C..., the configuration file of software A includes aa.conf, ab.ini, ac.xml, and the configuration file of software B includes ba.conf, bb.kv, bc.json, the configuration files of software C include ca.xml, cb.ini, cc.kv. Obtain the default configuration files (the first default configuration file and the second default configuration file) from the files of software A, B, C..., and generate a configuration description file.

In Figure 5, the configuration description information in the configuration description file includes the configuration file group, configuration file path, configuration file type, configuration file parsing rules, and configuration file synchronization rules.

Figure 6 is a detailed flow chart for generating configuration difference information based on configuration files provided by an embodiment of the present application. Specifically, Figure 6 is a detailed flow chart of 203 in Figures 2 and 3.

601. Compare the first default configuration file and the second default configuration file according to the configuration description file to obtain the first difference.

Comparing the first default configuration file with the second default configuration file may include determining whether there are newly added, deleted, and modified configuration items in the second default configuration file. New, deleted, and modified configuration items in the second default configuration file can be marked.

602. Compare the first default configuration file with the configuration file of the electronic device under the original operating system according to the configuration description file to obtain the second difference.

Comparing the first default configuration file with the configuration file of the electronic device under the original operating system may include determining whether there is a newly added or deleted configuration file in the configuration file of the electronic device under the original operating system, and whether the electronic device has a configuration file under the original operating system. Whether there are new, deleted, or modified configuration items in the configuration file. Configuration files that are added or deleted in the configuration file of the electronic device under the original operating system, and configuration items that are added, deleted, and modified in the configuration file of the electronic device in the original operating system can be marked.

603. Generate configuration difference information based on the first difference and the second difference.

The configuration difference information records the first difference and the second difference, such as newly added, deleted and modified configuration items in the second default configuration file, newly added or deleted configuration files of the electronic device in the original operating system configuration file, the configuration files of the electronic device in the original operating system, etc. New, deleted, and modified configuration items in the configuration file under the operating system.

Figure 7 is a schematic diagram of configuration difference information provided by an embodiment of the present application. Specifically, FIG. 7 is a schematic diagram of 203 in FIGS. 2 and 3 .

As shown in Figure 7, the configuration difference information includes configuration file path, original operating system, target operating system, processor architecture, configuration file group, first default configuration value, second default configuration value, original configuration value, and whether there is a third First difference, whether there is a second difference, and whether to synchronize the differences.

Figure 8 is a detailed flow chart for generating a target configuration file and a configuration file synchronization script provided by an embodiment of the present application. Specifically, FIG. 8 is a detailed flow chart of 204 in FIG. 2 and FIG. 3 .

801, read the configuration difference information, configuration description file and second default configuration file.

802. For each difference item in the configuration difference information, if the difference item indicates deletion of the configuration file, generate a deletion script.

803. If the difference item indicates a new configuration file, copy the new configuration file to obtain the target configuration file and generate a copy script.

804. If the difference item indicates adding, modifying or deleting a configuration item, modify the second default configuration file according to the configuration description file and generate a copy script.

Figure 9 is a schematic diagram of a target configuration file and a configuration file synchronization script provided by an embodiment of the present application. Specifically, FIG. 9 is a schematic diagram of 204 in FIGS. 2 and 3 .

As shown in Figure 9, the target configuration file and the configuration file synchronization script are generated based on the configuration description file, configuration difference information and the second default configuration file.

When obtaining the first default configuration file and the second default configuration file, in addition to packaging the first default configuration file and the second default configuration file, the data in the first default configuration file and the second default configuration file can also be packaged. Structured storage, for example, stores the data in the first default configuration file and the second default configuration file into the configuration database. The configuration database can be SQLite, MySQL or a custom database.

Figure 10 is a schematic diagram of structured storage of configuration file data provided by an embodiment of the present application. Specifically, FIG. 10 is a schematic diagram of structured storage of data in the first default configuration file and the second default configuration file. As shown in Figure 10, the original operating system and the target operating system include software A, B, C..., the configuration file of software A includes aa.conf, ab.ini, ac.xml, and the configuration file of software B includes ba.conf, bb.kv, bc.json, the configuration files of software C include ca.xml, cb.ini, cc.kv. Store the data in the configuration files of software A, B, C... into the configuration database.

FIG. 11 is a schematic structural diagram of an electronic device disclosed in an embodiment of the present application. Optionally, the electronic device 1100 shown in Figure 9 is used to perform the methods shown in Figures 2, 3, 4, 6 and 8.

Electronic device 1100 includes at least one processor 1101, memory 1102, and at least one network interface 1103.

The processor 1101 is, for example, a general-purpose central processing unit (CPU), a network processor (NP), a graphics processing unit (GPU), or a neural-network processing unit (NPU). ), a data processing unit (DPU), a microprocessor, or one or more integrated circuits used to implement the solution of the present application. For example, the processor 1101 includes an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. A PLD is, for example, a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.

The memory 1102 is, for example, a read-only memory (ROM) or other type of static storage device that can store static information and instructions, or a random access memory (random access memory, RAM) or a device that can store information and instructions. Other types of dynamic storage devices, such as electrically erasable programmable read-only memory (EEPROM), compactdisc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be used by Any other media accessed by a computer, but not limited to this. Optionally, the memory 1102 exists independently and is connected to the processor 1101 through an internal connection 1104. Alternatively, memory 1102 and processor 1101 are optionally integrated together.

Network interface 1103 uses any transceiver-like device for communicating with other devices or communications networks. The network interface 1103 includes, for example, at least one of a wired network interface or a wireless network interface. The wired network interface is, for example, an Ethernet interface. The Ethernet interface is, for example, an optical interface, an electrical interface or a combination thereof. The wireless network interface is, for example, a wireless local area networks (WLAN) interface, a cellular network interface or a combination thereof.

In some embodiments, processor 1101 includes one or more CPUs, such as CPU0 and CPU1 as shown in Figure 11.

In some embodiments, electronic device 1100 optionally includes multiple processors, such as processor 1101 and processor 1105 as shown in FIG. 11 . Each of these processors is, for example, a single-core processor (single-CPU) or a multi-core processor (multi-CPU). Processor here optionally refers to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).

In some embodiments, electronic device 1100 also includes internal connections 1104 . The processor 1101, the memory 1102 and at least one network interface 1103 are connected through an internal connection 1104. Internal connections 1104 include pathways that carry information between the components described above. Optionally, internal connection 1104 is a single board or bus. Optionally, the internal connections 1104 are divided into address bus, data bus, control bus, etc.

In some embodiments, the electronic device 1100 also includes an input-output interface 1106 . The input/output interface 1106 is connected to the internal connection 1104.

Optionally, the processor 1101 implements the method in the above embodiment by reading the program code 910 stored in the memory 1102, or the processor 1101 implements the method in the above embodiment by using the internally stored program code. In the case where the processor 1101 implements the method in the above embodiment by reading the program code 910 stored in the memory 1102, the memory 1102 stores the program code that implements the method provided by the embodiment of the present application.

For more details on how the processor 1101 implements the above functions, please refer to the descriptions in the previous method embodiments, which will not be repeated here.

This embodiment also provides a computer storage medium that stores computer instructions. When the computer instructions are run on an electronic device, the electronic device causes the electronic device to execute the above related method steps to implement the configuration file synchronization method in the above embodiment. .

This embodiment also provides a computer program product. When the computer program product is run on an electronic device, it causes the electronic device to perform the above related steps to implement the configuration file synchronization method in the above embodiment.

In addition, embodiments of the present application also provide a device. This device may be a chip, a component or a module. The device may include a connected processor and a memory. The memory is used to store computer execution instructions. When the device is running, The processor can execute computer execution instructions stored in the memory, so that the chip executes the configuration file synchronization method in each of the above method embodiments.

Among them, the electronic equipment, computer storage media, computer program products or chips provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the corresponding methods provided above. The beneficial effects of the method will not be repeated here.

Through the above description of the embodiments, those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In actual applications, the above functions can be allocated as needed. It is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be combined. Either it can be integrated into another device, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, indirect coupling or communication connection of devices or units, which may be in electrical, mechanical or other forms.

The unit described as a separate component may or may not be physically separate. The component shown as a unit may be one physical unit or multiple physical units, that is, it may be located in one place, or it may be distributed to multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application are essentially or contribute to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the software product is stored in a storage medium , including several instructions to cause a device (which can be a microcontroller, a chip, etc.) or a processor to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code. .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be covered by the protection scope of the present application. . Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims (12)

1. A configuration file synchronization method, characterized in that the method includes: Obtain the first default configuration file of the original operating system and the second default configuration file of the target operating system, and generate a configuration description file. The configuration description file includes configuration descriptions of the first default configuration file and the second default configuration file. information; Obtain the configuration file of the electronic device under the original operating system; Configuration difference information is generated according to the first default configuration file, the second default configuration file, the configuration file of the electronic device under the original operating system and the configuration description file, and the configuration difference information describes the Differences between the first default configuration file and the second default configuration file, the configuration file of the electronic device under the original operating system, and whether to synchronize the differences; Generate a target configuration file according to the second default configuration file, the configuration description file and the configuration difference information; Synchronize the configuration file of the electronic device under the target operating system according to the target configuration file. 2. The configuration file synchronization method according to claim 1, wherein said obtaining the first default configuration file of the original operating system and the second default configuration file of the target operating system and generating the configuration description file includes: Obtain the first full software package of the original operating system and the second full software package of the target operating system; Decompress the first full software package and the second full software package; Search for the first default configuration file from the file decompressed by the first full software package, and search for the second default configuration file from the file decompressed by the second full software package; Write configuration description information corresponding to the first default configuration file and the second default configuration file into the configuration description file. 3. The configuration file synchronization method according to claim 2, wherein the search for the first default configuration file from the file obtained by decompressing the first full software package includes: Search for text files from files obtained by decompressing the first full software package; Search the first default configuration file from the text file according to a preset file type. 4. The configuration file synchronization method according to claim 2, characterized in that the method further includes: The first default configuration file and the second default configuration file are packaged into resource files. 5. The configuration file synchronization method according to any one of claims 1 to 4, characterized in that, according to the first default configuration file, the second default configuration file, the electronic device in the The configuration file under the original operating system and the configuration description file generate configuration difference information including: Compare the first default configuration file and the second default configuration file according to the configuration description file to obtain a first difference; Compare the first default configuration file and the configuration file of the electronic device under the original operating system according to the configuration description file to obtain a second difference; The configuration difference information is generated according to the first difference and the second difference. 6. The configuration file synchronization method according to any one of claims 1 to 5, characterized in that the method further includes: A configuration file synchronization script is generated according to the second default configuration file, the configuration description file and the configuration difference information. 7. The configuration file synchronization method according to claim 6, wherein generating the target configuration file and the configuration file synchronization script according to the second default configuration file, the configuration description file and the configuration difference information includes: Read the configuration difference information, the configuration description file and the second default configuration file; For each difference in the configuration difference information: If the difference item indicates deletion of the configuration file, generate a deletion script; If the difference item indicates a new configuration file, copy the new configuration file and generate a copy script; If the difference item represents adding, modifying or deleting a configuration item, modify the second default configuration file according to the configuration description file to generate a copy script. 8. The configuration file synchronization method according to any one of claims 1 to 7, wherein the configuration description information includes configuration file group, configuration file path, configuration file type, configuration file parsing rules and configuration file Synchronization rules. 9. The configuration file synchronization method according to any one of claims 1 to 8, wherein the configuration difference information includes configuration file path, original operating system, target operating system, processor architecture, and configuration file group. , the first default configuration value, the second default configuration value, the original configuration value, whether there is a first difference, whether there is a second difference, and whether to synchronize the differences. 10. A computer-readable storage medium, characterized by comprising computer instructions that, when executed on an electronic device, cause the electronic device to perform the configuration of any one of claims 1 to 9 File synchronization method. 11. An electronic device, characterized in that the electronic device includes a processor and a memory, the memory is used to store instructions, and the processor is used to call instructions in the memory, so that the electronic device executes as The configuration file synchronization method according to any one of claims 1 to 9. 12. A chip system, characterized in that the chip system is applied to electronic equipment; the chip system includes an interface circuit and a processor; the interface circuit and the processor are interconnected through lines; the interface circuit is used to receive signals from the memory of the electronic device, and A signal is sent to the processor, and the signal includes a computer instruction stored in the memory; when the processor executes the computer instruction, the chip system executes the configuration file synchronization method according to any one of claims 1 to 9.