X-Git-Url: https://apps.delaporte.us/gitweb/matrix-cadbury.git/blobdiff_plain/63002ce55d83025446db2d0ea81de96cedcd9aa2..f86c05d41f140d19a41680a5002ff47554ebab2e:/README.md

diff --git a/README.md b/README.md
index 1b48dfd..e0449eb 100644
--- a/README.md
+++ b/README.md
@@ -13,6 +13,12 @@ the purpose of `Cadbury` is to compose several together under a single Matrix bo
 
 Create a bot account on your Matrix server, and set the necessary environment variables: `MATRIX_SERVER`, `MATRIX_BOT`, `MATRIX_BOT_PWD`.
 
+Set `MATRIX_DATA_DIR` to an existing directory path where you would like Cadbury to store any `sqlite3` databases.
+
+Expect files such as `goals.db` and `chores.db` to appear there after you tell Cadbury `!chore setup` and `!goal setup`, etc.
+
+Ensure that `python` and `sqlite3` are installed and available on the path.
+
 > Tip: Cadbury has no use for email. Your Matrix server may allow creating the bot account without an email account, using a `token` registration type.
 
 Run the bot with `make serve`,
@@ -27,6 +33,16 @@ Then use the following command to launch the bot:
 
 	.venv/bin/python app.py
 
+## Chatting
+
+Invite you Cadbury bot to a Matrix channel, and it will accept automatically, if it can.
+
+> Tip: Additional setup is required to add a Matrix bot to an encrypted channel.
+
+Use `!goal help` and `!chore help`, to get started.
+
+> Tip: Many bot roles require creating a sqlite3 database, and may require you to tell Cadbuary something like `!chore setup` one initial time to create the database file.
+
 ## Remixing
 
 When creating your own unique mix of bot roles, consider creating a public fork of