This section will guide you through starting the backend and frontend for the first time without Docker, and calling protected APIs using a Token.

1) Start Backend

cargo run

Overview

QiLuo includes a built-in Code Generator that scans Entity files generated by sea-orm-cli and automatically produces complete backend and frontend CRUD code, dramatically reducing repetitive work.

The quality of the QiLuo repository can be comprehensively evaluated from multiple dimensions such as code design, technology selection, functional completeness, and engineering practices. It demonstrates overall maturity and is suitable for enterprise-level application scenarios. The detailed analysis is as follows:

Overview

QiLuo is an enterprise-level rapid development platform based on the Rust technology stack, using the Axum framework to build high-performance Web API services. This document provides detailed information about the design and functionality of each API interface module in the QiLuo system.

This file is the core routing management module of the entire application, responsible for unified management and organization of all API interface routes.

File location: mod.rs

Overview

The caching system is implemented based on the Rust technology stack, supporting multiple cache storage methods and providing a unified operation interface. The core features and implementation details are as follows:

This file is a memory-based cache implementation that provides complete memory caching functionality for Rust applications, serving as an alternative to Redis cache.

File location: memory.rs

This file is a Redis-based cache implementation that provides complete Redis operation functionality for Rust applications.

File location: [redis.rs](src\cache edis.rs)

Core Structure

Problem Background

When using Rust Cross for Linux cross-compilation, we often encounter openssl-sys related compilation errors, especially when compiling to musl targets. This is because OpenSSL depends on system libraries, and the development packages may be missing in the cross-compilation environment.

1. Core Functions

• Scheduled Task Management: Supports defining task execution cycles through Cron expressions, and supports operations such as adding, editing, deleting, and manually executing tasks.
• Task Types: Currently supports two types of tasks:
  • geturl: Periodically requests a specified URL.
  • invokefunction: Periodically calls a specified function (requires function name and parameters).
• Automatic Scheduling: The system periodically checks for due tasks and executes them automatically, while updating the next execution time for the tasks.
• Persistent Storage: Task configurations are stored in the sys_job table in the database, supporting dynamic configuration updates.