Use ./config for HA configuration (#102)

.gitignore

@@ -13,16 +13,5 @@ coverage.xml
 
 
 # Home Assistant configuration
-.cloud
-.HA_VERSION
-.storage
-automations.yaml
-blueprints
-configuration.yaml
-deps
-home-assistant_v2*
-home-assistant.log*
-tts
-scenes.yaml
-scripts.yaml
-secrets.yaml
+config/*
+!config/configuration.yaml

CONTRIBUTING.md

@@ -53,7 +53,7 @@ This custom component is based on [integration_blueprint template](https://githu
 It comes with development environment in a container, easy to launch
 if you use Visual Studio Code. With this container you will have a stand alone
 Home Assistant instance running and already configured with the included
-[`configuration.yaml`](./configuration.yaml)
+[`configuration.yaml`](./config/configuration.yaml)
 file.
 
 ## License

scripts/develop

@@ -4,5 +4,17 @@ set -e
 
 cd "$(dirname "$0")/.."
 
+# Create config dir if not present
+if [[ ! -d "${PWD}/config" ]]; then
+    mkdir -p "${PWD}/config"
+    hass --config "${PWD}/config" --script ensure_config
+fi
+
+# Set the path to custom_components
+## This let's us have the structure we want <root>/custom_components/integration_blueprint
+## while at the same time have Home Assistant configuration inside <root>/config
+## without resulting to symlinks.
+export PYTHONPATH="${PYTHONPATH}:${PWD}/custom_components"
+
 # Start Home Assistant
-hass -c . --debug
+hass --config "${PWD}/config" --debug