No description
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-07-15 17:10:48 +02:00
apps workspace created 2026-06-13 13:59:30 +02:00
crm workspace created 2026-06-13 13:59:30 +02:00
processes added documentation for processes module 2026-07-15 17:10:48 +02:00
shared workspace created 2026-06-13 13:59:30 +02:00
.gitignore workspace created 2026-06-13 13:59:30 +02:00
Cargo.lock workspace created 2026-06-13 13:59:30 +02:00
Cargo.toml workspace created 2026-06-13 13:59:30 +02:00
README.md fixed typo in readme 2026-07-15 14:10:57 +02:00

manag3dlabs

This aims to be a complete management platform for mak3dlabs store Questo programma punta ad essere un gestionale completo per mak3dlabs, modulare abbastanza perché possa essere adattato a qualsiasi azienda,

structure

The UI will be implemented with leptos, but I don't want to depend too much on it, a cli will be useful too for testing or automations, I will try to have a minimalistic approach to every module, so the hacks and automations will be implemented elsewere. In the apps/ folder I will put the binaries, the user interfaces. In shared the types and utils that every other crate could depend on. then every moudle will have its own folder, now I divided core and ui, so that I don't put leptos code specific for the module inside the apps/web project. The first two modules I will implement are processes and crm.

processes

this module will be a task runner, I am working on a standardized structure for scripts, a git repository with a metadata format (Wip) will be required, based on the parsing of that metadata the processes module will ask you for the inputs, clone the repo in a temporary directory, run the script and optionally give you output. An example of script for this module is at http://192.168.1.48:3000/leo/3dmodels_renderer.

Warning

no containerization or vm will be implemented in the beginning, so check the scripts you run before running them

inventory

this module will read and manage the inventory. I still don't have a clear structure in mind for this module, it will be implemented after processes.

members = [ "apps/cli", "apps/web", "inventory/core", "inventory/ui", "processes/core", "processes/ui", "shared", ]