diff options
| author | Stef Walter <stefw@redhat.com> | 2015-10-08 10:45:46 +0200 |
|---|---|---|
| committer | Stef Walter <stefw@redhat.com> | 2015-10-08 10:45:46 +0200 |
| commit | 7bbeda1b7882b284a082372f879fba146a8d078d (patch) | |
| tree | 9dcde9fc08d7622e90b171c683a6202f9d5b59f3 | |
| parent | 4ac37039be9f1675b7b07760ccf06c89a837309f (diff) | |
Clarify Vagrantfile is just for package assets
| -rw-r--r-- | content/cockpit/cockpit-vagrantfile.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/content/cockpit/cockpit-vagrantfile.md b/content/cockpit/cockpit-vagrantfile.md index 74f6ff7..7e2fe11 100644 --- a/content/cockpit/cockpit-vagrantfile.md +++ b/content/cockpit/cockpit-vagrantfile.md @@ -9,7 +9,8 @@ you can test or develop Cockpit. The VM is isolated from your main system so any you change via Cockpit will only happen in the VM. The Vagrant VM mounts the Cockpit package assets from your git repository checkout, so when you make on the -host system, you can refresh the browser and immediately see the resulting changes. +host system, you can refresh the browser and immediately see the resulting changes. For changes to +C code, the Cockpit binaries would have to be rebuilt and testing via Vagrant won't work. ## Getting Started |