Linux command
micasa 命令
文本
复制后可按需替换文件名、目录或参数。
常用示例
Launch micasa
micasa
Explore with sample data
micasa --demo
Use a specific database file
micasa [path/to/house.db]
Persist demo data
micasa --demo [path/to/demo.db]
Print the resolved database path
micasa --print-path
说明
micasa is a keyboard-driven terminal UI application for managing everything about your home. It tracks maintenance schedules, projects, incidents, vendor quotes, appliances, warranties, service history, and file attachments. All data is stored in a single local SQLite file — no cloud, no account, no subscriptions. The application features an integrated LLM assistant that can help generate maintenance suggestions and project plans when connected to a local Ollama instance or any OpenAI-compatible API.
参数
- --demo
- Launch with fictitious sample data: a house profile, projects, maintenance items, appliances, service log entries, and quotes. When combined with a _db-path_, demo data persists to disk instead of staying in-memory.
- --print-path
- Print the resolved database path to stdout and exit. Useful for scripting and backup.
- --version
- Show version and exit.
- -h, --help
- Display help information.
- _db-path_
- Optional positional argument specifying the SQLite database file location.
FAQ
What is the micasa command used for?
micasa is a keyboard-driven terminal UI application for managing everything about your home. It tracks maintenance schedules, projects, incidents, vendor quotes, appliances, warranties, service history, and file attachments. All data is stored in a single local SQLite file — no cloud, no account, no subscriptions. The application features an integrated LLM assistant that can help generate maintenance suggestions and project plans when connected to a local Ollama instance or any OpenAI-compatible API.
How do I run a basic micasa example?
Run `micasa` in a terminal, then adjust file names, paths, flags, or remote targets for your system.
What does --demo do in micasa?
Launch with fictitious sample data: a house profile, projects, maintenance items, appliances, service log entries, and quotes. When combined with a _db-path_, demo data persists to disk instead of staying in-memory.