How sadroad/auspex works
The Client Application
• Located in the "client" directory with its own Cargo.toml and source files (client/src/main.rs).
• Likely responsible for user interaction or providing an interface that communicates with the backend server.
The Server Application
• Located in the "server" directory, again with its own Cargo.toml and a main source file (server/src/main.rs).
• This likely handles backend logic, business processes, data management, or acting as an API server.
Additional Artifacts and Configuration
• The top-level Cargo.lock, Cargo.toml indicate project-wide dependency tracking (if there is any shared configuration).
• Presence of flake.nix and flake.lock suggests that the project might use Nix for reproducible builds and dependency management.
• The justfile might be used for task automation (e.g., building, running tests, or deployments).
Main Components
a. Client (Frontend): Represent the client package as a component. Label it clearly as “Client (Rust)” or “User Interface”.
b. Server (Backend): Create a separate block for the server with a clear label, e.g., “Server (Rust)”.
c. Build and Deployment Tools: Optionally include nodes for “Nix Flake” and “Task Runner (Just)” to indicate the configuration and automation tooling used.
Relationships and Interactions
c. (Optional) Represent the integration between the Nix-based build environment and the overall build process, showing how it interacts with both client and server components.
Relevant Technologies and Frameworks
a. Rust: Mark both client and server as being built using Rust, which may have implications for how communication and concurrency are handled.
b. Cargo: For dependency management and building the Rust applications.
c. Nix: As indicated by flake.nix and flake.lock, highlight that there is a configuration for reproducible builds.