From 8a145cc997799f82267084f4046021c651dee01a Mon Sep 17 00:00:00 2001 From: Chris Caron Date: Mon, 30 Sep 2019 12:36:36 -0400 Subject: [PATCH] Updated config_text (markdown) --- config_text.md | 20 +++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/config_text.md b/config_text.md index eaa4ea9..b7d8db9 100644 --- a/config_text.md +++ b/config_text.md @@ -1,5 +1,13 @@ -## Text Based Configuration Files -The TEXT Based configuration files are pretty straight forward. You just provide a list of your notification URLs. For details on how to use this configuration file [[click here|config]]. +## Text Based Apprise Configuration +The TEXT Based configuration files are pretty straight forward and very easy to work with. You just provide a list of your notification URLs like so. +```apache +# Use pound/hashtag (#) characters to comment lines +# Here is an example of a very basic entry (without tagging): +mailto://someone:theirpassword@gmail.com +slack://token_a/token_b/token_c +``` + +Tagging is a very feature-rich aspect of Apprise, and you can easily associate tags with your URLs by just placing them before your URL you define. If you want to specify more then one tag, just separate them with a space and/or comma. ```apache # Use pound/hashtag (#) characters to comment lines # The syntax is = or just on each line @@ -18,4 +26,10 @@ desktop=gnome:// # notification service URL: tv,kitchen=kodi://myuser:mypass@kitchen.hostame tv,basement=kodi://myuser:mypass@basement.hostame -``` \ No newline at end of file +``` + +## Web Hosted TEXT Configuration +Apprise can retrieve configuration files from over a network as well using the HTTP protocol. +For HTTP requests, the **Content-Type** HTTP Header (_which defines Mime Type_) is very important. Apprise will parse remote network hosted configuration files as TEXT so long as you're using one of the following **Content-Type** entries: +- `text/plain` +- `text/html` \ No newline at end of file