A Vagrantfile is available into virtualization/vagrant folder for quickly spinning up a Linux virtual machine running Home Assistant. This can be beneficial for those who want to experiment with Home Assistant and/or developers willing to easily test local changes and run test suite against them.
A Vagrantfile is available into virtualization/vagrant folder for quickly spinning up a Linux virtual machine running Home Assistant. This can be beneficial for those who want to experiment with Home Assistant and/or developers willing to easily test local changes and run test suite against them. In the same virtualization/vagrant folder there’s also a provision.sh shell script which provides an easy way to interact with the Home Assistant instance running within the Vagrant VM.
Vagrant is intended for testing/development only. It is NOT recommended for permanent installations. @@ -100,7 +100,7 @@ Vagrant is intended for testing/development only. It is NOT recommended for perm
You must have Vagrant and Virtualbox installed on your workstation.
+You must have Vagrant and Virtualbox installed on your workstation. Vagrant and Virtualbox support all the main platforms, including Windows, MacOS and Linux.
au
Create the Vagrant VM and start Home Assistant
-$ vagrant up
+$ ./provision.sh setup
-This will download and start a virtual machine using Virtualbox, which will internally setup the development environment necessary to start Home Assistant process and run test suite as well. After the VM has started successfully, the Home Assistant frontend will be accessible locally from your browser at http://localhost:8123
+This will download and start a virtual machine using Virtualbox, which will internally setup the development environment necessary to start Home Assistant. The whole process might take up to 30 minutes to complete, depending on Internet connection speed and workstation resources. After the VM has started successfully, the Home Assistant frontend will be accessible locally from your browser at http://localhost:8123
Stopping Vagrant
To shutdown the Vagrant host:
-$ vagrant halt
+$ ./provision.sh stop
-To start it again, just run vagrant up
+To start it again:
+
+$ ./provision.sh start
+
+
Restarting Home Assistant process to test changes
The root home-assistant directory on your workstation will be mirrored with /home-assistant inside the VM. In virtualization/vagrant there’s also a config folder that you can use to drop configuration files (Check the Configuration section in the docmentation for more information about how to configure Home Assistant).
-Any changes made to the local directory on your workstation will be available from the Vagrant host, so to apply your changes to the Home Assistant process, just restart it:
+Any changes made to the local directory on your workstation will be available from the Vagrant host, so to apply your changes to the Home Assistant process, just restart it using the provided provision.sh wrapper script:
-$ touch restart ; vagrant provision
+$ ./provision.sh restart
+
+This command will only restart the Home Assistant process inside the Vagrant VM, it will not reboot the virtual machine. If that’s what you want, the right command is vagrant reload
+
+
Run test suite (Tox)
-To run tests against your changes:
+To run tests against the local version of Home Assistant code:
-$ touch run_tests ; vagrant provision
+$ ./provision.sh tests
Cleanup
-To completely remove the VM:
+To completely remove the VM
-$ rm setup_done ; vagrant destroy -f
+$ ./provision.sh destroy
-You can now recreate a completely new Vagrant host with vagrant up
+To completely remove the VM and setup a fresh new environment:
+$ ./provision.sh recreate
+
+
diff --git a/sitemap.xml b/sitemap.xml
index 7e4760c20a..8a1ad9035b 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -2954,62 +2954,62 @@
https://home-assistant.io/demo/frontend.html
-2017-03-08T09:16:22+00:00
+2017-03-08T11:50:01+00:00
https://home-assistant.io/demo/index.html
-2017-03-08T09:16:22+00:00
+2017-03-08T11:50:01+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2017-03-08T09:16:22+00:00
+2017-03-08T11:50:01+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2017-03-08T09:16:22+00:00
+2017-03-08T11:50:01+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2017-03-08T09:16:22+00:00
+2017-03-08T11:50:01+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2017-03-08T09:16:22+00:00
+2017-03-08T11:50:01+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2017-03-08T09:16:22+00:00
+2017-03-08T11:50:01+00:00
https://home-assistant.io/demo/panels/ha-panel-history.html
-2017-03-08T09:16:22+00:00
+2017-03-08T11:50:01+00:00
https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2017-03-08T09:16:22+00:00
+2017-03-08T11:50:01+00:00
https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2017-03-08T09:16:22+00:00
+2017-03-08T11:50:01+00:00
https://home-assistant.io/demo/panels/ha-panel-map.html
-2017-03-08T09:16:22+00:00
+2017-03-08T11:50:01+00:00
https://home-assistant.io/googlef4f3693c209fe788.html
-2017-03-08T09:16:22+00:00
+2017-03-08T11:50:01+00:00
https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2017-03-08T09:16:23+00:00
+2017-03-08T11:50:01+00:00
https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2017-03-08T09:16:23+00:00
+2017-03-08T11:50:01+00:00
https://home-assistant.io/static/mdi-demo.html
-2017-03-08T09:16:23+00:00
+2017-03-08T11:50:01+00:00