Offline development environment deployment method and device, equipment and storage medium

Abstract

The embodiment of the invention provides an offline development environment deployment method and device, equipment and a storage medium, and relates to the field of financial science and technology or other related fields. The method comprises the steps of displaying a workflow corresponding to a to-be-deployed environment on a main interface in response to a received first operation, then determining target configuration information of the to-be-deployed environment in response to a received second operation, and completing offline deployment of the to-be-deployed environment based on the target configuration information and configuration steps. According to the method, the problem that the program development environment is difficult to effectively deploy in the intranet offline environment is effectively solved, the operation and maintenance cost of development environment deployment is reduced by providing an automatic and visual deployment mode, the limitation and network dependence of a traditional scheme are overcome, and the deployment efficiency and the user experience are improved.

Description

Technical Field

[0001] The present application relates to the field of financial technology or other related fields, and in particular to an offline development environment deployment method, device, equipment and storage medium. Background Art

[0002] The background of rapid deployment technology for development environments stems from the demand for efficient, reliable, and rapid deployment processes in modern software development and operation and maintenance, especially driven by cloud computing, microservice architecture, containerization technology, and DevOps practices. This technology is particularly important in development environments because it can provide developers with a pre-configured, unified development and testing environment, allowing developers to start working immediately without spending time installing and configuring various software and tools. This convenience and efficiency improvement is of great significance for accelerating development cycles and improving productivity.

[0003] Among the related technologies, there are still some technical problems in the rapid deployment technology of the development environment. Especially in enterprises with high confidentiality requirements, which are usually in an internal network state closed to the outside world, it is inconvenient to use technologies such as cloud services and online development environment configuration, and it is difficult to adjust the one-click deployment tools that come with software development tools, which will seriously affect the effective deployment of the program development environment. Summary of the invention

[0004] The present application provides an offline development environment deployment method, device, equipment, storage medium and product, which are used to solve the problem in the related art that the program development environment is difficult to effectively deploy in an intranet offline environment.

[0005] In a first aspect, the present application provides an offline development environment deployment method, comprising:

[0006] In response to the received first operation, displaying a workflow corresponding to the environment to be deployed on the main interface, the workflow including configuration steps of the development environment and offline dependency files corresponding to the configuration steps, the configuration steps being used to set configuration parameters corresponding to the current development environment or to install offline dependency files required for the development environment;

[0007] In response to the received second operation, determining target configuration information of the environment to be deployed, the target configuration information including a target deployment address;

[0008] Complete offline deployment of the environment to be deployed based on the target configuration information and configuration steps.

[0009] In a second aspect, the present application provides an offline development environment deployment device, comprising:

[0010] An editing module, for displaying a workflow corresponding to the environment to be deployed on a main interface in response to the received first operation, wherein the workflow includes configuration steps of the development environment and offline dependent files corresponding to the configuration steps, wherein the configuration steps are used to set configuration parameters corresponding to the current development environment or to install offline dependent files required for the development environment;

[0011] an indication module, configured to determine target configuration information of the to-be-deployed environment in response to the received second operation, wherein the target configuration information includes a target deployment address;

[0012] The processing module is used to complete the offline deployment of the environment to be deployed based on the target configuration information and configuration steps.

[0013] In a third aspect, an embodiment of the present application provides an electronic device, including: a memory, a processor;

[0014] The memory stores computer-executable instructions;

[0015] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the above first aspect and / or various possible implementations of the first aspect.

[0016] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the first aspect above and / or various possible implementations of the first aspect.

[0017] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above first aspect and / or various possible implementation methods of the first aspect.

[0018] The offline development environment deployment method, apparatus, device and storage medium provided by the embodiments of the present disclosure display the corresponding workflow of the environment to be deployed on the main interface in response to the first operation received, and then determine the target configuration information of the environment to be deployed in response to the second operation received, and then complete the offline deployment of the environment to be deployed based on the target configuration information and configuration steps. Thus, by displaying the workflow of the environment to be deployed on the main interface and combining the target configuration information, the deployment process of the development environment is simplified, and rapid deployment of the development environment is achieved. By responding to the user's operation, the solution can automatically determine the configuration steps, the corresponding offline dependency files, and the target configuration information, thereby achieving fast and flexible environment configuration and deployment. This automated and visual deployment method reduces the cost of use and maintenance, overcomes the limitations and network dependence of traditional solutions, and improves deployment efficiency and user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0020] Figure 1 An application scenario diagram of the offline development environment deployment method provided in the embodiment of the present disclosure;

[0021] Figure 2 A flowchart of an offline development environment deployment method provided by an embodiment of the present disclosure;

[0022] Figure 3a A flowchart of an offline development environment deployment method provided by yet another embodiment of the present disclosure;

[0023] Figure 3b for Figure 3a A schematic diagram of a main interface including a workflow provided by the illustrated embodiment;

[0024] Figure 3c for Figure 3a A schematic diagram of the structure of the configuration interface provided by the illustrated embodiment;

[0025] Figure 4 A schematic diagram of the structure of an offline development environment deployment device provided by another embodiment of the present disclosure;

[0026] Figure 5 A schematic diagram of the structure of an electronic device provided by one embodiment of the present disclosure.

[0027] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0028] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0029] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant countries and regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0030] In addition, this application involves conducting big data analysis of user information (including but not limited to personal biometrics, identity data, consumption data, asset data, electronic terminal operation data, etc.), and using artificial intelligence technology to make automated decisions, and making technical solutions that have a significant impact on personal rights and interests based on the results of automated decisions. The application provides users with corresponding operation entrances for them to choose to agree or reject the results of automated decisions; if the user chooses to reject, the expert decision-making process will be entered.

[0031] It should be noted that the methods, devices, equipment, storage media and products for offline development environment deployment provided in this application can be used in the field of financial technology, and can also be used in any field other than the field of financial technology. The application fields of the methods, devices, equipment, storage media and products for offline development environment deployment in this application are not limited.

[0032] Figure 1 A schematic diagram of an application scenario of the offline development environment deployment method provided for this application, such as Figure 1 As shown, during the offline development environment deployment process, the user can deploy the corresponding configuration parameters and dependent files of the development environment to the target computer 110 at the target deployment address through the development environment deployment program 100, and the entire process does not require an Internet connection, and the offline development environment deployment process can be automatically completed.

[0033] It should be noted that Figure 1 The scenario shown includes a development environment deployment program, and only one or a specific number of target computers are used as examples for illustration, but the present disclosure is not limited to this, that is, the number of development environment deployment programs and target computers can be arbitrary.

[0034] In modern software development environments, with the popularity of cloud computing, microservice architecture, containerization technology, and DevOps practices, development and operation teams are facing increasingly complex deployment requirements. However, in certain specific intranet environments, cloud networking cannot be achieved due to security and data privacy considerations. This limitation makes it difficult to apply traditional one-click deployment solutions based on cloud services. In intranet environments, developers still need an efficient and reliable deployment process to quickly configure and manage the development environment. Development tools in this environment need to be able to provide cloud-like convenience and automation capabilities without external network connections to ensure that developers can focus on code writing and testing without having to worry about the complexity of environment configuration.

[0035] In the above scenario, since the configuration and deployment of the development environment need to rely entirely on local resources, it is easy to cause duplication and waste of resources. And due to the lack of cloud support, the one-click deployment function of the development tool may not meet the needs of complex environments, especially when multiple technology stacks and platforms are involved. In addition, online IDEs and code editors cannot be used in intranet environments because they rely on continuous network connections, which limits developers' tool selection and usage scenarios. Therefore, how to achieve efficient development of offline development environment deployment in an intranet environment has become a problem that needs to be solved urgently.

[0036] The offline development environment deployment method provided by this application realizes automated deployment by displaying the workflow of the environment to be deployed on the local main interface and determining the target configuration information in combination with user operations. Thus, the development environment can be quickly configured by using local resources through preset configuration steps and target deployment addresses, solving the problem of cloud service unavailability, ensuring efficient and reliable offline development environment deployment in the intranet environment, and improving development efficiency and consistency.

[0037] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0038] Figure 2 Schematic diagram of the offline development environment deployment method provided for this application Figure 1 ,like Figure 2 As shown, the method includes:

[0039] S201. In response to a received first operation, display a workflow corresponding to the environment to be deployed on a main interface.

[0040] The workflow includes configuration steps of the development environment and offline dependency files corresponding to the configuration steps. The configuration steps are used to set configuration parameters corresponding to the current development environment or install offline dependency files required for the development environment.

[0041] Specifically, this embodiment is used to illustrate the basic process of the offline development environment deployment method.

[0042] In the embodiment of the present disclosure, the execution subject is a program in a server or processor that needs to perform offline development environment deployment and program development. The program is used to achieve rapid deployment of the development environment and is collectively referred to as a program for ease of description.

[0043] The first operation is to start the program so as to perform an operation of the offline development environment deployment process. The first operation may be an operation of clicking a program icon or an operation of starting the program through a command line.

[0044] When the program is started through the first operation, the program displays a main interface on the display so that the user (such as a developer) can view the workflow for completing the development environment deployment.

[0045] This workflow not only shows the configuration steps of the development environment, but also includes the offline dependency files corresponding to the configuration steps. These configuration steps are used to set the configuration parameters of the current development environment or install the required offline dependency files to ensure smooth deployment in the intranet environment.

[0046] If the user does not modify the configuration steps, the workflow will display the pre-defined configuration steps for common development environments (such as the configuration steps for common IDE environments, which will be saved in the program in the form of pre-stored work packages), and provide the required offline dependency files or dependency file packages in the corresponding configuration steps so that users can install them without an Internet connection.

[0047] After receiving the user's first operation, the program will read the locally stored work package, extract the corresponding configuration steps and offline dependency files from it, and display them to the user in a graphical manner on the interface.

[0048] Users can click each configuration step to view detailed information for each step, including required resources, configuration parameters, dependent file paths, and expected results.

[0049] In some embodiments, to achieve this, the system may need to use a front-end framework (such as React or Vue.js) to build a dynamic interface and combine it with a back-end service to manage and update configuration data.

[0050] In some embodiments, the workflow can be displayed in multiple view modes, such as a flowchart view, a list view, or a step-by-step guidance view, to accommodate different user preferences.

[0051] In addition, the program can allow users to customize the workflow, adding or removing configuration steps and dependency files to meet specific development needs.

[0052] S202: In response to the received second operation, determine target configuration information of the environment to be deployed.

[0053] The target configuration information includes the target deployment address.

[0054] Specifically, the target configuration information includes the specific parameters and settings that need to be used during the deployment process, such as the target deployment address, resource configuration, and environment variables. This information is the key to successfully deploying the development environment and ensuring that the system can run in the correct environment.

[0055] The program provides a corresponding interface for users to enter target configuration information. This interface is the target configuration interface. Users enter or select target configuration information in this interface, and the system will generate a complete configuration file based on these inputs. This configuration file may include detailed information such as the IP address, port number, operating system version, and dependent library version of the target server.

[0056] In some embodiments, the program may provide preset configuration templates, and users may modify the templates based on the templates, thereby reducing the complexity of the configuration and quickly generating target configuration information.

[0057] In some embodiments, the program includes a function of communicating with an external service, and can automatically obtain and update target configuration information based on user updates to the system where the program is located, such as obtaining the latest target configuration information template from an intranet server.

[0058] S203: Complete offline deployment of the environment to be deployed based on the target configuration information and configuration steps.

[0059] Specifically, in the case of offline deployment, the system or device that needs to complete the offline deployment of the development environment is not connected to the external Internet. The program needs to use localized configuration steps and offline dependency files to complete the environment construction.

[0060] In the specific implementation, the program will call the corresponding built-in scripts or tools to perform deployment operations according to the target configuration information and configuration steps, such as installing necessary dependent software packages, configuring network settings, starting services, and so on.

[0061] In some embodiments, to ensure the success of the deployment, the program will verify after each step to check whether there are any errors or exceptions. If a problem occurs, the system should be able to automatically troubleshoot or prompt the user to intervene manually. After the deployment is completed, a detailed report is generated to record the execution and results of each step for the user to review and confirm.

[0062] In some embodiments, the program can also be applied to a networked environment. In this case, the program can also support multiple deployment modes, such as real-time downloading and updating of offline dependency files, updating preset workflows and target configuration information templates, etc., thereby improving deployment efficiency and quality.

[0063] The offline development environment deployment method provided by the embodiment of the present application displays the corresponding workflow of the environment to be deployed on the main interface in response to the first operation received, then determines the target configuration information of the environment to be deployed in response to the second operation received, and then completes the offline deployment of the environment to be deployed based on the target configuration information and configuration steps. Thus, by displaying the workflow of the environment to be deployed on the main interface and combining the target configuration information, the deployment process of the development environment is simplified, and the rapid deployment of the development environment is achieved. By responding to the user's operation, the solution can automatically determine the configuration steps, the corresponding offline dependency files, and the target configuration information, thereby achieving fast and flexible environment configuration and deployment. This automated and visual deployment method reduces the cost of use and maintenance, overcomes the limitations and network dependence of traditional solutions, and improves deployment efficiency and user experience.

[0064] Figure 3a Schematic diagram of the offline development environment deployment process provided for this application Figure 2 ,like Figure 3a As shown, in this embodiment Figure 2 Based on the embodiment, the specific process in the offline development environment deployment method is described in detail, and the method includes:

[0065] S301. In response to a received first operation, display a workflow corresponding to the environment to be deployed on a main interface.

[0066] The workflow includes configuration steps of the development environment and offline dependency files corresponding to the configuration steps. The configuration steps are used to set configuration parameters corresponding to the current development environment or install offline dependency files required for the development environment.

[0067] Specifically, this embodiment is used to explain in detail the actual steps of deploying an offline development environment.

[0068] In this embodiment, the workflow is displayed in the form of a flowchart.

[0069] In some embodiments, the workflow includes: elements and one-way lines, the elements include a starting point, an end point, and a configuration step; the starting point and the configuration step, two adjacent configuration steps, and the configuration step and the end point are respectively connected by one-way lines; an add control is set on the starting point, and the add control on the starting point is used to add a new configuration step between the starting point and the configuration step; an add control is also set on the configuration step, and the add control on the configuration step is used to add a new configuration step after the configuration step.

[0070] Specifically, the combination of elements and one-way lines (and lines containing arrows) provides a clear process view for the deployment of the offline development environment.

[0071] Users can dynamically add new configuration steps through the add controls on the starting point and configuration steps, and the program will automatically update the connection relationship of the workflow. It also allows users to customize the workflow, add or delete configuration steps and dependent files to meet specific development needs.

[0072] like Figure 3b As shown, it is a schematic diagram of the main interface containing the workflow. The main interface supports the import and export of workflows and the one-click deployment of the development environment (i.e., by triggering Figure 3b ), you can also edit the workflow (the content contained in the upper dotted box in the figure is the workflow) and enter the target configuration information (the content contained in the lower dotted box in the figure is the target configuration information).

[0073] In some embodiments, the main interface is obtained based on a server lightweight web framework written in Python.

[0074] Specifically, the system may need to use a lightweight web framework (such as Python-based Flask or Django) to build the interface, and combine it with a JavaScript library (such as D3.js) to implement dynamic workflow display and interaction.

[0075] S302: In response to a triggering operation on adding a control, the added configuration steps to be filled in are displayed in the main interface.

[0076] Specifically, the main interface allows the user to insert a new configuration step into the workflow to meet specific development requirements or adjust the existing process. Steps S302 to S305 are used to illustrate the implementation process of adding a new configuration step.

[0077] The implementation method is that after the user triggers the addition of controls, a new configuration step to be filled is inserted into the workflow, and the controls of this step are displayed on the interface (such as Figure 3b Add a new configuration step).

[0078] Programs can use JavaScript libraries such as React or Vue.js to manage dynamic updates of the interface and combine them with backend services to maintain the state of the workflow.

[0079] In some embodiments, the program may also provide different types of configuration steps for the user to choose from, such as installing dependent files, setting environment variables, or executing scripts.

[0080] Alternatively, the program may provide an interface and a selection bar for the user to select the desired step type, and the program may automatically generate corresponding placeholders based on the selection.

[0081] In some embodiments, in order to enhance the user experience, the program may also provide a real-time preview function when adding steps, to help users intuitively understand the position and function of the new step in the workflow.

[0082] S303: Generate a configuration interface for configuration steps to be filled.

[0083] The configuration interface is used to display the corresponding names of the configuration steps and execute actions.

[0084] Specifically, the configuration interface helps the user to define the specific operation of each step in detail by displaying the name and execution action corresponding to the configuration step.

[0085] The program generates an interactive configuration interface for each configuration step to be filled in. The user can enter or select the name of the configuration step and the execution action in the configuration interface, and this information will be used in the subsequent deployment process.

[0086] Similarly, the program can use a front-end framework (such as Bootstrap or Material-UI) to design the layout of the configuration interface, and combine it with a JavaScript library (such as jQuery) to implement interactive functions.

[0087] In the configuration interface, the program can provide a variety of input controls, such as text boxes, drop-down menus, check boxes, etc., to accommodate different types of configuration parameters. Users can enter or select the required information through these controls, and the program will update the status of the configuration step in real time.

[0088] In some embodiments, the program may provide configuration templates or preset options to help users quickly fill in commonly used configuration steps, or integrate real-time help or prompt functions to guide users to complete configuration operations.

[0089] like Figure 3cAs shown in the figure, it is a schematic diagram of the structure of the configuration interface. The configuration interface provides editing and modification of the corresponding parameters of the configuration steps (such as step name, action type) and dependent files (such as dependent file addresses), so that users can quickly customize each configuration step. At the same time, it can also provide options such as rollback to the previous version and undo editing to facilitate users to modify the configuration steps. The configuration step information editing can be confirmed by clicking the OK button.

[0090] S304: In response to the input operation in the configuration interface, determine the corresponding name and execution action of the configuration step to be filled.

[0091] Specifically, the user can enter various information (i.e., input operations) corresponding to the configuration steps to be filled in the configuration interface, such as the name and execution action corresponding to the configuration steps to be filled. The program can parse the user's input in the configuration interface and convert it into specific attributes of the configuration step. After the user enters or selects the name and executes the action, the program will immediately update the status of the configuration step and save this information in the background.

[0092] In some embodiments, if the configuration step to be filled includes an action of installing dependent files, when adding a new configuration step, it also includes obtaining the dependent files corresponding to the configuration step to be filled in response to an upload operation on the configuration interface.

[0093] Specifically, if the configuration step involves installing dependent files, the program will provide a file upload function, and the user can upload the required offline dependent files through the interface. The program needs to ensure the security and integrity of the uploaded files and store the files locally or in a specified storage location.

[0094] To achieve this, the system can use a front-end framework (such as Dropzone.js) to implement the file upload function, and combine it with a back-end service to handle file storage and management.

[0095] In some embodiments, the program can support multiple file upload methods, such as drag-and-drop upload, file selection upload, etc., to improve the user's operational convenience. The user can also upload multiple dependent files or dependent file packages, at which point the program will automatically associate these files with the corresponding configuration steps.

[0096] In some embodiments, the program may provide a file management function so that the user can view, delete or replace the uploaded files corresponding to the configuration steps.

[0097] S305: In response to the confirmation operation on the configuration interface, generate configuration steps based on the name and the execution action.

[0098] Specifically, after the user confirms the operation, the program will package the name, execution action and other information into a configuration step and insert it into the workflow. The program needs to ensure the integrity and correctness of the configuration steps and save the updated workflow status in the background.

[0099] In some embodiments, if the configuration step includes the action of installing dependent files, it is necessary to generate the configuration step based on the dependent files, names and execution actions in response to the confirmation operation on the configuration interface.

[0100] Specifically, if a configuration step contains dependent files, the name, execution action, dependent files and other information need to be packaged together into one configuration step.

[0101] In some embodiments, the program may use a backend service to handle the generation and storage of configuration steps and combine with a database or file system to manage the persistence of the workflow.

[0102] In some embodiments, the program may support version control of configuration steps, and users may view and roll back historical versions of configuration steps to quickly recover when errors occur.

[0103] In some embodiments, the program may also provide feedback information after confirming the operation, such as prompts indicating success or failure of the configuration step, to help the user understand the operation results.

[0104] S306: In response to the first type of triggering operation on the configuration step, display a configuration interface of the configuration step.

[0105] Specifically, the program also supports the modification of existing configuration steps. Steps S306 to S309 are used to explain in detail the modification process of existing configuration steps.

[0106] For existing configuration steps, users can trigger their controls to display the corresponding configuration interface.

[0107] The program can support a variety of different types of first-class trigger operation methods, such as single click, double click or right-click menu, etc., to adapt to the operating habits of different users.

[0108] S307: In response to the input operation in the configuration interface, update the corresponding name and execution action of the configuration step.

[0109] Specifically, similar to step S304, the user can modify the existing information in the configuration interface.

[0110] In some embodiments, the program may provide a real-time verification function. When a user enters or modifies data, the program will immediately check its validity and provide corresponding error prompts.

[0111] In some embodiments, the program may also support batch updating of configuration steps, and the user may modify the properties of multiple steps at one time to improve operational efficiency.

[0112] S308: If the configuration step includes an action of installing a file, in response to an upload operation on the configuration interface, update the dependent files corresponding to the configuration step.

[0113] Specifically, similar to the action in adding a configuration step, when modifying a configuration step, the user can also update the dependent files therein.

[0114] S309: In response to the confirmation operation on the configuration interface, the configuration steps are updated based on the updated name, execution action and dependent files.

[0115] Specifically, similar to the action in adding a configuration step, after the user performs the confirmation operation, the program will update the corresponding configuration step based on the updated configuration step related information, close the configuration interface, and then update the display content in the interface where the workflow is located.

[0116] Steps S306 to S309 are optional steps parallel to steps S302 to S305 , and those skilled in the art may select corresponding steps to perform as needed.

[0117] S310: In response to the second type of triggering operation on the configuration step, delete the configuration step.

[0118] Specifically, in addition to adding and modifying configuration steps, the user can also conveniently delete configuration steps. Steps S310 to S311 are used to explain in detail the process of deleting configuration steps.

[0119] This step is used to facilitate users to remove unnecessary configuration steps to simplify workflow or correct errors.

[0120] After the user takes the second type of trigger action, the program will delete the relevant data of the configuration steps from the background and update the connection relationship of the workflow.

[0121] In some embodiments, to ensure the security and correctness of the deletion operation and prevent accidental deletion or data loss, the program can use the backend service to handle the deletion of configuration steps and data management, and combine with the frontend framework to update the interface display.

[0122] In some embodiments, the program may support multiple triggering operation modes, such as clicking, right-click menu or shortcut keys, etc., to adapt to the operating habits of different users.

[0123] In some embodiments, the program may allow the user to confirm before deleting the data to prevent accidental deletion.

[0124] S311. Connect the elements before the configuration step and the elements after the configuration step through a one-way line, and update the workflow of the main interface.

[0125] Specifically, after the user deletes a configuration step, the system will automatically adjust the connection relationship of the remaining elements in the workflow, connecting the elements before the deleted step with the elements after the deleted step through a one-way line. By updating the workflow on the main interface, the consistency and integrity of the workflow is ensured.

[0126] In some embodiments, the program may support an undo operation so that the user can quickly recover after accidentally deleting a configuration step.

[0127] In some embodiments, after the operations in the above steps are completed, a corresponding packaging file can be generated in response to a received third operation based on the workflow and the offline dependency files corresponding to all configuration steps, and the packaging file is used for offline development environment deployment.

[0128] Specifically, after completing the workflow construction through the aforementioned steps, the user can save and export the workflow, export the files required for development environment deployment as a workflow file in json format, or package and export them together with related program dependencies (hereinafter referred to as "all-in-one workflow") as a work package file.

[0129] The file can be shared with others. The user who receives the exported file can import the file in the program, then start the one-click deployment program and restore the workflow. If the exported file is a work package, there is no need to initiate a request to the file server and re-download dependent files when executing the deployment. The project deployment and installation can be performed offline.

[0130] S312: In response to the received second operation, determine target configuration information of the environment to be deployed.

[0131] The target configuration information includes the target deployment address.

[0132] S313: Based on the target configuration information and configuration steps, complete the offline deployment of the environment to be deployed.

[0133] Specifically, steps S312 to S313 are Figure 2 The corresponding steps in the illustrated embodiment are the same in content and will not be described again here.

[0134] The offline development environment deployment method provided by the disclosed embodiment allows users to intuitively view and adjust configuration steps through dynamic display and management of workflows, ensuring the transparency and controllability of the deployment process. Secondly, the program supports the management and upload of offline dependent files, which solves the problem of being unable to connect to the Internet in the intranet environment and ensures the integrity of the development environment. Through a flexible configuration interface, users can quickly define and modify configuration steps, improving the accuracy and efficiency of operations, making the construction of the development environment more efficient and stable, thereby improving the work efficiency and deployment quality of the development and operation and maintenance teams in the intranet environment.

[0135] Figure 4 A schematic diagram of the structure of the offline development environment deployment device provided for this application, such as Figure 4 As shown, the offline development environment deployment device 400 provided in this embodiment includes:

[0136] The editing module 410 is used to display the workflow corresponding to the to-be-deployed environment on the main interface in response to the received first operation, where the workflow includes configuration steps of the development environment and offline dependent files corresponding to the configuration steps, where the configuration steps are used to set configuration parameters corresponding to the current development environment or install offline dependent files required for the development environment;

[0137] The instruction module 420 is used to determine target configuration information of the to-be-deployed environment in response to the received second operation, where the target configuration information includes a target deployment address;

[0138] The processing module 430 is used to complete the offline deployment of the to-be-deployed environment based on the target configuration information and the configuration steps.

[0139] In a possible implementation, the editing module 410 specifically includes: the workflow includes: elements and one-way lines, the elements include a starting point, an end point, and a configuration step; the starting point and the configuration step, two adjacent configuration steps, and the configuration step and the end point are respectively connected by one-way lines; an add control is set on the starting point, and the add control on the starting point is used to add a new configuration step between the starting point and the configuration step; an add control is also set on the configuration step, and the add control on the configuration step is used to add a new configuration step after the configuration step.

[0140] In one possible implementation, the editing module 410 is also used to, in response to a received first operation, after displaying the workflow corresponding to the to-be-deployed environment on the main interface, and then, in response to a trigger operation on an added control, display the added configuration steps to be filled in on the main interface; generate a configuration interface for the configuration steps to be filled in, the configuration interface being used to display the corresponding names and execution actions of the configuration steps; in response to an entry operation in the configuration interface, determine the corresponding names and execution actions of the configuration steps to be filled in; and in response to a confirmation operation on the configuration interface, generate configuration steps based on the names and execution actions.

[0141] In one possible implementation, the editing module 410 is also used for, if the configuration interface is also used to display dependent files to be installed, in response to an input operation in the configuration interface, after determining the corresponding name and execution action of the configuration operation to be filled in, if the configuration step to be filled includes the action of installing the dependent file, in response to an upload operation in the configuration interface, obtaining the corresponding dependent file of the configuration step to be filled; in response to a confirmation operation in the configuration interface, generating a configuration step based on the name and the execution action; in response to a confirmation operation in the configuration interface, generating a configuration step based on the dependent file, the name and the execution action.

[0142] In one possible implementation, the editing module 410 is also used to, in response to a received first operation, after displaying the workflow corresponding to the environment to be deployed on the main interface, display the configuration interface of the configuration step in response to a first type of trigger operation on the configuration step; in response to an input operation in the configuration interface, update the corresponding name and execution action of the configuration step; if the configuration step includes an action to install a file, in response to an upload operation on the configuration interface, update the corresponding dependent file of the configuration step; in response to a confirmation operation on the configuration interface, update the configuration step based on the updated name, execution action and dependent file.

[0143] In one possible implementation, the editing module 410 is also used to, in response to the first operation received, after the workflow corresponding to the environment to be deployed is displayed on the main interface, delete the configuration step in response to the second type of trigger operation on the configuration step; connect the elements before the configuration step with the elements after the configuration step through a one-way line, and update the workflow of the main interface.

[0144] In one possible implementation, the editing module 410 is also used to, in response to a received first operation, display on the main interface a workflow corresponding to the environment to be deployed, after the workflow includes configuration steps for the development environment, and then, in response to a received third operation, generate a corresponding package file based on the offline dependency files corresponding to the workflow and all configuration steps, and the package file is used for offline development environment deployment.

[0145] In a possible implementation, the editing module 410 specifically includes a main interface obtained based on a server lightweight web framework written in Python.

[0146] The offline development environment deployment device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be described in detail here.

[0147] Figure 5 This is a schematic diagram of the structure of the electronic device provided in this application. Figure 5As shown, the electronic device 50 provided in this embodiment includes: at least one processor 501 and a memory 502. Optionally, the device 50 also includes a communication component 503. The processor 501, the memory 502 and the communication component 503 are connected via a bus 504.

[0148] In a specific implementation process, at least one processor 501 executes the computer-executable instructions stored in the memory 502, so that at least one processor 501 executes the above method.

[0149] The specific implementation process of the processor 501 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

[0150] In the above embodiments, it should be understood that the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the invention can be directly implemented as a hardware processor, or can be implemented by a combination of hardware and software modules in the processor.

[0151] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (NVM), such as at least one disk storage.

[0152] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of this application is not limited to only one bus or one type of bus.

[0153] The present application also provides a computer program product, including a computer program, which implements the method in any of the above embodiments when executed by a processor.

[0154] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the method in any of the above embodiments is implemented.

[0155] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0156] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0157] The division of units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0158] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0159] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0160] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0161] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present application.

[0162] It should be further noted that, although the various steps in the flowchart are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowchart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0163] It should be understood that the above-mentioned device embodiments are only illustrative, and the device of the present application can also be implemented in other ways. For example, the division of units / modules in the above-mentioned embodiments is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0164] In addition, unless otherwise specified, each functional unit / module in each embodiment of the present application may be integrated into one unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The above-mentioned integrated unit / module may be implemented in the form of hardware or in the form of a software program module.

[0165] If the integrated unit / module is implemented in the form of hardware, the hardware may be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes but is not limited to transistors, memristors, etc. Unless otherwise specified, the processor may be any appropriate hardware processor, such as a CPU, a GPU, an FPGA, a DSP, an ASIC, etc. Unless otherwise specified, the storage unit may be any appropriate magnetic storage medium or magneto-optical storage medium, such as a resistive random access memory (RRAM), a dynamic random access memory (DRAM), a static random access memory (SRAM), an enhanced dynamic random access memory (EDRAM), a high-bandwidth memory (HBM), a hybrid memory cube (HMC), etc.

[0166] If the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a memory, including a number of instructions to enable a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0167] In the above embodiments, the description of each embodiment has its own emphasis. For the part not described in detail in a certain embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0168] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

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

Claims

1. A method for deploying an offline development environment, characterized in that: The steps include: In response to the received first operation, displaying a workflow corresponding to the environment to be deployed on the main interface, the workflow including configuration steps of the development environment and offline dependency files corresponding to the configuration steps, the configuration steps being used to set configuration parameters corresponding to the current development environment or to install offline dependency files required for the development environment; In response to the received second operation, determining target configuration information of the to-be-deployed environment, the target configuration information including a target deployment address; Based on the target configuration information and the configuration steps, the offline deployment of the environment to be deployed is completed.

2. The method according to claim 1, characterized in that The workflow includes: Elements and one-way lines, the elements including a starting point, an end point, and a configuration step; The starting point and the configuration step, two adjacent configuration steps, and the configuration step and the end point are connected by one-way lines respectively; An adding control is provided at the starting point, and the adding control at the starting point is used to add a new configuration step between the starting point and the configuration step; The configuration step is also provided with an adding control, and the adding control on the configuration step is used to add a new configuration step after the configuration step.

3. The method according to claim 2, characterized in that In response to the received first operation, after the workflow corresponding to the to-be-deployed environment is displayed on the main interface, the method further includes: In response to the triggering operation of the adding control, the added configuration steps to be filled are displayed in the main interface; Generate a configuration interface for the configuration step to be filled, wherein the configuration interface is used to display the corresponding name of the configuration step and the execution action; In response to an input operation in the configuration interface, determining a name corresponding to the configuration step to be filled and an execution action; In response to a confirmation operation on the configuration interface, the configuration step is generated based on the name and the execution action.

4. The method according to claim 3, characterized in that The configuration interface is also used to display the dependent files to be installed. After the step of responding to the input operation in the configuration interface and determining the name corresponding to the configuration operation to be filled in and the execution action, the step further includes: If the configuration step to be filled includes an action of installing a dependent file, in response to an upload operation on the configuration interface, obtaining the dependent file corresponding to the configuration step to be filled; The step of generating the configuration step based on the name and the execution action in response to the confirmation operation on the configuration interface includes: In response to a confirmation operation on the configuration interface, the configuration steps are generated based on the dependent files, the names and the execution actions.

5. The method according to claim 3, characterized in that: In response to the received first operation, after the workflow corresponding to the to-be-deployed environment is displayed on the main interface, the method further includes: In response to a first type of triggering operation on the configuration step, displaying a configuration interface of the configuration step; In response to an input operation in the configuration interface, updating the corresponding name and execution action of the configuration step; If the configuration step includes an action of installing a file, in response to an upload operation on the configuration interface, updating a dependent file corresponding to the configuration step; In response to a confirmation operation on the configuration interface, the configuration steps are updated based on the updated name, execution action and dependent files.

6. The method according to claim 2, characterized in that In response to the received first operation, after the workflow corresponding to the to-be-deployed environment is displayed on the main interface, the method further includes: In response to a second type of triggering operation on the configuration step, deleting the configuration step; The elements before the configuration step are connected with the elements after the configuration step through a one-way line, and the workflow of the main interface is updated.

7. The method according to claim 2, characterized in that In response to the received first operation, a workflow corresponding to the to-be-deployed environment is displayed on the main interface, wherein the workflow includes, after the configuration step of the development environment, the following steps are further included: In response to the received third operation, a corresponding packaging file is generated based on the workflow and offline dependency files corresponding to all configuration steps, and the packaging file is used for offline development environment deployment.

8. The method according to any one of claims 1 to 7, characterized in that The main interface is obtained based on a server lightweight web framework written in Python.

9. An offline development environment deployment device, characterized in that: include: An editing module, configured to display, in response to the received first operation, a workflow corresponding to the environment to be deployed on a main interface, wherein the workflow includes configuration steps of the development environment and offline dependency files corresponding to the configuration steps, wherein the configuration steps are used to set configuration parameters corresponding to the current development environment or to install offline dependency files required for the development environment; an indication module, configured to determine target configuration information of the to-be-deployed environment in response to the received second operation, wherein the target configuration information includes a target deployment address; A processing module is used to complete the offline deployment of the to-be-deployed environment based on the target configuration information and the configuration steps.

10. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 8 when executed by a processor.

12. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 8 when being executed by a processor.

Images