Axure application zero code cloud deployment method, system, equipment and medium

Abstract

The invention provides an Axure application zero-code cloud deployment method, system and device and a medium, and belongs to the technical field of software development. The method comprises the steps that Axure software of the latest version is installed, a cloud server is configured, and a cloud server instance is created; generating an HTML (Hypertext Markup Language) folder containing all pages and interactions according to the to-be-uploaded presentation through Axure software; configuring a standardized directory structure, and importing the HTML folder into the standardized directory structure for classified storage; the HTML folder is uploaded to a cloud server; installing and configuring a Web server in the cloud server, editing and configuring a storage path and an access permission of an application corresponding to the HTML folder, and restarting the cloud server to enable the configuration to take effect; and testing the interaction function of the application through the IP and the access path. According to the method, code-free cloud deployment of the Axure application is realized, the release process of prototype design is simplified, and the accessibility and the interaction test efficiency are improved.

Description

Technical Field

[0001] The present invention belongs to the field of software development technology, and more specifically relates to a zero-code cloud deployment method, system, device, and medium for Axure applications. Background Art

[0002] In current software development practices, even for small, demonstration applications with relatively simple functions, such as product demos or presentation prototypes, the traditional application development process still involves multiple, cumbersome steps. These steps typically include prototyping, front-end development, back-end coding, testing and debugging, and server deployment. This process not only leads to low development efficiency, extended development cycles, and increased labor costs, but also presents a high technical barrier to entry for non-professionals, making operations complex and error-prone. In particular, there is a significant gap between prototyping and actual development. HTML prototypes generated by tools like Axure are often used only as a development reference, requiring developers to recode to implement interactive logic and interfaces, further exacerbating development cycle and cost issues.

[0003] As a prototyping tool, Axure RP is widely used in the field of software development. It supports the generation of high-fidelity interactive prototypes through functions such as dynamic panels, masters, variables, and conditional logic. These prototypes can be exported as static applications containing HTML, CSS, JavaScript, and resource files. Axure's responsive design technology enables it to adapt to a variety of terminal devices and achieve complex interactive effects through state management. However, although the static files generated by Axure contain complete interactive logic and page resources, in existing technologies, these files are usually only used for development reference or local demonstration, and are not effectively combined with cloud server technology, and cannot be directly converted into applications that can be accessed online. This leads to a waste of resources and increases the complexity of development and deployment.

[0004] With the continuous development of cloud computing technology, cloud server deployment has become a key trend in software development and deployment. Mainstream cloud service providers offer sophisticated solutions for server instance creation, network configuration, and web server deployment, making the development and deployment process more flexible and efficient. However, traditional cloud server deployment methods still require developers to manually upload code, configure the environment, and rely on front-end and back-end programming to implement functionality. For non-professionals, this process still has a certain technical threshold. More importantly, existing cloud server deployment technologies cannot directly reuse static files generated by Axure, which limits the application of Axure prototypes in cloud deployment. Therefore, how to combine Axure prototyping technology with cloud server deployment technology to achieve fast, zero-code, and efficient cloud deployment of small demonstration applications has become a pressing issue in the current software development field. Summary of the Invention

[0005] In response to the above problems, the purpose of the present invention is to provide a zero-code cloud deployment method, system, device and medium for Axure applications. Through technologies such as automatic HTML generation, cloud server configuration and Web service deployment, the code-free cloud deployment of Axure applications is realized, thereby simplifying the prototype design release process and improving accessibility and interactive testing efficiency.

[0006] To achieve the above-mentioned purpose, the present invention is implemented through the following technical solutions: In a first aspect, an embodiment of the present application provides a zero-code cloud deployment method for an Axure application, including: Install the latest version of Axure software, configure the cloud server and create a cloud server instance; Generate an HTML folder containing all pages and interactions based on the presentation to be uploaded using Axure software; Configuring a standardized directory structure, and importing the HTML folder into the standardized directory structure for classified storage; Upload the HTML folder to the cloud server; Install and configure the web server in the cloud server and edit the storage path and access permissions of the Axure application corresponding to the HTML folder. Restart the cloud server for the configuration to take effect. Test the interactive functions of the Axure application through the public IP and access path.

[0007] In an optional embodiment, installing the latest version of Axure software, configuring a cloud server, and creating a cloud server instance includes: Install Axure software and update to the latest version; Select an appropriate cloud server according to your needs, create a cloud server instance, enable object storage services, configure the data storage directory, and set security group rules.

[0008] In an optional embodiment, the step of generating an HTML folder containing all pages and interactions based on the presentation to be uploaded using Axure software includes: Open the presentation to be uploaded in Axure software; Use Axure software for page layout and interactive logic design; Use the Publish to HTML function of Axure software to generate an HTML folder containing the interactive logic, and set the page title, page size and storage path when exporting.

[0009] In an optional embodiment, the standardized directory structure includes: a data folder, a files folder, a plugins folder, and a resources folder; The data folder is used to store prototype metadata in the project; The files folder is used to store HTML files and related resources, including but not limited to images, CSS files, and JavaScript files; plugins folder, used to store, manage and use plugins; The resources folder is used to store non-code resources required by the project, including but not limited to images, fonts, style sheets, JavaScript files, and configuration files.

[0010] In an optional embodiment, uploading the HTML folder to the cloud server includes: Connect to the cloud server instance using an SSH client or web console; Create a new folder on the cloud server to store the application's HTML folder and related resources.

[0011] Use the file transfer protocol to upload the HTML folder and related resources generated by Axure to the designated folder on the cloud server, and ensure the integrity of the upload.

[0012] In an optional embodiment, the steps of installing and configuring a web server in a cloud server, editing and configuring the storage path and access permissions of the Axure application corresponding to the HTML folder, and restarting the cloud server to make the configuration effective include: Determine whether a web server has been installed on the cloud server; If not, install the web server through the cloud server's package manager and edit the configuration file to specify the application directory and access permissions to complete service initialization; Save the configuration file and restart the Web server for the configuration to take effect.

[0013] In an optional embodiment, testing the interactive function of the Axure application through the public network IP and access path includes: Enter the public IP address of the cloud server and the application access path in the browser to check whether the corresponding presentation can be accessed and interacted with normally; If you can access and interact normally, share the corresponding access link.

[0014] In a second aspect, the embodiments of the present application further provide an Axure application zero-code cloud deployment system, including: The environment configuration module is used to install the latest version of Axure software, configure the cloud server, and create a cloud server instance; Export application module, used to generate an HTML folder containing all pages and interactions based on the presentation to be uploaded using Axure software; A configuration storage module is used to configure a standardized directory structure and import the HTML folder into the standardized directory structure for classified storage; Upload module, used to upload HTML folders to the cloud server; The server configuration module is used to install and configure the web server in the cloud server and edit the storage path and access permissions of the Axure application corresponding to the HTML folder. Restart the cloud server for the configuration to take effect. The access test module is used to test the interactive functions of Axure applications through public IP addresses and access paths.

[0015] In a third aspect, an embodiment of the present application further provides an electronic device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the steps of the zero-code cloud deployment method for Axure applications as described in any one of the above items are implemented.

[0016] In a fourth aspect, an embodiment of the present application further provides a storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the zero-code cloud deployment method of Axure application as described in any of the above items are implemented.

[0017] It can be seen from the above technical solutions that the present invention has the following advantages: In the zero-code cloud deployment method for Axure applications provided in this application, code-free cloud deployment of Axure applications is achieved by automatically generating an HTML folder containing all pages and interactive logic, configuring a standardized directory structure on a cloud server for classified storage, and installing and configuring a web server to deploy the Axure application. The entire process simplifies the release process of prototype design, avoids tedious manual coding and configuration work, and significantly improves work efficiency. At the same time, the method also focuses on the data processing process. Through a carefully designed standardized directory structure, HTML folders and their related resources are stored and managed in an orderly manner, thereby ensuring the consistency and integrity of the data. In addition, cloud deployment also enables Axure applications to easily achieve cross-platform access and interactive testing, further improving the usability and testing efficiency of prototype design.

[0018] This application eliminates traditional manual coding and configuration steps by automatically generating HTML folders and deploying them in the cloud, significantly simplifying the Axure application publishing process and lowering the technical threshold, making it easy for non-technical personnel to complete application deployment.

[0019] This application classifies and stores HTML folders and related resources through a standardized directory structure, ensuring data consistency and integrity, improving data processing efficiency, and avoiding errors and delays caused by data confusion.

[0020] This application uses cloud deployment to enable easy cross-platform access to Axure applications. Users can view and interact with prototype designs anytime and anywhere simply through a browser, greatly enhancing the accessibility and interactivity of the application.

[0021] This application supports online interactive testing. Testers can directly test the interactive functions of the Axure application through the public network IP and access path without downloading and installing additional software, thereby improving testing efficiency and shortening the product iteration cycle.

[0022] In this application, cloud deployment leverages the elastic scaling capabilities of cloud servers, allowing for dynamic resource allocation based on actual demand. This avoids the waste and idleness of traditional server resources, reducing costs and resource consumption. Furthermore, the high availability and disaster recovery capabilities of cloud servers ensure application stability and security. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0024] Figure 1 This is a flowchart of the zero-code cloud deployment method for Axure applications provided in this application.

[0025] Figure 2 This is a schematic diagram of the structure of the zero-code cloud deployment system for Axure applications provided for this application.

[0026] Figure 3 This is a schematic diagram of the structure of the electronic device provided in this application. DETAILED DESCRIPTION

[0027] The following detailed description of the specific steps of the zero-code cloud deployment method for Axure applications will further fully describe various embodiments of the present disclosure. The present disclosure can have various embodiments, and adjustments and changes can be made therein. However, it should be understood that there is no intention to limit the various embodiments of the present disclosure to the specific embodiments disclosed herein, and that the present disclosure should be construed to encompass all adjustments, equivalents, and / or alternatives falling within the spirit and scope of the various embodiments of the present disclosure.

[0028] Hereinafter, the terms "include" or "may include" as used in various embodiments of the present disclosure indicate the presence of disclosed functions, operations, or elements, and do not limit the addition of one or more functions, operations, or elements. In addition, as used in various embodiments of the present disclosure, the terms "include," "have," and their cognates are intended only to indicate specific features, numbers, steps, operations, elements, components, or combinations of the foregoing, and should not be understood as excluding the presence of one or more other features, numbers, steps, operations, elements, components, or combinations of the foregoing, or the possibility of adding one or more features, numbers, steps, operations, elements, components, or combinations of the foregoing.

[0029] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0030] See also Figure 1 The figure shows a method flow chart of a zero-code cloud deployment method for Axure applications in a specific embodiment, the method comprising: S1: Install the latest version of Axure software, configure the cloud server and create a cloud server instance.

[0031] In a specific implementation, the latest version of AxureRP (e.g., 9.0+) is used to build a prototype design environment. A cloud server instance is created through the cloud service provider console (with the public IP and security group rules configured). A cloud storage service that supports static hosting (such as OSS / COS) is selected to complete the construction of the basic network environment.

[0032] For example, first make sure Axure is installed and updated to the latest version: this helps ensure the compatibility of the exported HTML file and the use of the latest features.

[0033] Next, choose a cloud server provider. Choose the right cloud server provider based on your needs, such as Alibaba Cloud, Tencent Cloud, or Amazon AWS. These providers offer a wide range of cloud server options, allowing you to choose the right configuration based on your project needs.

[0034] Finally, create a cloud server instance. On the selected cloud server provider platform, create a cloud server instance as needed and configure the corresponding network environment (such as public network IP, security group rules, etc.).

[0035] S2: Use Axure software to generate an HTML folder containing all pages and interactions based on the presentation to be uploaded.

[0036] In a specific embodiment, the Publish to HTML function of Axure software is used to generate a webpage file containing interactive logic. The page title, size, and storage path are optimized through export settings to ensure that a separate folder contains complete resources and disable the generation of redundant files. Complete resources include HTML files, CSS files, JS files, and image files.

[0037] For example, first, open the presentation you want to upload in Axure. Then, export it as an HTML file. To do this, click "Publish" in the menu bar and select "Publish to HTML" or a similar option. This will generate an HTML folder containing all the pages and interactions. Be sure to set the required options when exporting, such as the folder path, page titles, and page dimensions.

[0038] S3: Configure a standardized directory structure, and import the HTML folder into the standardized directory structure for classified storage.

[0039] In a specific implementation, a standard directory structure is established, including: a data directory to store prototype metadata, a files directory containing web page files, and an images directory to centrally manage image resources. Automatic resource replication and version control are achieved through Axure's built-in mechanism to ensure that the resource reference path is correct.

[0040] For example, the standardized directory structure includes: data folder, files folder, plugins folder and resources folder.

[0041] The data folder is used to store project data, including page content, component settings, user interactions, etc., and is usually stored in the project file itself (such as the .rp file). However, you may also create files or folders in other locations of the project (such as a specific subfolder under the user's documents folder) to store additional project-related data, such as user-defined component libraries, automatic backup files, etc.

[0042] The files folder is used to store HTML output files. When you export a project to HTML, the generated HTML file and its associated resources (such as images, CSS files, JavaScript files, etc.) are usually saved in a folder named files (or a similar name). This folder contains the complete web page representation of the project, allowing users to view and interact with the prototype directly in the browser.

[0043] The files folder is also used to store all images used in the project, including background images, button icons, and page element images. These images are stored in the images folder. These images are an important part of prototype design and are crucial for improving the prototype's visual quality and user experience. When users insert images, the software automatically copies them to the images folder (or designated image storage location) to ensure centralized management and easy access to image resources.

[0044] The plugins folder primarily deals with the management and use of plugins. It's a dedicated directory for storing plugins. These plugins can be developed by third parties and are used to extend the software's functionality, such as adding new tools, improving productivity, and optimizing the user experience. By centrally storing plugins in the plugins folder, users can easily manage and maintain them. Whether installing new plugins or uninstalling unneeded ones, this folder can be used to keep the software clean and efficient.

[0045] The resources folder (or similarly named folder) is typically used to store non-code assets needed for a project, such as images, fonts, style sheets (CSS), JavaScript files, and configuration files. These resources are crucial to the project's integrity and visual presentation. If this concept is applied to a use case, while a folder named "resources" isn't directly generated, it does process and use various resource files to build a prototype. These resource files may be organized and stored in different ways, but they all have in common: they enhance the prototype's visuals and interactivity.

[0046] S4: Upload the HTML folder to the cloud server.

[0047] In a specific implementation, connect to the cloud server via SSH and use an SFTP tool (such as FileZilla) to upload the complete export folder to a web directory (such as / var / www / html / axure) to ensure file integrity verification. The MD5 algorithm can be used for file integrity verification.

[0048] For this example, first connect to your cloud server instance using an SSH client or the cloud server provider's web console. Then, create a new folder on the cloud server (e.g., / var / www / html / axure) to store your application's HTML files and related resources. Finally, use an SFTP client (e.g., FileZilla) or another file transfer protocol to upload the HTML folder generated by Axure and its contents to the designated folder on the cloud server. Ensure that all files (including HTML files, images, CSS, and JavaScript files) are uploaded correctly.

[0049] S5: Install and configure the web server in the cloud server and edit the storage path and access permissions of the Axure application corresponding to the HTML folder. Restart the cloud server for the configuration to take effect.

[0050] In a specific implementation, first determine whether a web server has been installed on the cloud server; if not, install Nginx or Apache web server through the cloud server's package manager, specify the application directory and access permissions by editing the configuration file, enable Gzip compression and configure MIME type support to complete service initialization; finally, save the configuration file and restart the web server to make the configuration take effect.

[0051] For example, if a web server (such as Apache or Nginx) is not installed on the cloud server, you need to install and configure it first. This can usually be done through the cloud server's package manager (such as yum, apt, etc.). At this time, edit the web server's configuration file to ensure that the application's HTML files can be accessed through the web. For the Apache server, you need to edit the configuration file in the / etc / httpd / conf / httpd.conf or / etc / httpd / conf.d / directory and add the corresponding <virtualhost>or <directory>Use the command to specify the storage path and access permissions for the Axure presentation. After saving the configuration file, restart the web server for the configuration to take effect.

[0052] S6: Test the interactive functions of the Axure application through the public IP and access path.

[0053] In this specific implementation, we verify application access through a public IP address and path (e.g., http: / / IP / axure / index.html), test interactive functionality and multi-device compatibility (PC / mobile), and configure HTTP status code monitoring (404 / 500 error handling). During testing, we check whether the presentation is accessible and interactive.

[0054] If everything is working correctly, you can share this access link with your team members or clients, allowing them to access and view the application through a browser.

[0055] In this example, we first used Axure RP to create a prototype design, including page layout and interaction logic. We fully utilized Axure's tools and features, such as dynamic panels, master templates, variables, and conditional logic, to build complex interactive scenarios. We designed the app with responsiveness and accessibility in mind, ensuring it runs well on different devices and browsers. After completing the design in Axure, we exported the prototype as an application file using the "Publish" function. The exported HTML file contains all the prototype's content, styles, and interaction logic, and can be viewed directly in a browser.

[0056] At this point, select a reliable cloud server provider, such as Alibaba Cloud, Tencent Cloud, or Amazon Cloud. Choose the appropriate server configuration based on your application's requirements and budget, including CPU, memory, storage space, and network bandwidth. Then, set up an environment on the cloud server that supports HTML parsing, such as Apache or Nginx. Upload the exported HTML file and related resource files (such as images, CSS, and JavaScript) to a designated directory on the cloud server. Also, configure the server's network settings and security group rules to ensure that the application can be accessed from the internet. Configure the application's access URL and port number on the cloud server.

[0057] Finally, perform comprehensive testing to ensure that the application runs properly on the cloud server without obvious performance issues or errors.

[0058] It can be seen that the zero-code cloud deployment method for Axure applications disclosed in this embodiment significantly simplifies the release process of Axure applications by automatically generating HTML folders, cloud deployment, and adopting a standardized directory structure, lowering the technical threshold and ensuring the consistency and integrity of data during processing and storage. Specifically, it uses technical means to directly convert prototype designs into web applications that can be accessed online, eliminating the need for tedious manual coding and configuration, greatly improving work efficiency. At the same time, this method uses a carefully designed standardized directory structure to classify, store, and manage HTML folders and their related resources in an orderly manner, avoiding data confusion and errors and ensuring the accuracy and efficiency of data processing. In addition, cloud deployment also enables applications to easily achieve cross-platform access and interactive testing, further improving the usability and testing efficiency of prototype design, and providing users with a more convenient and efficient experience. In general, this method has achieved significant beneficial effects in simplifying the release process, improving data processing efficiency, enhancing accessibility and interactivity, improving testing efficiency, and reducing costs and resource consumption.

[0059] In one embodiment of the present invention, a possible embodiment is given below to illustrate its specific implementation scheme in a non-limiting manner.

[0060] The zero-code cloud deployment method for Axure applications disclosed in the present invention also includes: When uploading applications to the cloud server, protect sensitive information and prevent unauthorized access by setting strong passwords, using the HTTPS protocol, and configuring security group rules.

[0061] Regularly back up applications and other important data on cloud servers to prevent data loss or corruption.

[0062] Optimize the performance of cloud servers according to actual needs, such as adjusting resource allocation and optimizing network settings, to improve application access speed and user experience.

[0063] like Figure 2 As shown, the following is an embodiment of the Axure application zero-code cloud deployment system provided by the embodiment of the present disclosure. This system and the Axure application zero-code cloud deployment method of the above embodiments belong to the same inventive concept. For details not fully described in the embodiment of the Axure application zero-code cloud deployment system, please refer to the embodiment of the above-mentioned Axure application zero-code cloud deployment method.

[0064] A zero-code cloud deployment system for Axure applications includes: an environment configuration module, an application export module, a configuration storage module, an upload module, a server configuration module, and an access test module.

[0065] The environment configuration module is used to install the latest version of Axure software, configure the cloud server, and create a cloud server instance.

[0066] The export application module is used to generate an HTML folder containing all pages and interactions based on the presentation to be uploaded using the Axure software.

[0067] The configuration storage module is used to configure a standardized directory structure and import the HTML folder into the standardized directory structure for classified storage.

[0068] Upload module, used to upload HTML folders to the cloud server.

[0069] The server configuration module is used to install and configure the web server in the cloud server and edit the storage path and access permissions of the Axure application corresponding to the HTML folder. Restart the cloud server for the configuration to take effect.

[0070] The access test module is used to test the interactive functions of Axure applications through public IP addresses and access paths.

[0071] The Axure application zero-code cloud deployment system provided in this embodiment is through.

[0072] Figure 3 A schematic diagram of the hardware structure of an electronic device for implementing various embodiments of the present invention.

[0073] The zero-code cloud deployment method for Axure applications provided in the embodiments of the present application can be applied to electronic devices. Those skilled in the art will understand that the electronic device structure involved in the embodiments of the present invention does not constitute a limitation on the electronic device, and the electronic device may include more or fewer components than shown, or combine certain components, or arrange components differently. In an embodiment of the present invention, electronic devices include but are not limited to laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. Electronic devices can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the embodiments of the present application described and / or required herein.

[0074] The electronic device may include a processor, an external memory interface, an internal memory, a universal serial bus (USB) interface, a charging management module, a power management module, a battery, a wireless communication module, an audio module, a speaker, a microphone, a sensor module, a button, a camera, a display, and a SIM card interface, etc.

[0075] A processor may include one or more processing units, such as a central processing unit (CPU), an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors.

[0076] The processor can be the nerve center and command center of the electronic device. The controller can generate operation control signals based on the instruction opcode and timing signal to complete the control of instruction fetching and execution.

[0077] The processor may also include a memory for storing instructions and data. In some embodiments, the memory in the processor is a cache memory. This memory can store instructions or data that the processor has just used or is reusing. If the processor needs to use the instruction or data again, it can directly call it from the memory. This avoids repeated accesses, reduces processor latency, and thus improves system efficiency.

[0078] The external memory interface can be used to connect an external memory card, such as a MicroSD card, to expand the storage capacity of an electronic device. The external memory card communicates with the processor through the external memory interface, enabling data storage. For example, files such as music and videos can be stored on the external memory card.

[0079] Internal memory can be used to store computer-executable program code, which includes instructions. The processor executes the instructions stored in the internal memory to perform various functional applications and data processing of the electronic device. The internal memory can include a program storage area and a data storage area. The internal memory can include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0080] The wireless communication function of an electronic device can be implemented through an antenna, a wireless communication module, a modem processor, and a baseband processor.

[0081] Wireless communication modules can provide wireless communication solutions for electronic devices, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), etc.

[0082] Electronic devices can implement audio functions through audio modules, speakers, receivers, microphones, headphone jacks, and application processors.

[0083] Electronic devices can achieve shooting functions through ISP, camera, video codec, GPU, display and application processor.

[0084] Electronic devices can achieve display functions through GPU, display screen and application processor.

[0085] A GPU is a microprocessor for image processing that connects the display screen to the application processor. It performs mathematical and geometric calculations for graphics rendering. A processor may include one or more GPUs, which execute program instructions to generate or modify display information.

[0086] The display screen is used to display images, videos, etc. The display screen includes a display panel.

[0087] The above-mentioned electronic device implements the zero-code cloud deployment method of Axure applications in this application by automatically generating HTML folders, implementing cloud deployment and adopting a standardized directory structure, thereby significantly simplifying the Axure application release process, lowering technical barriers, ensuring data processing consistency and integrity, improving prototype design work efficiency, enhancing application cross-platform accessibility and convenience of interactive testing, and optimizing user experience and reducing costs.

[0088] The storage medium provided in this application stores a program product that can implement the zero-code cloud deployment method of Axure applications.

[0089] Axure application zero-code cloud deployment methods include: Install the latest version of Axure software, configure the cloud server and create a cloud server instance; Generate an HTML folder containing all pages and interactions based on the presentation to be uploaded using Axure software; Configuring a standardized directory structure, and importing the HTML folder into the standardized directory structure for classified storage; Upload the HTML folder to the cloud server; Install and configure the web server in the cloud server and edit the storage path and access permissions of the Axure application corresponding to the HTML folder. Restart the cloud server for the configuration to take effect. Test the interactive functions of the Axure application through the public IP and access path.

[0090] In some possible implementations, the zero-code cloud deployment method for Axure applications disclosed herein may be implemented in the form of a program product, which includes program code. When the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps described in the "Exemplary Methods" section above of this specification according to various exemplary implementations of the present disclosure.

[0091] The storage medium of the present disclosure can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, a system, device or component of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0092] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention is not limited to the embodiments shown herein but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.< / directory> < / virtualhost>

Claims

1. A zero-code cloud deployment method for Axure applications, characterized by: include: Install the latest version of Axure software, configure the cloud server and create a cloud server instance; Generate an HTML folder containing all pages and interactions based on the presentation to be uploaded using Axure software; Configuring a standardized directory structure, and importing the HTML folder into the standardized directory structure for classified storage; Upload the HTML folder to the cloud server; Install and configure the web server in the cloud server and edit the storage path and access permissions of the Axure application corresponding to the HTML folder. Restart the cloud server for the configuration to take effect. Test the interactive functions of the Axure application through the public IP and access path.

2. The zero-code cloud deployment method for Axure applications according to claim 1 is characterized in that: The installation of the latest version of Axure software, configuration of the cloud server and creation of a cloud server instance include: Install Axure software and update to the latest version; Select an appropriate cloud server according to your needs, create a cloud server instance, enable object storage services, configure the data storage directory, and set security group rules.

3. The zero-code cloud deployment method for Axure applications according to claim 2 is characterized in that: The Axure software is used to generate an HTML folder containing all pages and interactions based on the presentation to be uploaded, including: Open the presentation to be uploaded in Axure software; Use Axure software for page layout and interactive logic design; Use the Publish to HTML function of Axure software to generate an HTML folder containing the interactive logic, and set the page title, page size and storage path when exporting.

4. The zero-code cloud deployment method for Axure applications according to claim 3 is characterized in that: The standardized directory structure includes: a data folder, a files folder, a plugins folder, and a resources folder; The data folder is used to store prototype metadata in the project; The files folder is used to store HTML files and their related resources, including images, CSS files, and JavaScript files; plugins folder, used to store, manage and use plugins; The resources folder is used to store non-code resources required for the project, including images, fonts, style sheets, JavaScript files, and configuration files.

5. The zero-code cloud deployment method for Axure applications according to claim 4 is characterized in that: Uploading the HTML folder to the cloud server includes: Connect to the cloud server instance using an SSH client or web console; Create a new folder on the cloud server to store the application's HTML folder and related resources; Use the file transfer protocol to upload the HTML folder and related resources generated by Axure to the designated folder on the cloud server, and ensure the integrity of the upload.

6. The zero-code cloud deployment method for Axure applications according to claim 5, characterized in that: The steps to install and configure the web server in the cloud server and edit the storage path and access permissions of the Axure application corresponding to the HTML folder are as follows: Determine whether a web server has been installed on the cloud server; If not, install the web server through the cloud server's package manager and edit the configuration file to specify the application directory and access permissions to complete service initialization; Save the configuration file and restart the Web server for the configuration to take effect.

7. The zero-code cloud deployment method for Axure applications according to claim 6, characterized in that: The interactive functions of the Axure application are tested through the public IP and access path, including: Enter the public IP address of the cloud server and the application access path in the browser to check whether the corresponding presentation can be accessed and interacted with normally; If you can access and interact normally, share the corresponding access link.

8. A zero-code cloud deployment system for Axure applications, characterized by: The system adopts the Axure application zero-code cloud deployment method according to any one of claims 1 to 7; The system comprises: The environment configuration module is used to install the latest version of Axure software, configure the cloud server, and create a cloud server instance; Export application module, used to generate an HTML folder containing all pages and interactions based on the presentation to be uploaded using Axure software; A configuration storage module is used to configure a standardized directory structure and import the HTML folder into the standardized directory structure for classified storage; Upload module, used to upload HTML folders to the cloud server; The server configuration module is used to install and configure the web server in the cloud server and edit the storage path and access permissions of the Axure application corresponding to the HTML folder. Restart the cloud server for the configuration to take effect. The access test module is used to test the interactive functions of Axure applications through public IP addresses and access paths.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the program, the steps of the zero-code cloud deployment method for Axure applications are implemented as described in any one of claims 1 to 7.

10. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the zero-code cloud deployment method for Axure applications are implemented as described in any one of claims 1 to 7.

Images