使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/olafkfreund/nix-skills --skill microvm-nix開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
microvm.nix
Read the repository instructions, flake inputs, target host, VM nixosConfigurations, imports, and existing microVM modules before editing. Preserve the project's module and feature-flag conventions.
Use declaring VMs and the introduction for the module shape. Use declarative deployment, host integration, and host systemd for host-managed VMs. Consult options, the networking references, and shares only for the relevant workload.
Distinguish a VM's NixOS configuration from the host's microvm.vms management. Treat host paths, shared stores, networking, interfaces, and device passthrough as trust boundaries. Existing deployed VMs may require the documented microvm update flow instead of an automatic host rebuild update.
Validate the flake and dry-build the affected host or VM before starting or updating runtime services.
Nix style
- Never search
/nix/store(for examplefind /nix/store/*foo-* -name libfoo.so)
and never copy a literal store path. Find the providing package with nix-locate, and refer to it through Nix: ${pkgs.foo}/lib or lib.makeLibraryPath [ pkgs.foo ].
- Do not quote attribute names that are valid identifiers
([A-Za-z_][A-Za-z0-9_'-]*, dashes included). Write pkgs.foo-bar and packages.x86_64-linux, not pkgs."foo-bar". Quote only other names (".config/foo", "2.0"), the keywords assert else if in inherit let or rec then with, and interpolations ("${name}"). Upstream examples in references sometimes quote needlessly; do not copy that style.