From e04e8a0eabb2bc6b0aab5277fe4964b1a48014b5 Mon Sep 17 00:00:00 2001 From: "Phyks (Lucas Verney)" Date: Thu, 15 Jun 2017 13:48:25 +0200 Subject: [PATCH] Update getting started doc to add tips --- doc/0.getting_started.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/doc/0.getting_started.md b/doc/0.getting_started.md index cb329f4..f1a459f 100644 --- a/doc/0.getting_started.md +++ b/doc/0.getting_started.md @@ -130,3 +130,25 @@ If you want to build the web assets, you can use `npm run build:dev` (respectively `npm run watch:dev` to build continuously and monitor changes in source files). You can use `npm run build:prod` (`npm run watch:prod`) to do the same in production mode (with minification etc). + + +## Tips + +### Running with multiple configs + +Let's say you are looking for a place in different places far apart (e.g. both +a house in the country for the weekends and a place in a city for the week), +you can use multiple configuration file (in this case, two configuration +files) to define everything. + +Indeed, `serve` command for the web app only use a subset of the +configuration, basically only the `data_directory`, `database` URI and so on. +So, you are free to use any config file for `serve` command and still run +`import` commands multiple times with different configuration files, for +different housing queries. + +This is kind of a hack on the current system, but is working! + +*Note*: You can also use this tip if you are living in a city split across +multiple postal codes and want to implement constraints such as "close to +place X if postal code is Y".