> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/kilo-mioty-service-center/getting-started/installation-local-vm-and-automation.md). # Installation: Local VM and Automation Install KiloCenter in a local Linux VM with Docker Compose to get repeatable MIOTY test setups for team onboarding. Use the current installation examples only in an isolated evaluation environment with test data. Published credentials, signing-key defaults and network exposure need correction before customer use. Changing only the administrator password is insufficient. Read the [installation safety notice](/kilo-mioty-service-center/security/installation-safety.md) before running commands. A local virtual machine gives your team a repeatable place to install and exercise KiloCenter Community Edition. Use it to learn MIOTY network setup and test installation changes before applying them to the service center you operate. ### What does this guide achieve? Create repeatable local environments for testing and team onboarding. ### Local VM Pattern Provision a Linux VM, clone the repository, and follow the steps from Installation: Docker Compose. Docker Compose is the recommended approach for VM-based setups since it handles all services — including KC-Web — automatically. ```bash cd kilocenter-modules cp .env.example .env docker compose run --rm certgen docker compose up --build -d ``` Open `http://localhost/` to verify KC-Web is running. ### What to Keep Consistent Keep these stable across VM environments: * Docker Compose service set (`postgres`, `redis`, `mosquitto`, `kc-identity`, `kilocenter`, `kc-gateway`, `kc-web`) * TLS certificate generation (run `certgen` before first start -- see Docker Compose Installation) * Port mappings and health check endpoints ### Why Use This Mode * Clean-room validation from a fresh machine * Repeatable onboarding for new team members * Pre-production environment rehearsals --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.kiloiot.io/kilo-mioty-service-center/getting-started/installation-local-vm-and-automation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.