Disclosure of Invention
The disclosure provides a method, a device, a system, an electronic device and a storage medium for processing a page file, so as to at least solve the problem of resource waste in the related art. The technical scheme of the present disclosure is as follows:
according to a first aspect of an embodiment of the present disclosure, there is provided a method for processing a page file, applied to a page management platform, the method including:
acquiring a page file corresponding to at least one service, and deploying the page file into a container pre-created by the page management platform;
And responding to the address configuration instruction sent by the first account, configuring the page access address for the page file to finish file deployment, wherein the page access addresses of the page files corresponding to different services are different.
Optionally, the responding to the address configuration instruction sent by the first account configures a page access address for the page file, including:
Responding to a selection instruction of the first account for an alternative page file, and taking the alternative page file indicated by the selection instruction as a file to be configured, wherein the alternative page file is a page file corresponding to a service to which the first account belongs;
and setting a page access address for the file to be configured according to the domain name and the access path indicated by the address configuration instruction.
Optionally, paths are associated with different page file catalogues in advance, the paths associated with the page file catalogues of the candidate page files are identical to the access paths or partially coincide with the access paths, and the paths associated with the page file catalogues corresponding to different services are different.
Optionally, before the deploying the page file into the container created in advance by the page management platform, the method further includes:
creating the container based on a preset container mirror image;
The step of deploying the page file into a container pre-created by the page management platform comprises the step of deploying the page file in the created container.
Optionally, the method includes:
Synchronizing the current deployed page file, the page access address of the deployed page file and the related information of the container;
and after restarting the page management platform, redeploying the current deployed page file in the container according to the current deployed page file, the page access address of the deployed page file and the related information of the container.
Optionally, the obtaining the page file corresponding to the at least one service includes:
the method comprises the steps of receiving a page file submitted by a preset interface under the condition that a second account passes a first verification, wherein the page file is submitted to the preset interface by the second account in a target deployment mode, and the target deployment mode is selected from at least two preset deployment modes;
Before the page file is deployed into the container pre-created by the page management platform, the method further comprises the steps of performing second verification on the preset interface, and executing the operation of deploying the page file into the container pre-created by the page management platform under the condition that the second verification is passed.
According to a second aspect of the embodiments of the present disclosure, there is provided a method for processing a page file, applied to a terminal, the method including:
the method comprises the steps of providing at least one page file corresponding to a service for a page management platform, wherein the page management platform is used for deploying the page file into a container pre-created by the page management platform;
the method comprises the steps of sending an address configuration instruction to the page management platform based on a first account, wherein the page management platform is further used for configuring page access addresses for the page files in response to the address configuration instruction so as to complete file deployment, and the page access addresses of the page files corresponding to different services are different.
Optionally, the method further comprises:
displaying an alternative page file, wherein the alternative page file is a page file corresponding to the business to which the first account belongs;
And the page management platform is also used for taking the candidate page file indicated by the selection instruction as a file to be configured, and setting a page access address for the file to be configured according to the domain name and the access path indicated by the address configuration instruction.
Optionally, the displaying the candidate page file includes:
Displaying all page files included in a target file directory and/or displaying the target file directory;
and the paths associated with the target file catalogues are identical to or partially coincide with the access paths.
Optionally, the providing the page file corresponding to at least one service to the page management platform includes:
The method comprises the steps of providing a page file to be deployed to a preset interface based on a second account, wherein the page file is provided based on a target deployment mode selected from at least two preset deployment modes, and the preset interface is used for submitting the page file to the page management platform under the condition that the second account passes a first verification.
According to a third aspect of embodiments of the present disclosure, there is provided a pagefile processing apparatus, for use with a page management platform, the apparatus comprising:
The acquisition module is configured to execute acquisition of a page file corresponding to at least one service, and deploy the page file into a container pre-created by the page management platform;
The configuration module is configured to execute an address configuration instruction sent by the first account, configure a page access address for the page file to complete file deployment, and the page access addresses of the page files corresponding to different services are different.
Optionally, the configuration module is specifically configured to perform:
Responding to a selection instruction of the first account for an alternative page file, and taking the alternative page file indicated by the selection instruction as a file to be configured, wherein the alternative page file is a page file corresponding to a service to which the first account belongs;
and setting a page access address for the file to be configured according to the domain name and the access path indicated by the address configuration instruction.
Optionally, paths are associated with different page file catalogues in advance, the paths associated with the page file catalogues of the candidate page files are identical to the access paths or partially coincide with the access paths, and the paths associated with the page file catalogues corresponding to different services are different.
Optionally, the apparatus further includes:
A creation module configured to execute creating the container based on a preset container image;
The acquisition module is specifically configured to execute deploying the page file in the created container.
Optionally, the apparatus further includes:
The synchronization module is configured to perform synchronization of the current deployed page file, the page access address of the deployed page file and related information of the container;
The deployment module is configured to execute the process of redeploying the current deployed page file in the container according to the current deployed page file, the page access address of the deployed page file and the related information of the container after the page management platform is restarted.
Optionally, the acquiring module is further specifically configured to perform:
the method comprises the steps of receiving a page file submitted by a preset interface under the condition that a second account passes a first verification, wherein the page file is submitted to the preset interface by the second account in a target deployment mode, and the target deployment mode is selected from at least two preset deployment modes;
the device further comprises an execution module configured to execute a second verification on the preset interface and execute the operation of deploying the page file into a container pre-created by the page management platform if the second verification is passed.
According to a fourth aspect of the embodiments of the present disclosure, there is provided a pagefile processing apparatus, for application to a terminal, the apparatus including:
The system comprises a page management platform, a providing module, a service providing module and a service providing module, wherein the page management platform is used for deploying the page file into a container pre-created by the page management platform;
The system comprises a first sending module, a page management platform, a first service module and a second service module, wherein the first sending module is configured to send an address configuration instruction to the page management platform based on a first account, the page management platform is further used for configuring a page access address for the page file in response to the address configuration instruction so as to complete file deployment, and the page access addresses of the page files corresponding to different services are different.
Optionally, the apparatus further includes:
the display module is configured to execute displaying an alternative page file, wherein the alternative page file is a page file corresponding to a service to which the first account belongs;
The page management platform is further used for taking the candidate page file indicated by the selection instruction as a file to be configured, and setting a page access address for the file to be configured according to the domain name indicated by the address configuration instruction and the access path.
Optionally, the display module is specifically configured to perform:
Displaying all page files included in a target file directory and/or displaying the target file directory;
and the paths associated with the target file catalogues are identical to or partially coincide with the access paths.
Optionally, the providing module is specifically configured to perform:
The method comprises the steps of providing a page file to be deployed to a preset interface based on a second account, wherein the page file is provided based on a target deployment mode selected from at least two preset deployment modes, and the preset interface is used for submitting the page file to the page management platform under the condition that the second account passes a first verification.
According to a fifth aspect of embodiments of the present disclosure, there is provided a pagefile processing system, the system including a terminal and a page management platform;
the terminal is used for providing at least one page file corresponding to the service for the page management platform;
the page management platform is used for deploying the page file into a container pre-created by the page management platform;
the terminal is further used for sending an address configuration instruction to the page management platform based on the first account;
The page management platform is also used for responding to the address configuration instruction and configuring page access addresses for the page files so as to finish file deployment, and the page access addresses of the page files corresponding to different services are different.
According to a sixth aspect of embodiments of the present disclosure, there is provided an electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the method of any of the first aspects.
According to a seventh aspect of embodiments of the present disclosure, there is provided a storage medium, which when executed by a processor of an electronic device, causes the electronic device to perform the method of any one of the first aspects.
According to an eighth aspect of embodiments of the present disclosure, there is provided a computer program product comprising readable program instructions which, when executed by a processor of an electronic device, cause the electronic device to perform the method according to any one of the first aspects.
The technical scheme provided by the embodiment of the disclosure has the advantages that in the embodiment of the disclosure, the page file corresponding to at least one service can be obtained and deployed into the container pre-created by the page management platform. And responding to the address configuration instruction sent by the first account, configuring the page access address for the page file to finish file deployment, wherein the page access addresses of the page files corresponding to different services are different. In the embodiment of the disclosure, the page management platform is used as a public service to uniformly provide deployment services for all the businesses, and the page files corresponding to all the businesses can be uniformly deployed to the page management platform. Therefore, a fixed amount of hardware resources are not required to be applied for the service, and resource waste can be avoided to a certain extent.
And only the page files to be deployed are required to be provided, and the page management platform is directly deployed based on the container which is created in advance, so that the container mirror image is not required to be constructed, the deployment time can be reduced to a certain extent, and the deployment efficiency is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
FIG. 1 is a flow chart illustrating a method of processing a pagefile, which may be applied to a page management platform, according to an exemplary embodiment, as shown in FIG. 1, the method may include:
and 101, acquiring a page file corresponding to at least one service, and deploying the page file into a container pre-created by the page management platform.
In the embodiment of the disclosure, the page file may be an executable file obtained by converting source code. Illustratively, the page file may be a static web page file, the file type of the page file may be html, the page file may represent pages of an online web page, pages of an online e-book, and so forth. That is, the pages of the online e-book are implemented based on the web page file. In one implementation, the source code generated in the front-end development may be structured, i.e., converted into a browser executable file, resulting in a pagefile. The page file corresponding to the service refers to a page file created for realizing the service, wherein the service can be defined in advance according to actual requirements. For example, a service may be defined according to a function to be provided, and a page file created for each service may be used to implement a function corresponding to the service. Assuming that the function corresponding to service a is a history presentation function, the page file corresponding to service a may be used to provide a page displaying a history.
The page management platform may be a server cluster, and the deployment operation may also be referred to as a publishing and online operation, where the deployment operation specifically refers to an operation of uploading a build product, i.e., a page file, to a server. The page management platform in the embodiment of the disclosure may be used for deploying page files corresponding to each service, and the page management platform may be used for providing page hosting services for a plurality of services, that is, page files corresponding to the plurality of services may be uniformly deployed to the page management platform. By deploying the page file into the container, the page file can be released to the page management platform in a container mode, and a container engine can be installed in the page management platform so as to normally run the page file, thereby ensuring that a user can normally access the page.
And 102, responding to an address configuration instruction sent by the first account, and configuring a page access address for the page file to finish file deployment, wherein the page access addresses of the page files corresponding to different services are different.
In the embodiment of the disclosure, the first account may be an account with the operation authority of the page file, and illustratively, the first account may be an account of a creator or a collaborator of the page file. The address configuration instructions may be used to route the deployed page file, i.e., set a page access address that may be used to access the page file. After route configuration is performed for the deployed page file, the file deployment operation can be completed.
When the method is specifically configured, the page access addresses configured for the page files corresponding to different services are different, so that the page files corresponding to a plurality of services can be deployed to the same platform, and meanwhile, conflicts among the different services can be avoided to a certain extent. Of course, the page access addresses of different page file configurations corresponding to the same service may also be different, so as to avoid access conflicts. Of course, the page access address can also be returned to the terminal logging in the first account, so that the user can conveniently and quickly acquire the configuration result.
In summary, the method for processing a page file according to the embodiment of the present disclosure may obtain a page file corresponding to at least one service, and deploy the page file to a container created in advance by a page management platform. And responding to the address configuration instruction sent by the first account, configuring the page access address for the page file to finish file deployment, wherein the page access addresses of the page files corresponding to different services are different. In the embodiment of the disclosure, the page management platform is used as a public service to uniformly provide deployment services for all the businesses, and the page files corresponding to all the businesses can be uniformly deployed to the page management platform. Therefore, a fixed amount of hardware resources are not required to be applied for the service, and resource waste can be avoided to a certain extent.
And only the page files to be deployed are required to be provided, and the page management platform is directly deployed based on the container which is created in advance, so that the container mirror image is not required to be constructed, the deployment time can be reduced to a certain extent, and the deployment efficiency is improved.
Optionally, the operation of configuring the page access address for the page file in response to the address configuration instruction sent by the first account may specifically include:
And step S21, responding to a selection instruction of the first account for the candidate page file, and taking the candidate page file indicated by the selection instruction as a file to be configured, wherein the candidate page file is a page file corresponding to a service to which the first account belongs.
Specifically, the candidate page file may be a page file deployed in the container in a page file corresponding to the service to which the first account belongs. The service to which the first account belongs may be a service to which the first account has operation authority, for example, the service to which the first account belongs may be a service to which the first account is responsible for processing in the department to which the first account belongs. In the embodiment of the disclosure, the alternative page file can be taken as a selection object for the first account to select. The selection instruction of the first account for the candidate page file may be triggered by a selection operation on the candidate page file, where the selected candidate page file is the candidate page file indicated by the selection instruction. Because the candidate page files are page files corresponding to the business to which the first account belongs, the page files corresponding to other businesses are prevented from being displayed to the first account, and service isolation among different businesses is ensured, namely, in a deployment link, the page files corresponding to the different businesses are only checked by the account responsible for the business, so that the problem of information leakage among the different businesses can be avoided.
It should be noted that, in the embodiment of the present disclosure, a container may be deployed with a page file corresponding to at least one service. Because the page files corresponding to the businesses are uniformly managed by the page management platform and the businesses are isolated, the page files corresponding to a plurality of businesses can be deployed in the same container, thereby improving the resource utilization rate.
And S22, setting a page access address for the file to be configured according to the domain name indicated by the address configuration instruction and the access path.
In this step, the domain name indicated by the address configuration instruction and the access path may be set by the first account according to actual requirements. The page access address can be generated according to the domain name indicated by the address configuration instruction and the access path, the route configuration information is generated according to the page access address, and the route configuration information is written into the address configuration file of the page management platform. For example, the page management platform may be deployed with an nginx service, and may store the corresponding relationship between the file information of the file to be configured and the page access address as route configuration information in the address configuration file. The page management platform can be further configured with a node service, wherein the operations of generating the page access address and writing the corresponding relation between the identification of the file to be configured and the page access address as the route configuration information can be realized by the node service. The address profile may be "nginx. Thus, after the page file is deployed to the container, the route is configured, i.e., the page access address is generated using the specific domain name plus the specified access path, so that the page of the service deployment can be accessed.
In the embodiment of the disclosure, a selection instruction of a first account for an alternative page file is responded, the alternative page file indicated by the selection instruction is used as a file to be configured, and the alternative page file is a page file corresponding to a service to which the first account belongs. And setting a page access address for the file to be configured according to the domain name and the access path indicated by the address configuration instruction. Therefore, the page access address configuration can be realized to a certain extent, and the page files corresponding to other services are prevented from being displayed to the first account, so that the problem of information leakage among different services is avoided.
Optionally, paths are associated with different page file catalogues in advance, the paths associated with the page file catalogues of the candidate page files are identical to the access paths or partially coincide with the access paths, and the paths associated with the page file catalogues corresponding to different services are different. In the disclosed embodiment, each route has a specified service directory, i.e., each path association corresponds to a pagefile directory. In the page management platform, the page files may be divided according to the directory, and a specific directory division manner may be set according to actual requirements, which is not limited in the embodiments of the present disclosure. Illustratively, the directory partitioning may be done by department + business name. For example, a directory is partitioned for a department + business name composition. FIG. 2 is a diagram of a directory, as shown in FIG. 2, where resource files may refer to pagefiles and resource directories may refer to pagefile directories, according to an example embodiment. The path associated with the page file directory may be set according to actual requirements, for example, the directory path of the page file directory in the page management platform may be set as the associated path, or the name of the page file directory may be set as the associated path.
Specifically, in the case where the path associated in advance with the page file directory is identical to the content of the access path, the page file under the page file directory may be used as the candidate page file. Or in the case that the pre-associated path of the page file directory is the same as the content existence part of the access path, the page file under the page file directory is used as the candidate page file. When generating the page access address according to the domain name and the access path indicated by the address configuration instruction, the domain name and the access path indicated by the address configuration instruction and the path of the selected candidate page file may be specifically used as the page access address. Or the domain name plus the access path can be directly used as the page access address.
Because the same domain name may be adopted when the page access address is configured for the page files of different services, in the embodiment of the disclosure, paths associated with the page file directories corresponding to different services are different, so that adverse effects caused by route coverage when different services use the same domain name can be avoided to a certain extent. Specifically, when different services use the same domain name, whether the associated path has a superposition part with the path indicated by the associated instruction or not is detected in response to the received associated instruction, wherein the associated path is the path currently associated with the page file directory corresponding to other services. The presence of the overlap portion may refer to the content presence of partial/full repetition of both. If no overlap exists, the path indicated by the associated instruction is associated with the pagefile directory indicated by the associated instruction. In this way, by performing conflict verification, it can be ensured that the routing prefix does not have any inclusion relationship, thereby ensuring the security of routing configuration. Wherein a routing prefix may refer to an associated path.
In the embodiment of the disclosure, when the paths associated with the directory are identical to the access paths or partially overlap with the access paths, files in the directory are used as candidate page files, because the paths associated with the page file directories corresponding to different services are different, the paths associated with the different services can be ensured not to have any inclusion relationship, and thus information leakage among the different services can be further avoided.
It should be noted that, in the embodiment of the present disclosure, authority control may also be performed, specifically, the production environment routing configuration may be modified in response to the modification instruction only when the first account is the project manager account, and the routing configuration may be updated after the current audit account is audited. Wherein, in response to the modification instruction, the production environment routing configuration is modified, which may be to modify the page access address of the page file indicated by the modification instruction, and update 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.
Optionally, before the page file is deployed into the container pre-created by the page management platform, the method may further include the step of creating the container based on the preset container image in step S31. Correspondingly, the step of deploying the page file into a container pre-created by the page management platform can specifically comprise the step of deploying the page file in the created container. The container mirror image may be deployed in the page management platform after the page management platform is built, and illustratively, the container mirror image may be deployed in the page management platform before the page file sent by the terminal is received. Accordingly, the container may be built based on the container image, e.g., a preset create command may be used to build the container based on the container image for use in subsequent deployments. In the embodiment of the disclosure, the container mirror image is preset in the page management platform, and the container is created in advance. Therefore, by directly arranging the page file in the created container, the time consumption for starting the container can be reduced to a certain extent, the time consumption for arranging the page file is reduced, and the arrangement efficiency is improved.
Optionally, in an embodiment of the present disclosure, the following steps may be further performed:
Step S41, synchronizing the current deployed page file, the page access address of the deployed page file and the related information of the container.
In the embodiment of the disclosure, synchronization can be performed at the stage of cold start when the page management platform expands or receives a restart instruction. Specifically, the current deployed page files and the route configuration information corresponding to each deployed page file can be synchronized, so as to realize synchronization of page access addresses. The container where the deployed page file is located may be a container where the page file is deployed, and the related information of the container may be a service address corresponding to the current cluster, and specifically may be an IP address and port information of an instance corresponding to the container. For example, the data may be synchronized to a preset storage device.
Step S42, after the page management platform is restarted, redeploying the current deployed page file in the container according to the current deployed page file, the page access address of the deployed page file and the related information of the container.
In particular, the synchronized pagefiles may be redeployed in the page management platform, in particular, the containers in which the currently deployed pagefiles were located before may be located according to the relevant information of the containers, and then the currently deployed pagefiles may be redeployed in these containers to avoid omission. And generating route configuration information according to the synchronous page access address, and writing the route configuration information into an address configuration file of the page management platform, thereby completing redeployment operation.
In the embodiment of the disclosure, the current deployed page file, the page access address of the deployed page file and the related information of the container are synchronized. After restarting the page management platform, redeploying the current deployed page file in the container according to the current deployed page file, the page access address of the deployed page file and the related information of the container. Therefore, the consistency of the states before and after restarting of the page management platform can be ensured to a certain extent, and the problem of missing deployment is avoided.
Optionally, the operation of obtaining the page file corresponding to the at least one service may specifically include step S51, receiving the page file submitted by the preset interface when the second account passes the first verification, where the page file is submitted by the second account to the preset interface in a target deployment manner, and the target deployment manner is selected from at least two preset deployment manners.
Accordingly, before the above-mentioned deployment of the page file into the container pre-created by the page management platform, the embodiment of the disclosure may further execute the step of performing a second verification on the preset interface in step S61, and executing the operation of deploying the page file into the container pre-created by the page management platform if the second verification is passed.
Specifically, the second account may be the same as the first account described above, or may be different. The first verification and the second verification may be set according to actual requirements, and the complexity of the first verification may be higher than the complexity of the second verification. The first verification may be to verify whether the second account is legal, whether the second account has an operation right, and whether the current time is at an operable time. If so, it may be determined that the second account is authenticated by the first authentication. Accordingly, after the second account issues the deployment instruction, the second account may be authenticated, i.e., first verified, by the preset interface. If the second account passes the first verification, the preset interface can submit the page file to be deployed to the page management platform. Authentication is performed again through a second verification in the page management platform, wherein the second verification can be to verify whether a preset interface of the current submitted page file is a pre-authorized interface service. If so, the preset interface can be determined to pass the second verification, and then the page file can be deployed to the page management platform.
In the embodiment of the disclosure, the safety of deployment can be ensured to a certain extent through double authentication verification. Meanwhile, the second account is verified by the preset interface, and the page management platform can determine the rationality of the current deployment only by verifying the preset interface, so that the burden of the page management platform can be reduced to a certain extent.
Further, at least two preset deployment modes can be set according to actual requirements, and the preset deployment modes can be page file submission modes supported by a page management platform. Illustratively, the preset deployment may include a preset plug-in based deployment, a command line based tool deployment, and a specified platform based deployment. The preset plugin may be a persistent integration (Continuous Integration, CI)/persistent deployment (Continuous Deployment, CD) platform deployment plugin, and the specified platform may be a static hosting platform. FIG. 3 is a schematic diagram of a deployment that may be illustrated in accordance with an exemplary embodiment, as illustrated in FIG. 3, where a user may perform project build packaging on a developed project to obtain a pagefile and then publish the pagefile in accordance with the three provided deployments to the page processing platform. After the api service authentication, the system can be deployed to a public static service. The api service may correspond to the preset receiving service, and the public static service may correspond to the page processing platform. In the embodiment of the disclosure, by providing a plurality of preset deployment modes, the second account can select the target deployment mode based on actual requirements, so that subsequent deployment and release can be conveniently and rapidly performed, and the service scenarios of different services can be met to a certain extent.
FIG. 4 is a flowchart illustrating another method of pagefile processing that may be applied to a terminal, as shown in FIG. 4, according to one exemplary embodiment, the method may include:
and step 201, providing at least one page file corresponding to the service for a page management platform, wherein the page management platform is used for deploying the page file into a container pre-created by the page management platform.
The terminal can be multiple, and one terminal can be used for providing one or more page files corresponding to the service.
And 202, sending an address configuration instruction to the page management platform based on the first account, wherein the page management platform is further used for configuring page access addresses for the page files in response to the address configuration instruction so as to complete file deployment, and the page access addresses of the page files corresponding to different services are different.
In summary, according to the method for processing a page file provided by the embodiment of the present disclosure, the terminal may provide a page file corresponding to at least one service to the page management platform and send an address configuration instruction based on the first account. So that the page management platform can deploy the page file into a container pre-created by the page management platform. And responding to the address configuration instruction sent by the first account, configuring the page access address for the page file to finish file deployment, wherein the page access addresses of the page files corresponding to different services are different. In the embodiment of the disclosure, the page management platform is used as a public service to uniformly provide deployment services for all the businesses, and the page files corresponding to all the businesses can be uniformly deployed to the page management platform. Therefore, a fixed amount of hardware resources are not required to be applied for the service, and resource waste can be avoided to a certain extent.
And only the page files to be deployed are required to be provided, and the page management platform is directly deployed based on the container which is created in advance, so that the container mirror image is not required to be constructed, the deployment time can be reduced to a certain extent, and the deployment efficiency is improved.
Optionally, the operation of providing the page file corresponding to the at least one service to the page management platform specifically includes providing the page file to be deployed to a preset interface based on a second account, where the page file is provided based on a target deployment mode selected from at least two preset deployment modes, and the preset interface is configured to submit the page file to the page management platform when the second account passes the first verification. In the embodiment of the disclosure, by providing a plurality of preset deployment modes, the second account can select the target deployment mode to perform subsequent deployment and release based on actual requirements, so that the use scenes of different services can be met to a certain extent. And the second account is verified by the preset interface, so that the page management platform can determine the rationality of the deployment only by verifying the preset interface, thereby reducing the burden of the page management platform to a certain extent.
Optionally, in the embodiment of the present disclosure, the method may further include displaying an alternative page file, where the alternative page file is a page file corresponding to a service to which the first account belongs, responding to a selection operation of the alternative page file, and sending a selection instruction to the page management platform, where the page management platform is further configured to use the alternative page file indicated by the selection instruction as a file to be configured, and set a page access address for the file to be configured according to a domain name and an access path indicated by the address configuration instruction. Specifically, the terminal may display a visual interface in which to display the candidate page file for selection by the first account. Corresponding to the foregoing example in fig. 2, the route configuration link restriction may only access the file under < department bu > _ < service app > to which the first account belongs, and isolation between services is achieved from the route perspective, so as to ensure that different services do not affect each other.
The first account can also set a domain name and an access path in the interface to trigger the terminal to send an address configuration instruction based on the first account. The domain name and the access path are set in the interface, namely the domain name and the access path indicated by the address configuration instruction. For example, the selectable domain name and the access path may be displayed in the interface, where the domain name and the access path selected by the first account are used as the domain name and the access path indicated by the address configuration instruction. Or an input box can be provided in the interface, and the domain name and the access path input by the first account are used as the domain name and the access path indicated by the address configuration instruction. In the embodiment of the disclosure, the page processing platform supports generating the page route forwarding rule through the visualized operation, and freely customizes the route access of the page level, namely, the page access address of the page file can be defined through the visualized operation. Therefore, compared with the mode of contacting operation staff and defining by the operation staff through modifying the configuration rules, the configuration can be completed based on the visual interface in the embodiment of the disclosure, so that the cost can be reduced to a certain extent and the communication time can be saved.
In the embodiment of the disclosure, the alternative page file can be displayed as a selection object for the first account to select. Because the candidate page files are page files corresponding to the business to which the first account belongs, the page files corresponding to other businesses are prevented from being displayed to the first account, and service isolation among different businesses is ensured, namely, in a deployment link, the page files corresponding to the different businesses are only checked by the account responsible for the business, so that the problem of information leakage among the different businesses can be avoided.
Optionally, the operation of displaying the candidate page file may specifically include step S71 of displaying all page files included in a target file directory and/or displaying the target file directory, where paths are associated with different page file directories in advance, and the paths associated with the target file directory are identical to or partially overlap with the access paths. Specifically, when the content of the access path is identical to the content of the access path in the page file directory, or when the content of the access path is partially identical to the content of the access path in the page file directory, the page file directory may be returned directly to display, or the target file directory may be returned directly to display in the form of a directory. Therefore, the requirement of the second account can be fully met by providing diversified display modes.
Illustratively, taking the page management platform as an example, the nginx service is adopted, three types of route configuration templates can be provided in the embodiment of the disclosure to meet different front-end service requirements. In the routing template 1, when the target page is accessed by the appointed prefix, the target page is searched under the appointed file directory. In the routing template 2, when the access is performed with the specified prefix, the specified file is returned. In the routing template 3, when the access is performed in a specified path, a specified file is returned. When the access is performed with the appointed prefix, the search for the target page under the appointed file directory can correspond to returning to the target file directory under the condition that the pre-associated path of the page file directory is the same as the content existence part of the access path. When accessing with the specified prefix, returning the specified file may correspond to returning the page file in the case where the path associated in advance with the page file directory is the same as the content-existing portion of the access path. When accessing in the designated path, returning the designated file may correspond to returning the page file if the path associated in advance with the page file directory is identical to the contents of the access path. The defining mode of the routing template can be set according to actual requirements, and the routing template 1 can be defined as #case: prefix match, rewrite to folder. The routing template 2 may be defined as #case: prefix match rewrite to file. The routing template 3 may be defined as #case: equivalent match rewrite to file. The "location" in the routing template 1 may be set to < user access prefix > { alias/data/nginx/html/< department bu > _ < business app >/latest/specified file directory, the "location" in the routing template 2 may be set to < user access prefix > { root/data/nginx/html/< department bu > _ < business app >/latest/< department bu >/html/< department bu >/may be set to < user access address > root/data/nginx/html/< department bu >/business app >/department/.
In one application scenario, the page file may be a static web page in front-end engineering, the page processing platform may be a static service cluster based on a dock (container), and the front-end pages may be deployed to the cluster. Embodiments of the present disclosure are described below in an exemplary architecture. Fig. 5 is a schematic architecture diagram of a page processing platform according to an exemplary embodiment, where, as shown in fig. 5, the platform includes an nginx service and a node service, where the nginx service may be used as an external traffic portal to implement a basic static service. The configuration of the catalogs and the paths can be carried out based on the Nginx service, different services can be distinguished through the paths in the Nginx service, namely, different paths are associated for the catalogs of the different services, and under the routing configuration function, the account accessible catalogs are limited, so that the effect of isolation among the services is achieved, and the page management platform is used as a public static page hosting service and can have the capability of bearing static pages of the different services. node services can be used to achieve dynamic quick deployment of static pages, route dynamic configuration updates, and cold start resource synchronization. The nginnx service is used as a traffic entry, the page file may be submitted to the nginnx service first, and then the nginnx service gives the node service, and the node service performs the operations of second verification, deployment, synchronization, generation of the page access address, and writing into the configuration file of the nginnx, so as to implement address configuration and the like. Specifically, the node service can deploy the page file into a pre-created container, so that dynamic quick deployment is realized, the problem of overlong time caused by mirror image online is avoided, and quick release and rollback can be supported. And by providing routing configuration capability, the access path of the static page can be conveniently managed. The routing dynamic configuration update may refer to the foregoing operation of configuring the page access address, the cold start resource synchronization may refer to the foregoing synchronization operation, the cluster information storage may refer to synchronization related information, the static page resource synchronization may refer to synchronizing the currently deployed page file, and the routing configuration synchronization may refer to synchronizing the page access address of the deployed page file.
It should be noted that, the nginx service may also use other services instead, such as node service, which is not limited by the embodiments of the present disclosure.
Further, the page processing platform may pre-perform static service image deployment container cloud, i.e., pre-build container images in the page processing platform, creating containers. Container health checks may also be performed. The static service is based on the container cloud, and the service stability can be better ensured by utilizing the health examination, service management and dynamic capacity expansion and contraction capabilities of the container cloud. A container cloud refers to a server on which a container engine is installed.
In a related technology, under the conditions that various services are gradually containerized and the container environment and front and back ends are separated, as the container is isolated and has no state, each front-end engineering needs to apply for independent at least 1-core 1G dual-machine room service resources, so as to construct a container mirror image, construct the container based on the container mirror image, and then deploy one to a plurality of html files in one service. However, for static page files, the container actually acts only to render html files, thus resulting in lower resource utilization. Meanwhile, a large number of front-end projects are independently applied and deployed, so that more service nodes are maintained in the later period, and further, the service maintenance cost is high. In addition, the time cost is high in the deployment mode, and when an emergency problem occurs and online correction is needed, the time is often longer.
In the embodiment of the disclosure, a front-end-oriented static page hosting service is provided, deployment services are uniformly provided for each service, and page files corresponding to each service can be uniformly deployed to a page management platform.
The business does not need to pay attention to resource application and maintenance, so that service resources and maintenance cost can be saved. And because the mirror image is not required to be constructed under the condition of receiving the page file to be deployed, the server is restarted. Therefore, quick deployment can be realized, and the online deployment efficiency is improved.
FIG. 6 is a block diagram illustrating a pagefile processing apparatus that may be applied to a page management platform, according to an exemplary embodiment, as shown in FIG. 6, the apparatus 30 may include:
the acquiring module 301 is configured to perform acquiring a page file corresponding to at least one service, and deploy the page file into a container pre-created by the page management platform;
the configuration module 302 is configured to execute an address configuration instruction sent by responding to the first account, configure a page access address for the page file to complete file deployment, and the page access addresses of the page files corresponding to different services are different.
In summary, the device for processing a page file provided in the embodiment of the present disclosure may obtain a page file corresponding to at least one service, and deploy the page file to a container created in advance by a page management platform. And responding to the address configuration instruction sent by the first account, configuring the page access address for the page file to finish file deployment, wherein the page access addresses of the page files corresponding to different services are different. In the embodiment of the disclosure, the page management platform is used as a public service to uniformly provide deployment services for all the businesses, and the page files corresponding to all the businesses can be uniformly deployed to the page management platform. Therefore, a fixed amount of hardware resources are not required to be applied for the service, and resource waste can be avoided to a certain extent. And only the page files to be deployed are required to be provided, and the page management platform is directly deployed based on the container which is created in advance, so that the container mirror image is not required to be constructed, the deployment time can be reduced to a certain extent, and the deployment efficiency is improved.
In an alternative embodiment, the configuration module 302 is specifically configured to perform:
Responding to a selection instruction of the first account for an alternative page file, and taking the alternative page file indicated by the selection instruction as a file to be configured, wherein the alternative page file is a page file corresponding to a service to which the first account belongs;
and setting a page access address for the file to be configured according to the domain name and the access path indicated by the address configuration instruction.
In an alternative embodiment, paths are pre-associated with different page file directories, paths associated with page file directories to which the candidate page file belongs are identical to or partially overlap with the access paths, and paths associated with page file directories corresponding to different services are different.
In an alternative embodiment, the apparatus 30 further comprises:
A creation module configured to execute creating the container based on a preset container image;
The acquisition module 301 is specifically configured to execute deploying the pagefile in the created container.
In an alternative embodiment, the apparatus 30 further comprises:
The synchronization module is configured to perform synchronization of the current deployed page file, the page access address of the deployed page file and related information of the container;
The deployment module is configured to execute the process of redeploying the current deployed page file in the container according to the current deployed page file, the page access address of the deployed page file and the related information of the container after the page management platform is restarted.
In an alternative embodiment, the obtaining module 301 is further specifically configured to perform:
the method comprises the steps of receiving a page file submitted by a preset interface under the condition that a second account passes a first verification, wherein the page file is submitted to the preset interface by the second account in a target deployment mode, and the target deployment mode is selected from at least two preset deployment modes;
the device further comprises an execution module configured to execute a second verification on the preset interface and execute the operation of deploying the page file into a container pre-created by the page management platform if the second verification is passed.
Fig. 7 is a block diagram illustrating another pagefile processing apparatus according to an exemplary embodiment, the apparatus being applied to a terminal, and the apparatus 40 may include:
a providing module 401 configured to execute providing a page file corresponding to at least one service to the page management platform; the page management platform is used for deploying the page file into a container pre-created by the page management platform;
The first sending module 402 is configured to send an address configuration instruction to the page management platform based on the first account, where the page management platform is further configured to configure a page access address for the page file in response to the address configuration instruction, so as to complete file deployment, and page access addresses of page files corresponding to different services are different.
In summary, the device for processing a page file provided in the embodiment of the present disclosure may provide a page file corresponding to at least one service to a page management platform and send an address configuration instruction based on a first account. So that the page management platform can deploy the page file into a container pre-created by the page management platform. And responding to the address configuration instruction sent by the first account, configuring the page access address for the page file to finish file deployment, wherein the page access addresses of the page files corresponding to different services are different. In the embodiment of the disclosure, the page management platform is used as a public service to uniformly provide deployment services for all the businesses, and the page files corresponding to all the businesses can be uniformly deployed to the page management platform. Therefore, a fixed amount of hardware resources are not required to be applied for the service, and resource waste can be avoided to a certain extent. And only the page files to be deployed are required to be provided, and the page management platform is directly deployed based on the container which is created in advance, so that the container mirror image is not required to be constructed, the deployment time can be reduced to a certain extent, and the deployment efficiency is improved.
In an alternative embodiment, the apparatus 40 further comprises:
the display module is configured to execute displaying an alternative page file, wherein the alternative page file is a page file corresponding to a service to which the first account belongs;
The page management platform is further used for taking the candidate page file indicated by the selection instruction as a file to be configured, and setting a page access address for the file to be configured according to the domain name indicated by the address configuration instruction and the access path.
In an alternative embodiment, the display module is specifically configured to perform:
Displaying all page files included in a target file directory and/or displaying the target file directory;
and the paths associated with the target file catalogues are identical to or partially coincide with the access paths.
In an alternative embodiment, the providing module 401 is specifically configured to perform:
The method comprises the steps of providing a page file to be deployed to a preset interface based on a second account, wherein the page file is provided based on a target deployment mode selected from at least two preset deployment modes, and the preset interface is used for submitting the page file to the page management platform under the condition that the second account passes a first verification.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
According to one embodiment of the disclosure, a system for processing the page file is provided, and comprises a terminal and a page management platform, wherein the terminal is used for providing at least one page file corresponding to a service for the page management platform, the page management platform is used for deploying the page file into a container pre-created by the page management platform, the terminal is further used for sending an address configuration instruction to the page management platform based on a first account, the page management platform is further used for responding to the address configuration instruction to configure a page access address for the page file so as to complete file deployment, and the page access addresses of the page files corresponding to different services are different.
The method for processing the page file corresponding to the page file processing system may include the step S81 of providing, by the terminal, the page file corresponding to at least one service to the page management platform. And step S82, the page management platform deploys the page file into a container pre-created by the page management platform. And step S83, the terminal sends an address configuration instruction to the page management platform based on the first account. And S84, the page management platform responds to the address configuration instruction to configure the page access address for the page file so as to finish file deployment, wherein the page access addresses of the page files corresponding to different services are different.
According to one embodiment of the present disclosure, there is provided an electronic device comprising a processor, a memory for storing processor-executable instructions, wherein the processor is configured to perform steps in a method of processing a page file as in any of the embodiments described above.
According to an embodiment of the present disclosure, there is also provided a storage medium, which when executed by a processor of an electronic device, enables the electronic device to perform the steps of the method of page file processing as in any of the embodiments described above.
According to an embodiment of the present disclosure, there is also provided a computer program product comprising readable program instructions which, when executed by a processor of an electronic device, enable the electronic device to perform the steps of the method of page file processing as in any of the embodiments described above.
FIG. 8 is a block diagram illustrating an apparatus for pagefile processing according to an exemplary embodiment. The apparatus 700 may include, among other things, 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 perform all or part of the steps of the pagefile processing method described above. In an exemplary embodiment, a storage medium is also provided, such as a memory 704 including instructions executable by the processor 720 of the apparatus 700 to perform the above-described method. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
FIG. 9 is a block diagram illustrating another apparatus for pagefile processing according to an exemplary embodiment. The apparatus 800 may include, among other things, a processing component 822, a memory 832, an input-output interface 858, a network interface 850, and a power component 826. The apparatus 800 may be provided as a server. The application programs stored in memory 832 may include one or more modules each corresponding to a set of instructions. Further, the processing component 822 is configured to execute instructions to perform the above-described pagefile processing methods.
User information (including but not limited to user equipment information, user personal information, etc.), related data, etc. related to the present disclosure are all information authorized by the user or authorized by the parties.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.