xmaza --version xmaza init xmaza start to verify and start it. If you hit permission errors, try adjusting file ownership or using a virtual environment/container to isolate dependencies. For config, edit ~/.xmaza/config.yaml (or the path shown by xmaza config --show) to customize ports, logging, or feature flags.
curl -sSL https://example.com/xmaza/install.sh | bash or clone and build:
git clone https://example.com/xmaza.git cd xmaza make && sudo make install On Windows, use the installer .exe or the package manager recommended by the project and follow prompts.
xmaza --version xmaza init xmaza start to verify and start it. If you hit permission errors, try adjusting file ownership or using a virtual environment/container to isolate dependencies. For config, edit ~/.xmaza/config.yaml (or the path shown by xmaza config --show) to customize ports, logging, or feature flags.
curl -sSL https://example.com/xmaza/install.sh | bash or clone and build: xmaza install
git clone https://example.com/xmaza.git cd xmaza make && sudo make install On Windows, use the installer .exe or the package manager recommended by the project and follow prompts. xmaza --version xmaza init xmaza start to verify
