about summary refs log tree commit diff
path: root/README.markdown
diff options
context:
space:
mode:
authorVincent Ambo <tazjin@gmail.com>2017-12-26T10·15+0100
committerVincent Ambo <tazjin@gmail.com>2017-12-26T10·15+0100
commitabe8419b034600b8cea37a17407ed933766cfbf5 (patch)
treef680c290b5c71f356b431c11ee2ed8cf3762196f /README.markdown
parente50e2acde039f8a16373c653aaa1e76b37bd02a2 (diff)
docs(README): Update docs with a note about configuration
Diffstat (limited to 'README.markdown')
-rw-r--r--README.markdown11
1 files changed, 8 insertions, 3 deletions
diff --git a/README.markdown b/README.markdown
index e4e8809056c0..064742c0091f 100644
--- a/README.markdown
+++ b/README.markdown
@@ -32,9 +32,9 @@ aids with reminding users of recurring tasks. Some basic ideas:
 * It should work mostly passively without much user interaction.
 
 I believe that the basic (*very* simple) idea behind Gemma solves these issues.
-Unfortunately my previous relationship fell apart before I actually got to test
-this out in a real-life situation involving multiple people, but feedback from
-other potential test subjects would be welcome! :)
+Unfortunately my living situation changed before I actually got to test this out
+in a real-life situation involving multiple people, but feedback from other
+potential test subjects would be welcome! :)
 
 ## Overview
 
@@ -88,4 +88,9 @@ distribution. Basically you need to know Common Lisp (in which case you'll know
 how to get the backend running) and have `elm-reactor` installed to run the
 development version of the frontend application.
 
+Gemma is configured via a configuration file that should be located either at
+`/etc/gemma/config.lisp` or at a custom location specified via the environment
+variable `GEMMA_CONFIG`. Have a look at the `config.lisp` file in the repository
+root for an example.
+
 [wrote an article]: http://www.harpersbazaar.com/culture/features/a12063822/emotional-labor-gender-equality/