Page file processing method, device, system, electronic device and storage medium

Abstract

The present disclosure relates to a page file processing method, device, system, electronic device and storage medium, and relates to the field of network technology. In the present disclosure, a page file corresponding to at least one business is obtained, and the page file is deployed to a container pre-created by a page management platform. In response to the address configuration instruction sent by the first account, a page access address is configured for the page file to complete the file deployment; the page access addresses of the page files corresponding to different businesses are different. In this way, there is no need to apply for a fixed amount of hardware resources for the business, thereby avoiding resource waste to a certain extent.

Description

Technical Field

[0001] The present disclosure relates to the field of network technology, and in particular to a page file processing method, device, system, electronic device, and storage medium. Background Art

[0002] Currently, a page file is usually created and deployed online to provide users with accessible pages.

[0003] When deploying page files, the related technology requires applying for a fixed amount of hardware resources for each business. Then, a container image is built based on the requested hardware resources, and a container is built based on the container image. Only then can the page files corresponding to the business be deployed. In this approach, because each business occupies a fixed amount of allocated hardware resources by default, this sometimes leads to resource waste. Summary of the Invention

[0004] The present disclosure provides a page file processing method, device, system, electronic device, and storage medium to at least solve the problem of resource waste in related technologies. The technical solutions of the present disclosure are as follows:

[0005] According to a first aspect of an embodiment of the present disclosure, a page file processing method is provided, which is applied to a page management platform. The method includes:

[0006] Obtaining a page file corresponding to at least one business, and deploying the page file to a container pre-created by the page management platform;

[0007] In response to the address configuration instruction sent by the first account, a page access address is configured for the page file to complete file deployment; the page access addresses of the page files corresponding to different businesses are different.

[0008] Optionally, configuring a page access address for the page file in response to the address configuration instruction sent by the first account includes:

[0009] In response to a selection instruction for a candidate page file from the first account, using the candidate page file indicated by the selection instruction as a to-be-configured file; the candidate page file is a page file corresponding to a business to which the first account belongs;

[0010] According to the domain name and access path indicated by the address configuration instruction, a page access address is set for the configuration file to be configured.

[0011] Optionally, different page file directories are pre-associated with paths, and the path associated with the page file directory to which the candidate page file belongs is the same as or partially overlaps with the access path; the paths associated with the page file directories corresponding to different services are different.

[0012] Optionally, before deploying the page file to the container pre-created by the page management platform, the method further includes:

[0013] Creating the container based on a pre-set container image;

[0014] The deploying the page file to the container pre-created by the page management platform includes: deploying the page file in the created container.

[0015] Optionally, the method includes:

[0016] Synchronize the currently deployed page files, the page access addresses of the deployed page files, and the relevant information of the container in which they are located;

[0017] After the page management platform is restarted, the currently deployed page file is redeployed in the container according to the currently deployed page file, the page access address of the deployed page file, and the related information of the container.

[0018] Optionally, obtaining at least one page file corresponding to a business includes:

[0019] Receiving the page file submitted by the preset interface when the second account passes the first verification; the page file is submitted by the second account to the preset interface in a target deployment mode, and the target deployment mode is selected from at least two preset deployment modes;

[0020] Before deploying the page file to the container pre-created by the page management platform, the method also includes: performing a second verification on the preset interface, and if the second verification is passed, executing the operation of deploying the page file to the container pre-created by the page management platform.

[0021] According to a second aspect of an embodiment of the present disclosure, a page file processing method is provided, which is applied to a terminal. The method includes:

[0022] Providing at least one page file corresponding to a business to the page management platform; the page management platform is used to deploy the page file to a container pre-created by the page management platform;

[0023] An address configuration instruction is sent to the page management platform based on the first account; the page management platform is also used to configure a page access address for the page file in response to the address configuration instruction to complete file deployment; the page access addresses of page files corresponding to different businesses are different.

[0024] Optionally, the method further includes:

[0025] Displaying an alternative page file, where the alternative page file is a page file corresponding to the business to which the first account belongs;

[0026] In response to the selection operation of the alternative page file, a selection instruction is sent to the page management platform; the page management platform is also used to use the alternative page file indicated by the selection instruction as the configuration file to be configured, and set the page access address for the configuration file to be configured according to the domain name and access path indicated by the address configuration instruction.

[0027] Optionally, the displaying of the alternative page file includes:

[0028] Display all page files included in the target file directory and / or display the target file directory;

[0029] Different page file directories are pre-associated with paths, and the path associated with the target file directory is the same as or partially overlaps with the access path.

[0030] Optionally, providing at least one page file corresponding to a business to the page management platform includes:

[0031] A page file to be deployed is provided to a preset interface based on a second account; the page file is provided based on a target deployment method selected from at least two preset deployment methods; the preset interface is used to submit the page file to the page management platform when the second account passes the first verification.

[0032] According to a third aspect of an embodiment of the present disclosure, a page file processing device is provided, which is applied to a page management platform. The device includes:

[0033] An acquisition module configured to acquire a page file corresponding to at least one business and deploy the page file to a container pre-created by the page management platform;

[0034] The configuration module is configured to execute the address configuration instruction sent in response to the first account, configure the page access address for the page file to complete the file deployment; the page access address of the page file corresponding to different businesses is different.

[0035] Optionally, the configuration module is specifically configured to execute:

[0036] In response to a selection instruction for a candidate page file from the first account, using the candidate page file indicated by the selection instruction as a to-be-configured file; the candidate page file is a page file corresponding to a business to which the first account belongs;

[0037] According to the domain name and access path indicated by the address configuration instruction, a page access address is set for the configuration file to be configured.

[0038] Optionally, different page file directories are pre-associated with paths, and the path associated with the page file directory to which the candidate page file belongs is the same as or partially overlaps with the access path; the paths associated with the page file directories corresponding to different services are different.

[0039] Optionally, the device further includes:

[0040] A creation module is configured to create the container based on a preset container image;

[0041] The acquisition module is specifically configured to execute: deploying the page file in the created container.

[0042] Optionally, the device further includes:

[0043] A synchronization module is configured to synchronize the currently deployed page files, the page access addresses of the deployed page files, and the related information of the containers in which they are located;

[0044] The deployment module is configured to execute, after the page management platform is restarted, redeploying the currently deployed page file in the container according to the currently deployed page file, the page access address of the deployed page file and the relevant information of the container.

[0045] Optionally, the acquisition module is further configured to execute:

[0046] Receiving the page file submitted by the preset interface when the second account passes the first verification; the page file is submitted by the second account to the preset interface in a target deployment mode, and the target deployment mode is selected from at least two preset deployment modes;

[0047] The device also includes: an execution module, configured to perform a second verification on the preset interface, and if the second verification is passed, execute the operation of deploying the page file to the container pre-created by the page management platform.

[0048] According to a fourth aspect of an embodiment of the present disclosure, a page file processing device is provided, which is applied to a terminal. The device includes:

[0049] A providing module is configured to provide a page file corresponding to at least one business to a page management platform; the page management platform is used to deploy the page file to a container pre-created by the page management platform;

[0050] The first sending module is configured to execute an address configuration instruction to the page management platform based on the first account; the page management platform is also used to respond to the address configuration instruction to configure a page access address for the page file to complete file deployment; the page access addresses of page files corresponding to different businesses are different.

[0051] Optionally, the device further includes:

[0052] a display module configured to display an alternative page file, where the alternative page file is a page file corresponding to the business to which the first account belongs;

[0053] The second sending module is configured to execute a selection instruction to the page management platform in response to the selection operation of the alternative page file; the page management platform is also used to use the alternative page file indicated by the selection instruction as the configuration file to be configured, and set the page access address for the configuration file to be configured according to the domain name and access path indicated by the address configuration instruction.

[0054] Optionally, the display module is specifically configured to execute:

[0055] Display all page files included in the target file directory and / or display the target file directory;

[0056] Different page file directories are pre-associated with paths, and the path associated with the target file directory is the same as or partially overlaps with the access path.

[0057] Optionally, the providing module is specifically configured to execute:

[0058] A page file to be deployed is provided to a preset interface based on a second account; the page file is provided based on a target deployment method selected from at least two preset deployment methods; the preset interface is used to submit the page file to the page management platform when the second account passes the first verification.

[0059] According to a fifth aspect of an embodiment of the present disclosure, a page file processing system is provided, the system including a terminal and a page management platform;

[0060] The terminal is configured to provide the page management platform with at least one page file corresponding to a service;

[0061] The page management platform is used to deploy the page file into a container pre-created by the page management platform;

[0062] The terminal is further configured to send an address configuration instruction to the page management platform based on the first account;

[0063] The page management platform is further configured to configure a page access address for the page file in response to the address configuration instruction to complete file deployment; the page access addresses of the page files corresponding to different services are different.

[0064] According to a sixth aspect of an embodiment of the present disclosure, there is provided an electronic device, including:

[0065] processor;

[0066] a memory for storing instructions executable by the processor;

[0067] The processor is configured to execute the instructions to implement the method as described in any one of the first aspects.

[0068] According to a seventh aspect of an embodiment of the present disclosure, a storage medium is provided. When instructions in the storage medium are executed by a processor of an electronic device, the electronic device executes the method as described in any one of the first aspects.

[0069] According to an eighth aspect of an embodiment of the present disclosure, a computer program product is provided, which includes readable program instructions. When the readable program instructions are executed by a processor of an electronic device, the electronic device executes the method as described in any one of the first aspects.

[0070] The technical solution provided by the embodiment of the present disclosure brings at least the following beneficial effects: In the embodiment of the present disclosure, a page file corresponding to at least one business can be obtained, and the page file can be deployed to a container pre-created by the page management platform. In response to the address configuration instruction sent by the first account, the page access address is configured for the page file to complete the file deployment; the page access addresses of the page files corresponding to different businesses are different. In the embodiment of the present disclosure, the page management platform, as a public service, uniformly provides deployment services for each business, and the page files corresponding to each business can be uniformly deployed to the page management platform. In this way, there is no need to apply for a fixed amount of hardware resources for the business, which can avoid resource waste to a certain extent.

[0071] And you only need to provide the page files that need to be deployed, and the page management platform will directly deploy them based on the pre-created container. In this way, there is no need to build a container image, which can reduce the deployment time and improve deployment efficiency to a certain extent.

[0072] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0073] The accompanying drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute an improper limitation of the present disclosure.

[0074] Figure 1 is a flow chart showing a method for processing a page file according to an exemplary embodiment;

[0075] Figure 2 is a schematic diagram of a directory according to an exemplary embodiment;

[0076] Figure 3 is a deployment diagram according to an exemplary embodiment;

[0077] Figure 4 is a flow chart showing another page file processing method according to an exemplary embodiment;

[0078] Figure 5 is a schematic diagram of the architecture of a page processing platform according to an exemplary embodiment;

[0079] Figure 6 is a block diagram showing a page file processing device according to an exemplary embodiment;

[0080] Figure 7 is a block diagram showing another page file processing device according to an exemplary embodiment;

[0081] Figure 8 is a block diagram showing an apparatus for page file processing according to an exemplary embodiment;

[0082] Figure 9 It is a block diagram showing another apparatus for page file processing according to an exemplary embodiment. DETAILED DESCRIPTION

[0083] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0084] It should be noted that the terms "first," "second," and the like in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the numbers used in this manner are interchangeable where appropriate so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure as detailed in the appended claims.

[0085] Figure 1 This is a flow chart showing a method for processing page files according to an exemplary embodiment. The method can be applied to a page management platform, such as Figure 1 As shown, the method may include:

[0086] Step 101: Obtain a page file corresponding to at least one business, and deploy the page file to a container pre-created by the page management platform.

[0087] In the embodiment of the present disclosure, the page file may be an executable file obtained by converting the source code. Exemplarily, the page file may be a static web page file, the file type of the page file may be html, and the page file may represent a page of an online web page, a page of an online e-book, and so on. That is, the page of an online e-book is implemented based on a web page file. In one implementation, the source code generated in the front-end development may be constructed, that is, the source code may be converted into a browser executable file to obtain a page file. The page file corresponding to a business refers to a page file created to implement the business, wherein the business may be defined in advance according to actual needs. For example, a business may be defined according to the functions to be provided, and the page file created for each business may be used to implement the functions corresponding to the business. Assuming that the function corresponding to business A is the history record display function, the page file corresponding to business A may be used to provide a page for displaying history records.

[0088] The page management platform can be a server cluster, and the deployment operation can also be called a publishing or online operation. The deployment operation specifically refers to the operation of uploading the build product, that is, the page file, to the server. The page management platform in the embodiment of the present disclosure can be used to deploy page files corresponding to each business, and the page management platform can be used to provide page hosting services to multiple businesses. In other words, the page files corresponding to multiple businesses can all be uniformly deployed to the page management platform. By deploying the page file into a container, it is possible to publish the page file to the page management platform in the form of a container. A container engine can be installed in the page management platform to run the page file normally, thereby ensuring that users can access the page normally.

[0089] Step 102: In response to the address configuration instruction sent by the first account, configure a page access address for the page file to complete file deployment; the page access addresses of the page files corresponding to different businesses are different.

[0090] In the disclosed embodiment, the first account may be an account with permission to operate the page file. For example, the first account may be the creator account or collaborator account of the page file. The address configuration instruction may be used to configure routing for the deployed page file, that is, to set a page access address that can be used to access the page file. After configuring routing for the deployed page file, the file deployment operation may be completed.

[0091] During the specific configuration, the page access addresses configured for the page files corresponding to different businesses are different. In this way, while deploying the page files corresponding to multiple businesses on the same platform, conflicts between different businesses can be avoided to a certain extent. Of course, the page access addresses configured for different page files corresponding to the same business can also be different to avoid access conflicts. Of course, the page access address can also be returned to the terminal logged in to the first account to facilitate the user to easily know the configuration results.

[0092] In summary, the page file processing method provided by the embodiment of the present disclosure can obtain a page file corresponding to at least one business, and deploy the page file to a container pre-created by the page management platform. In response to the address configuration instruction sent by the first account, the page access address is configured for the page file to complete the file deployment; the page access addresses of the page files corresponding to different businesses are different. In the embodiment of the present disclosure, the page management platform, as a public service, uniformly provides deployment services for each business, and the page files corresponding to each business can be uniformly deployed to the page management platform. In this way, there is no need to apply for a fixed amount of hardware resources for the business, which can avoid resource waste to a certain extent.

[0093] And you only need to provide the page files that need to be deployed, and the page management platform will directly deploy them based on the pre-created container. In this way, there is no need to build a container image, which can reduce the deployment time and improve deployment efficiency to a certain extent.

[0094] Optionally, the operation of configuring a page access address for the page file in response to the address configuration instruction sent by the first account may specifically include:

[0095] Step S21 : In response to a selection instruction for a candidate page file from the first account, taking the candidate page file indicated by the selection instruction as a configuration file to be configured; the candidate page file is a page file corresponding to a business to which the first account belongs.

[0096] Specifically, the alternative page file may be a page file that has been deployed in the container among the page files corresponding to the business to which the first account belongs. The business to which the first account belongs may be a business that the first account has operation authority. For example, the business to which the first account belongs may be a business that the first account is responsible for handling in the department to which it belongs. In the embodiment of the present disclosure, the alternative page file can be used as a selection object for the first account to select. The first account's selection instruction for the alternative page file may be triggered by a selection operation on the alternative page file, and the selected alternative page file is the alternative page file indicated by the selection instruction. Since the alternative page file is the page file corresponding to the business to which the first account belongs, it is possible to avoid the page files corresponding to other businesses being displayed to the first account, thereby ensuring service isolation between different businesses. That is, in the deployment link, the page files corresponding to different businesses will only be viewed and operated by the account responsible for the business, thereby avoiding the problem of information leakage between different businesses.

[0097] It should be noted that in the embodiments of the present disclosure, at least one page file corresponding to a business can be deployed in a container. Since the page files corresponding to each business are uniformly managed by the page management platform and each business is isolated from each other, page files corresponding to multiple businesses can be deployed in the same container, thereby improving resource utilization.

[0098] Step S22: Setting a page access address for the configuration file according to the domain name and access path indicated by the address configuration instruction.

[0099] In this step, the domain name and access path indicated by the address configuration instruction can be set by the first account according to actual needs. The page access address can be generated according to the domain name plus the access path indicated by the address configuration instruction, and the routing configuration information can be generated according to the page access address, and written into the address configuration file of the page management platform. For example, the page management platform can be deployed with an nginx service, and the correspondence between the file information of the file to be configured and the page access address can be stored in the address configuration file as routing configuration information. The page management platform can also be configured with a node service, wherein the operations of generating the page access address and writing the correspondence between the identifier of the file to be configured and the page access address as routing configuration information can be implemented by the node service. The address configuration file can be "nginx.conf". In this way, after the page file is deployed to the container, the route is configured, that is, the page access address is generated using a specific domain name plus a specified access path, so that the page deployed by the business can be accessed.

[0100] In the disclosed embodiment, in response to a selection instruction for an alternative page file from a first account, the alternative page file indicated by the selection instruction is used as the configuration file to be configured; the alternative page file is the page file corresponding to the business to which the first account belongs. Based on the domain name and access path indicated by the address configuration instruction, a page access address is set for the configuration file to be configured. In this way, to a certain extent, while implementing the configuration of the page access address, page files corresponding to other businesses can be prevented from being displayed to the first account, thereby avoiding the problem of information leakage between different businesses.

[0101] Optionally, different page file directories are pre-associated with paths, and the path associated with the page file directory to which the alternative page file belongs is the same as or partially overlaps with the access path; the paths associated with the page file directories corresponding to different businesses are different. In the embodiment of the present disclosure, each route has a designated service directory, that is, each path is associated with a corresponding page file directory. In the page management platform, page files can be divided according to directories, and the specific directory division method can be set according to actual needs, and the embodiment of the present disclosure does not limit this. For example, directories can be divided according to department + business name. For example, a directory is divided for the composition of a department + business name. Figure 2 is a directory diagram according to an exemplary embodiment. Figure 2 As shown, the resource file may refer to a page file, and the resource directory may refer to a page file directory. The path associated with the page file directory can be set according to actual needs. For example, the directory path of the page file directory in the page management platform can be set as the associated path, or the name of the page file directory can be set as the associated path.

[0102] Specifically, when the path pre-associated with the page file directory is exactly the same as the content of the access path, the page files under the page file directory can be used as alternative page files. Alternatively, when the path pre-associated with the page file directory is partially identical to the content of the access path, the page files under the page file directory can be used as alternative page files. When generating a page access address according to the domain name plus the access path indicated by the address configuration instruction, the domain name indicated by the address configuration instruction plus the access path and the path of the selected alternative page file can be used as the page access address. Alternatively, the domain name plus the access path can be directly used as the page access address.

[0103] Since the same domain name may be used when configuring page access addresses for page files of different businesses, in the embodiment of the present disclosure, the paths associated with the page file directories corresponding to different businesses are different, which can avoid, to a certain extent, the adverse effects caused by routing overlap when different businesses use the same domain name. Specifically, when different businesses use the same domain name, in response to the received association instruction, it can be detected whether there is any overlapping part between the associated path and the path indicated by the association instruction; wherein the associated path is the path currently associated with the page file directory corresponding to other businesses. The existence of overlapping parts may refer to partial / complete duplication of the contents of the two. If there is no overlapping part, the path indicated by the association instruction is associated with the page file directory indicated by the association instruction. In this way, by performing a conflict check, it can be ensured that there is no inclusion relationship in the routing prefix, thereby ensuring the security of the routing configuration. wherein, the routing prefix may refer to the associated path.

[0104] In the embodiment of the present disclosure, when the path associated with the directory is the same as the access path or there is partial overlap, the file in the directory is used as an alternative page file. Since the paths associated with the page file directories corresponding to different businesses are different, this ensures that the paths associated with different businesses will not have any inclusion relationship, thereby further avoiding information leakage between different businesses.

[0105] It should be noted that permission control can also be performed in the embodiments of the present disclosure. Specifically, only when the first account is a project administrator account, the production environment routing configuration can be modified in response to a modification instruction, and the routing configuration can be updated after the current audit account has passed the review. Among them, modifying the production environment routing configuration in response to a modification instruction can be to modify the page access address of the page file indicated by the modification instruction, and updating the routing configuration means updating the page access address of the page file indicated by the modification instruction. For example, the routing configuration information of the page file indicated by the modification instruction is updated to the routing configuration information generated based on the modified page access address.

[0106] Optionally, before deploying the page file to the container pre-created by the page management platform, the following steps may also be performed in the embodiment of the present disclosure: Step S31, creating the container based on the pre-set container image. Accordingly, the step of deploying the page file to the container pre-created by the page management platform may specifically include: deploying the page file in the created container. Among them, the container image can be deployed in the page management platform after the page management platform is built. Exemplarily, the container image can be deployed in the page management platform before the page file sent by the terminal is received. Accordingly, a container can be built based on the container image. For example, a preset creation command can be used to build a container based on the container image to facilitate subsequent deployment. In the embodiment of the present disclosure, since the container image is pre-set in the page management platform and the container is created in advance, by directly deploying the page file in the created container, the time consumption of container startup can be reduced to a certain extent, the time consumption of deploying page files can be reduced, and the deployment efficiency can be improved.

[0107] Optionally, in the embodiment of the present disclosure, the following steps may also be performed:

[0108] Step S41: Synchronize the currently deployed page file, the page access address of the deployed page file, and related information of the container in which it is located.

[0109] In the embodiment of the present disclosure, synchronization can be performed during the cold start phase when the page management platform is expanded or receives a restart instruction. Specifically, the currently deployed page files and the routing configuration information corresponding to each deployed page file can be synchronized to synchronize the page access address. The container where the deployed page file is located can be the container where the page file is deployed, and the relevant information of the container can be the service address corresponding to the current cluster, specifically the IP address and port information of the instance corresponding to the container. Exemplarily, these data can be synchronized to a preset storage device.

[0110] Step S42: After the page management platform is restarted, the currently deployed page file is redeployed in the container according to the currently deployed page file, the page access address of the deployed page file, and the related information of the container.

[0111] Specifically, the synchronized page files can be redeployed in the page management platform. Specifically, the containers where the currently deployed page files were previously located can be located based on the relevant container information. Then, the currently deployed page files can be redeployed in these containers to avoid omissions. Furthermore, routing configuration information is generated based on the synchronized page access address and written into the address configuration file of the page management platform, thereby completing the redeployment operation.

[0112] In the disclosed embodiment, the currently deployed page file, the page access address of the deployed page file, and related information about the container in which it is located are synchronized. After the page management platform is restarted, the currently deployed page file is redeployed in the container based on the currently deployed page file, the page access address of the deployed page file, and related information about the container in which it is located. This ensures, to a certain extent, that the state of the page management platform before and after the restart is consistent, avoiding deployment omissions.

[0113] Optionally, the above-mentioned operation of obtaining a page file corresponding to at least one business may specifically include: step S51, receiving the page file submitted by the preset interface when the second account passes the first verification; the page file is submitted to the preset interface by the second account in a target deployment method, and the target deployment method is selected from at least two preset deployment methods.

[0114] Accordingly, before deploying the page file to the container pre-created by the page management platform, the following steps may also be performed in the embodiment of the present disclosure: Step S61, perform a second verification on the preset interface, and if the second verification is passed, execute the operation of deploying the page file to the container pre-created by the page management platform.

[0115] Specifically, the second account may be the same as the above-mentioned first account, or may be different. The first verification and the second verification may be set according to actual needs, and the complexity of the first verification may be higher than the complexity of the second verification. For example, the first verification may be to verify whether the second account is legal, whether the second account has the operation rights, and whether the current time is in the operable time. If so, it can be determined that the second account has passed the first verification. Accordingly, after the second account issues the deployment instruction, it can first be authenticated by the preset interface, that is, the first verification is performed. If the second account passes the first verification, the preset interface can submit the page file to be deployed to the page management platform. The page management platform will perform authentication again through the second verification. The second verification may be to verify whether the preset interface for submitting the page file this time is a pre-authorized interface service. If so, it can be determined that the preset interface has passed the second verification, and the page file can be deployed to the page management platform.

[0116] In this disclosed embodiment, dual authentication ensures deployment security to a certain extent. Furthermore, the second account is first authenticated by a pre-set interface, and the page management platform only needs to verify the pre-set interface to determine the legitimacy of this deployment, thereby reducing the burden on the page management platform to a certain extent.

[0117] Furthermore, at least two preset deployment methods can be set according to actual needs, and the preset deployment method can be a page file submission method supported by the page management platform. Exemplarily, the preset deployment method can include deployment based on a preset plug-in, deployment based on a command line tool, and deployment based on a specified platform. Among them, the preset plug-in can be a continuous integration (CI) / continuous deployment (CD) platform deployment plug-in, and the specified platform can be a static hosting platform. Figure 3 FIG. 1 is a schematic diagram showing a deployment according to an exemplary embodiment. Figure 3 As shown, the user can build and package the developed project to obtain the page file, and then publish it according to the three provided ways of deploying it to the page processing platform. After verification by the API service, it can be deployed to the public static service. Among them, the API service can correspond to the above-mentioned preset receiving service, and the public static service can correspond to the above-mentioned page processing platform. In the embodiment of the present disclosure, by providing a variety of preset deployment methods, the second account can select the target deployment method based on actual needs, and perform subsequent deployment and release more conveniently and quickly, thereby meeting the use scenarios of different businesses to a certain extent.

[0118] Figure 4 is a flow chart showing another method for processing a page file according to an exemplary embodiment. The method can be applied to a terminal, such as Figure 4 As shown, the method may include:

[0119] Step 201: Provide at least one page file corresponding to a business to a page management platform; the page management platform is used to deploy the page file to a container pre-created by the page management platform.

[0120] There may be multiple terminals, and one terminal may be used to provide page files corresponding to one or more services.

[0121] Step 202: Send an address configuration instruction to the page management platform based on the first account; the page management platform is further configured to configure a page access address for the page file in response to the address configuration instruction to complete file deployment; the page access addresses of the page files corresponding to different businesses are different.

[0122] In summary, the page file processing method provided by the embodiment of the present disclosure is such that the terminal can provide the page management platform with at least one page file corresponding to a business and send an address configuration instruction based on the first account. This allows the page management platform to deploy the page file to a container pre-created by the page management platform. In response to the address configuration instruction sent by the first account, the page access address is configured for the page file to complete the file deployment; the page access addresses of the page files corresponding to different businesses are different. In the embodiment of the present disclosure, the page management platform, as a public service, uniformly provides deployment services for each business, and the page files corresponding to each business can be uniformly deployed to the page management platform. In this way, there is no need to apply for a fixed amount of hardware resources for the business, which can avoid resource waste to a certain extent.

[0123] And you only need to provide the page files that need to be deployed, and the page management platform will directly deploy them based on the pre-created container. In this way, there is no need to build a container image, which can reduce the deployment time and improve deployment efficiency to a certain extent.

[0124] Optionally, the above-mentioned operation of providing at least one page file corresponding to a business to the page management platform specifically includes: providing a page file to be deployed to a preset interface based on a second account; the page file is provided based on a target deployment method selected from at least two preset deployment methods; the preset interface is used to submit the page file to the page management platform when the second account passes the first verification. In the embodiment of the present disclosure, by providing a variety of preset deployment methods, the second account can select a target deployment method based on actual needs for subsequent deployment and release, thereby meeting the usage scenarios of different businesses to a certain extent. The second account is first verified by the preset interface, so that the page management platform only needs to verify the preset interface later to determine the rationality of this deployment, thereby reducing the burden on the page management platform to a certain extent.

[0125] Optionally, the following operations may also be performed in the embodiment of the present disclosure: displaying an alternative page file, the alternative page file being a page file corresponding to the business to which the first account belongs; in response to a selection operation on the alternative page file, sending a selection instruction to the page management platform; the page management platform is further configured to use the alternative page file indicated by the selection instruction as a to-be-configured file, and to set a page access address for the to-be-configured file according to the domain name and access path indicated by the address configuration instruction. Specifically, the terminal may display a visual interface in which the alternative page file is displayed for selection by the first account. Corresponding to the aforementioned Figure 2 In the example above, the routing configuration restricts access to only the files under the department_business app to which the first account belongs. This isolates services from a routing perspective, ensuring that different businesses do not affect each other.

[0126] The first account can also set the domain name and access path in the interface to trigger the terminal to send an address configuration instruction based on the first account. The domain name and access path set in the interface are the domain name and access path indicated by the address configuration instruction. For example, the selectable domain names and access paths can be displayed in the interface, and the domain name and access path selected by the first account are used as the domain name and access path indicated by the address configuration instruction. Alternatively, an input box can be provided in the interface, and the domain name and access path entered by the first account are used as the domain name and access path indicated by the address configuration instruction. In the embodiment of the present disclosure, the page processing platform supports the generation of page routing forwarding rules through visual operations, and the free customization of page-level routing access, that is, the page access address of the page file can be defined through visual operations. In this way, compared with the method of contacting the operation and maintenance personnel and having the operation and maintenance personnel define it by modifying the configuration rules, the configuration can be completed based on the visual interface in the embodiment of the present disclosure, thereby reducing costs to a certain extent and saving communication time.

[0127] In the disclosed embodiment, alternative page files can be displayed as selection objects for selection by the first account. Since the alternative page files are page files corresponding to the business to which the first account belongs, page files corresponding to other businesses can be prevented from being displayed to the first account, ensuring service isolation between different businesses. That is, during the deployment process, page files corresponding to different businesses can only be viewed and operated by the account responsible for that business, thereby preventing information leakage between different businesses.

[0128] Optionally, the above-mentioned operation of displaying alternative page files may specifically include: step S71, displaying all page files included in the target file directory and / or displaying the target file directory; wherein, different page file directories are pre-associated with paths, and the path associated with the target file directory is the same as or partially overlaps with the access path. Specifically, when the path pre-associated with the page file directory and the content of the access path are exactly the same, or when the path pre-associated with the page file directory and the content of the access path are partially the same, the page file may be directly returned for display, or the target file directory may be directly returned and displayed in the form of a directory. In this way, by providing a variety of display methods, the needs of the second account can be more fully met.

[0129] Exemplarily, taking the page management platform using nginx service as an example, three formats of routing configuration templates can be provided in the embodiment of the present disclosure to meet different front-end business needs. In routing template 1, when accessed with a specified prefix, the target page is searched under the specified file directory. In routing template 2, when accessed with a specified prefix, the specified file is returned. In routing template 3, when accessed with a specified path, the specified file is returned. Among them, when accessed with a specified prefix, searching for the target page under the specified file directory can correspond to: when the path pre-associated with the page file directory and the content of the access path are partially the same, the target file directory is returned. When accessed with a specified prefix, returning the specified file can correspond to: when the path pre-associated with the page file directory and the content of the access path are partially the same, the page file is returned. When accessed with a specified path, returning the specified file can correspond to: when the path pre-associated with the page file directory and the content of the access path are exactly the same, the page file is returned. The definition method of the routing template can be set according to actual needs. Exemplarily, routing template 1 can be defined as: #case: prefix match, rewrite to folder. Routing template 2 can be defined as: #case: prefix match, rewrite to file. Route template 3 can be defined as: #case: equal match, rewrite to file. The "location" in route template 1 can be set to: <User Access Prefix>{alias / data / nginx / html / <Department bu>_<Business app> / latest / Specify the file directory; the "location" in route template 2 can be set to: <User Access Prefix>{root / data / nginx / html / <Department bu>_<Business app> / latest / ; the "location" in route template 3 can be set to: <User Access Address>{root / data / nginx / html / <Department bu>_<Business app> / latest / .

[0130] In one application scenario, the page file can be a static web page in a front-end project, and the page processing platform can be a static service cluster based on docker (container), and all front-end pages can be deployed to the cluster. The following is an exemplary architecture to illustrate the embodiment of the present disclosure. Figure 5 is a schematic diagram of the architecture of a page processing platform according to an exemplary embodiment. Figure 5As shown, the platform includes the nginx service and the node service. The nginx service serves as the external traffic entry point, implementing basic static services. Directory and path configuration can be performed based on the Nginx service. Within the Nginx service, different services can be differentiated by path. Specifically, different paths can be associated with directories for different services. Under the routing configuration function, account access to directories can be restricted, achieving isolation between services. This allows the page management platform, as a public static page hosting service, to host static pages for different services. The node service can be used to implement dynamic and rapid deployment of static pages, dynamic routing configuration updates, and cold start resource synchronization. As the Nginx service serves as the traffic entry point, page files can be submitted to the Nginx service, which then passes them to the node service. The node service performs secondary verification, deployment, synchronization, generates page access addresses, and writes them to the Nginx configuration file to implement address configuration. Specifically, the node service can deploy page files into pre-created containers, enabling dynamic and rapid deployment, avoiding the long image rollout time and supporting rapid release and rollback. By providing routing configuration capabilities, it is easy to manage the access paths of static pages. Routing dynamic configuration update can refer to the aforementioned operation of configuring the page access address, cold start resource synchronization can refer to the aforementioned synchronization operation, cluster information storage can refer to synchronizing related information, static page resource synchronization can refer to synchronizing the currently deployed page files, and routing configuration synchronization can refer to synchronizing the page access addresses of deployed page files.

[0131] It should be noted that the above-mentioned nginx service can also be replaced by other services, such as the node service, and the embodiments of the present disclosure do not limit this.

[0132] Furthermore, the page processing platform can pre-deploy static service images in a container cloud. This means pre-building container images and creating containers within the page processing platform. Container health checks can also be performed. Static services are based on the container cloud, leveraging the container cloud's health checks, service governance, and dynamic scaling capabilities to ensure business stability. A container cloud refers to a server with a container engine installed.

[0133] In a related technology, as various services are gradually containerized and the container environment and front-end and back-end are separated, since containers are isolated and stateless, each front-end project needs to apply for independent service resources of at least 1 core and 1G in a dual-data center to build a container image, build a container based on the container image, and then deploy one or more HTML files for a business. However, for static page files, the actual function of the container is only to render HTML files, which leads to relatively low resource utilization. At the same time, a large number of front-end projects independently apply for and deploy, which will lead to the maintenance of more service nodes in the later stage, resulting in higher service maintenance costs. In addition, the time cost of this deployment method is relatively high. When urgent problems arise and need to be corrected online, it often takes longer.

[0134] In the embodiment of the present disclosure, a front-end-oriented static page hosting service is provided, which provides unified deployment services for various businesses, and the page files corresponding to each business can be uniformly deployed to the page management platform.

[0135] Businesses don't need to worry about resource application and maintenance, saving service resources and maintenance costs. Furthermore, since there's no need to build an image and restart the server upon receiving a page file to deploy, rapid deployment is possible, improving rollout efficiency.

[0136] Figure 6 is a block diagram of a page file processing device according to an exemplary embodiment, the device is applied to a page management platform, such as Figure 6 As shown, the device 30 may include:

[0137] The acquisition module 301 is configured to acquire a page file corresponding to at least one business and deploy the page file to a container pre-created by the page management platform;

[0138] The configuration module 302 is configured to execute the address configuration instruction sent by the first account, configure the page access address for the page file, and complete the file deployment; the page access address of the page file corresponding to different services is different.

[0139] In summary, the page file processing device provided in the embodiment of the present disclosure can obtain a page file corresponding to at least one business, and deploy the page file to a container pre-created by the page management platform. In response to the address configuration instruction sent by the first account, the page access address is configured for the page file to complete the file deployment; the page access addresses of the page files corresponding to different businesses are different. In the embodiment of the present disclosure, the page management platform, as a public service, uniformly provides deployment services for each business, and the page files corresponding to each business can be uniformly deployed to the page management platform. In this way, there is no need to apply for a fixed amount of hardware resources for the business, which can avoid resource waste to a certain extent. And only the page files that need to be deployed need to be provided, and the page management platform will deploy them directly based on the pre-created container. In this way, there is no need to build a container image, which can reduce the deployment time to a certain extent and improve deployment efficiency.

[0140] In an optional embodiment, the configuration module 302 is specifically configured to execute:

[0141] In response to a selection instruction for a candidate page file from the first account, using the candidate page file indicated by the selection instruction as a to-be-configured file; the candidate page file is a page file corresponding to a business to which the first account belongs;

[0142] According to the domain name and access path indicated by the address configuration instruction, a page access address is set for the configuration file to be configured.

[0143] In an optional embodiment, different page file directories are pre-associated with paths, and the path associated with the page file directory to which the candidate page file belongs is the same as or partially overlaps with the access path; the paths associated with the page file directories corresponding to different services are different.

[0144] In an optional embodiment, the device 30 further includes:

[0145] A creation module is configured to create the container based on a preset container image;

[0146] The acquisition module 301 is specifically configured to execute: deploying the page file in the created container.

[0147] In an optional embodiment, the device 30 further includes:

[0148] A synchronization module is configured to synchronize the currently deployed page files, the page access addresses of the deployed page files, and the related information of the containers in which they are located;

[0149] The deployment module is configured to execute, after the page management platform is restarted, redeploying the currently deployed page file in the container according to the currently deployed page file, the page access address of the deployed page file and the relevant information of the container.

[0150] In an optional embodiment, the acquisition module 301 is further configured to execute:

[0151] Receiving the page file submitted by the preset interface when the second account passes the first verification; the page file is submitted by the second account to the preset interface in a target deployment mode, and the target deployment mode is selected from at least two preset deployment modes;

[0152] The device also includes: an execution module, configured to perform a second verification on the preset interface, and if the second verification is passed, execute the operation of deploying the page file to the container pre-created by the page management platform.

[0153] Figure 7 is a block diagram of another page file processing device according to an exemplary embodiment, which is applied to a terminal, such as Figure 7 As shown, the device 40 may include:

[0154] A providing module 401 is configured to provide a page file corresponding to at least one business to a page management platform; the page management platform is configured to deploy the page file to a container pre-created by the page management platform;

[0155] The first sending module 402 is configured to execute an address configuration instruction to the page management platform based on the first account; the page management platform is also used to respond to the address configuration instruction to configure a page access address for the page file to complete file deployment; the page access addresses of the page files corresponding to different businesses are different.

[0156] In summary, the page file processing device provided in the embodiment of the present disclosure can provide the page management platform with at least one page file corresponding to a business and an address configuration instruction based on the first account. This allows the page management platform to deploy the page file to a container pre-created by the page management platform. In response to the address configuration instruction sent by the first account, the page access address is configured for the page file to complete the file deployment; the page access addresses of the page files corresponding to different businesses are different. In the embodiment of the present disclosure, the page management platform, as a public service, uniformly provides deployment services for each business, and the page files corresponding to each business can be uniformly deployed to the page management platform. In this way, there is no need to apply for a fixed amount of hardware resources for the business, which can avoid resource waste to a certain extent. And only the page files that need to be deployed need to be provided, and the page management platform directly deploys them based on the pre-created container. In this way, there is no need to build a container image, which can reduce the deployment time and improve deployment efficiency to a certain extent.

[0157] In an optional embodiment, the device 40 further includes:

[0158] a display module configured to display an alternative page file, where the alternative page file is a page file corresponding to the business to which the first account belongs;

[0159] The second sending module is configured to execute a selection instruction to the page management platform in response to the selection operation of the alternative page file; the page management platform is also used to use the alternative page file indicated by the selection instruction as the configuration file to be configured, and set the page access address for the configuration file to be configured according to the domain name and access path indicated by the address configuration instruction.

[0160] In an optional embodiment, the display module is specifically configured to execute:

[0161] Display all page files included in the target file directory and / or display the target file directory;

[0162] Different page file directories are pre-associated with paths, and the path associated with the target file directory is the same as or partially overlaps with the access path.

[0163] In an optional embodiment, the providing module 401 is specifically configured to execute:

[0164] A page file to be deployed is provided to a preset interface based on a second account; the page file is provided based on a target deployment method selected from at least two preset deployment methods; the preset interface is used to submit the page file to the page management platform when the second account passes the first verification.

[0165] Regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0166] According to one embodiment of the present disclosure, a page file processing system is provided, which includes a terminal and a page management platform; the terminal is used to provide the page management platform with at least one page file corresponding to a business; the page management platform is used to deploy the page file to a container pre-created by the page management platform; the terminal is also used to send an address configuration instruction to the page management platform based on a first account; the page management platform is also used to configure a page access address for the page file in response to the address configuration instruction to complete file deployment; the page access addresses of page files corresponding to different businesses are different.

[0167] The page file processing method corresponding to the page file processing system may include the following steps: Step S81, the terminal provides at least one page file corresponding to a business to the page management platform. Step S82, the page management platform deploys the page file to a container pre-created by the page management platform. Step S83, the terminal sends an address configuration instruction to the page management platform based on the first account. Step S84, the page management platform configures a page access address for the page file in response to the address configuration instruction to complete file deployment; the page access addresses of page files corresponding to different businesses are different.

[0168] According to one embodiment of the present disclosure, an electronic device is provided, comprising: a processor and a memory for storing processor-executable instructions, wherein the processor is configured to implement the steps in the page file processing method in any of the above embodiments when executing.

[0169] According to an embodiment of the present disclosure, a storage medium is further provided. When instructions in the storage medium are executed by a processor of an electronic device, the electronic device can execute the steps in the page file processing method in any of the above embodiments.

[0170] According to one embodiment of the present disclosure, a computer program product is also provided, which includes readable program instructions. When the readable program instructions are executed by a processor of an electronic device, the electronic device can perform the steps in the page file processing method in any of the above embodiments.

[0171] Figure 87 is a block diagram of an apparatus for page file processing according to an exemplary embodiment. The apparatus 700 may include a processing component 702, a memory 704, a power component 706, a multimedia component 708, an audio component 710, an input / output interface 712, a sensor component 714, a communication component 716, and a processor 720. The processing component 702 may include one or more processors 720 to execute instructions to complete all or part of the steps of the above-mentioned page file processing method. In an exemplary embodiment, a storage medium including instructions is also provided, such as a memory 704 including instructions, and the above-mentioned instructions can be executed by the processor 720 of the apparatus 700 to complete the above-mentioned method. Optionally, the storage medium may be a non-temporary computer-readable storage medium, for example, the non-temporary computer-readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

[0172] Figure 9 8 is a block diagram illustrating another apparatus for page file processing according to an exemplary embodiment. Apparatus 800 may include a processing component 822, a memory 832, an input / output interface 858, a network interface 850, and a power supply component 826. Apparatus 800 may be provided as a server. Applications stored in memory 832 may include one or more modules, each corresponding to a set of instructions. Furthermore, processing component 822 is configured to execute the instructions to perform the above-described page file processing method.

[0173] The user information (including but not limited to the user's device information, user personal information, etc.) and related data involved in this disclosure are all information authorized by the user or authorized by all parties.

[0174] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

[0175] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A page file processing method, characterized in that: The method is applied to a page management platform, and includes: Obtaining a page file corresponding to at least one business, and deploying the page file to a container pre-created by the page management platform; In response to the address configuration instruction sent by the first account, configuring a page access address for the page file to complete file deployment; the page access addresses of the page files corresponding to different businesses are different; The configuring a page access address for the page file in response to the address configuration instruction sent by the first account includes: In response to a selection instruction for a candidate page file from the first account, using the candidate page file indicated by the selection instruction as a to-be-configured file; the candidate page file is a page file corresponding to a business to which the first account belongs; Setting a page access address for the configuration file to be configured according to the domain name and access path indicated by the address configuration instruction; wherein the domain name and access path indicated by the address configuration instruction are set by the first account; The deploying of the page file into the container pre-created by the page management platform includes: deploying the page files corresponding to multiple services in the same container.

2. The method according to claim 1, characterized in that Different page file directories are pre-associated with paths. The path associated with the page file directory to which the candidate page file belongs is the same as or partially overlaps with the access path. The paths associated with the page file directories corresponding to different services are different.

3. The method according to claim 1, characterized in that Before deploying the page file to the container pre-created by the page management platform, the method further includes: Creating the container based on a pre-set container image; The deploying the page file to the container pre-created by the page management platform includes: deploying the page file in the created container.

4. The method according to claim 1, wherein The method comprises: Synchronize the currently deployed page files, the page access addresses of the deployed page files, and the relevant information of the container in which they are located; After the page management platform is restarted, the currently deployed page file is redeployed in the container according to the currently deployed page file, the page access address of the deployed page file, and the related information of the container.

5. The method according to claim 1, wherein The obtaining of at least one page file corresponding to a business includes: Receiving the page file submitted by the preset interface when the second account passes the first verification; the page file is submitted by the second account to the preset interface in a target deployment mode, and the target deployment mode is selected from at least two preset deployment modes; Before deploying the page file to the container pre-created by the page management platform, the method also includes: performing a second verification on the preset interface, and if the second verification is passed, executing the operation of deploying the page file to the container pre-created by the page management platform.

6. A page file processing method, characterized in that: Applied to a terminal, the method includes: Providing at least one page file corresponding to a business to a page management platform; the page management platform is used to deploy the page file to a container pre-created by the page management platform; wherein deploying the page file to the container pre-created by the page management platform includes: deploying the page files corresponding to multiple businesses in the same container; sending an address configuration instruction to the page management platform based on the first account; the page management platform is further configured to configure a page access address for the page file in response to the address configuration instruction to complete file deployment; the page access addresses of the page files corresponding to different businesses are different; wherein the domain name and access path indicated by the address configuration instruction are set by the first account; Characterized in that the method further comprises: Displaying an alternative page file, where the alternative page file is a page file corresponding to the business to which the first account belongs; In response to the selection operation of the alternative page file, a selection instruction is sent to the page management platform; the page management platform is also used to use the alternative page file indicated by the selection instruction as the configuration file to be configured, and set the page access address for the configuration file to be configured according to the domain name and access path indicated by the address configuration instruction.

7. The method according to claim 6, characterized in that The display alternative page file includes: Display all page files included in the target file directory and / or display the target file directory; Different page file directories are pre-associated with paths, and the path associated with the target file directory is the same as or partially overlaps with the access path.

8. The method according to any one of claims 6-7, characterized in that: Providing at least one page file corresponding to a business to the page management platform includes: A page file to be deployed is provided to a preset interface based on a second account; the page file is provided based on a target deployment method selected from at least two preset deployment methods; the preset interface is used to submit the page file to the page management platform when the second account passes the first verification.

9. A page file processing device, characterized in that: The device is applied to a page management platform, and includes: An acquisition module configured to acquire a page file corresponding to at least one business and deploy the page file to a container pre-created by the page management platform; a configuration module configured to execute, in response to the address configuration instruction sent by the first account, a configuration of a page access address for the page file to complete file deployment; the page access addresses of the page files corresponding to different businesses are different; The configuration module is specifically configured to execute: In response to a selection instruction for a candidate page file from the first account, using the candidate page file indicated by the selection instruction as a to-be-configured file; the candidate page file is a page file corresponding to a business to which the first account belongs; According to the domain name and access path indicated by the address configuration instruction, the page access address is set for the configuration file; wherein the domain name and access path indicated by the address configuration instruction are set by the first account The acquisition module is specifically configured to deploy the page files corresponding to multiple services in the same container.

10. The device according to claim 9, characterized in that Different page file directories are pre-associated with paths. The path associated with the page file directory to which the candidate page file belongs is the same as or partially overlaps with the access path. The paths associated with the page file directories corresponding to different services are different.

11. The device according to claim 9, characterized in that The device further comprises: A creation module is configured to create the container based on a preset container image; The acquisition module is specifically configured to execute: deploying the page file in the created container.

12. The device according to claim 9, characterized in that The device further comprises: A synchronization module is configured to synchronize the currently deployed page files, the page access addresses of the deployed page files, and the related information of the containers in which they are located; The deployment module is configured to execute, after the page management platform is restarted, redeploying the currently deployed page file in the container according to the currently deployed page file, the page access address of the deployed page file and the relevant information of the container.

13. The device according to claim 9, characterized in that The acquisition module is further specifically configured to execute: Receiving the page file submitted by the preset interface when the second account passes the first verification; the page file is submitted by the second account to the preset interface in a target deployment mode, and the target deployment mode is selected from at least two preset deployment modes; The device also includes: an execution module, configured to perform a second verification on the preset interface, and if the second verification is passed, execute the operation of deploying the page file to the container pre-created by the page management platform.

14. A page file processing device, characterized in that: Applied to a terminal, the device includes: A providing module is configured to provide a page file corresponding to at least one business to a page management platform; the page management platform is configured to deploy the page file to a container pre-created by the page management platform; wherein deploying the page file to the container pre-created by the page management platform includes: deploying the page files corresponding to multiple businesses in the same container; a first sending module configured to execute an address configuration instruction to the page management platform based on the first account; the page management platform is further configured to configure a page access address for the page file in response to the address configuration instruction to complete file deployment; the page access addresses of the page files corresponding to different businesses are different; wherein the domain name and access path indicated by the address configuration instruction are set by the first account; The device further comprises: a display module configured to display an alternative page file, where the alternative page file is a page file corresponding to the business to which the first account belongs; The second sending module is configured to execute a selection instruction to the page management platform in response to the selection operation of the alternative page file; the page management platform is also used to use the alternative page file indicated by the selection instruction as the configuration file to be configured, and set the page access address for the configuration file to be configured according to the domain name and access path indicated by the address configuration instruction.

15. The device according to claim 14, characterized in that The display module is specifically configured to execute: Display all page files included in the target file directory and / or display the target file directory; Different page file directories are pre-associated with paths, and the path associated with the target file directory is the same as or partially overlaps with the access path.

16. The device according to any one of claims 14-15, characterized in that The providing module is specifically configured to execute: A page file to be deployed is provided to a preset interface based on a second account; the page file is provided based on a target deployment method selected from at least two preset deployment methods; the preset interface is used to submit the page file to the page management platform when the second account passes the first verification.

17. A page file processing system, characterized in that: The system includes a terminal and a page management platform; The terminal is configured to provide the page management platform with at least one page file corresponding to a service; The page management platform is configured to deploy the page file into a container pre-created by the page management platform; wherein deploying the page file into the container pre-created by the page management platform includes: deploying the page files corresponding to multiple services in the same container; The terminal is further configured to send an address configuration instruction to the page management platform based on the first account, where the domain name and access path indicated by the address configuration instruction are set by the first account; The terminal is further configured to display an alternative page file, the alternative page file being a page file corresponding to the business to which the first account belongs; and in response to a selection operation on the alternative page file, send a selection instruction to the page management platform; The page management platform is further configured to, in response to the selection instruction, use the candidate page file indicated by the selection instruction as a to-be-configured file; The page management platform is further configured to configure a page access address for the page file in response to the address configuration instruction to complete file deployment; the page access addresses of the page files corresponding to different services are different.

18. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the method according to any one of claims 1 to 8.

19. A storage medium, characterized in that: When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device executes the method according to any one of claims 1 to 8.

20. A computer program product, characterized in that The computer program product includes readable program instructions, and when the readable program instructions are executed by a processor of an electronic device, the electronic device is caused to perform the method according to any one of claims 1 to 8.

Images