From ddf71c1afcc3f04bca1966e0c41a60be8aa6ff27 Mon Sep 17 00:00:00 2001 From: theolind Date: Sat, 28 Feb 2015 21:42:12 +0100 Subject: [PATCH] Wrote a short blog post about yaml migration --- ...28-home-assistant-migrating-to-yaml.markdown | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 source/_posts/2015-02-28-home-assistant-migrating-to-yaml.markdown diff --git a/source/_posts/2015-02-28-home-assistant-migrating-to-yaml.markdown b/source/_posts/2015-02-28-home-assistant-migrating-to-yaml.markdown new file mode 100644 index 00000000000..1ae32e42d37 --- /dev/null +++ b/source/_posts/2015-02-28-home-assistant-migrating-to-yaml.markdown @@ -0,0 +1,17 @@ +--- +layout: post +title: "Home Assistant moving to YAML" +description: "Configuration will now be more flexible" +date: 2015-02-28 20:38:00 +0100 +date_formatted: February 28, 2015 +comments: true +--- + +Home Assistant is now using [YAML](http://yaml.org/) for it's configuration file. +YAML allows the use of lists, which should make the configuration file a bit more flexible and useful. The new configuration file format is backwards compatible with existing components. Because of this, there is no need for component developers to update their components. + +The new file is named configuration.yaml and if it can't be found in your config directory, Home Assistant will instead try to find the old configuration file, home-assistant.conf. + +The home-assistant.conf.example has been replaced with an updated configuration.yaml.example. + +Users of Home Assistant should migrate as the old configuration format will be depicted.