version bump

README.md

@@ -26,6 +26,15 @@ source /opt/profile/profile.sh
 It's not recommended to load that profile in `/etc/profile` as users' `.bashrc`
 files might interfere with some aliases and functions defined in profile.
 
+### 2.1. Initial configuration
+Copy the example configuration file and customise it to your needs:
+```bash
+cp <installpath>/profile/doc/profile.conf.example <installpath>/profile/profile.conf
+```
+`profile.conf` is git-ignored so your personal settings will never be
+accidentally committed. All keys are optional — sensible defaults apply when
+unset. See [section 4](#4-configuration) for the full reference.
+
 ## 3. What's the purpose?
 profile gives access to numerous functions, aliases and to an advanced prompt.
 All functions are organized into modules under the `profile.d/` directory and
@@ -89,6 +98,10 @@ load time, which exports every key in that section as an environment variable.
 Unknown keys are silently ignored; all keys are optional — sensible defaults
 apply when unset.
 
+`profile.conf` is listed in `.gitignore` so personal values (API keys, cities,
+compiler flags, …) are never accidentally staged. Start from the annotated
+template at `doc/profile.conf.example` (see [section 2.1](#21-initial-configuration)).
+
 ### 4.1. Core sections
 
 | Section | Purpose |