2019-05-16 14:43:44 +00:00
|
|
|
#### [Home](../README.md)
|
|
|
|
## Customize bashbots environment
|
|
|
|
This section describe how you can customize bashbot to your needs by setting environment variables.
|
|
|
|
|
|
|
|
|
|
|
|
### Change file locations
|
|
|
|
In standard setup bashbot is self containing, this means you can place 'telegram-bot-bash' any location
|
|
|
|
and run it from there. All files - programm, config, data etc - will reside in 'telegram-bot-bash'.
|
|
|
|
|
|
|
|
If you want to have other locations for config, data etc, define and export the following environment variables.
|
|
|
|
**Note: all specified directories and files must exist or running 'bashbot.sh' will fail.**
|
|
|
|
|
|
|
|
#### BASHBOT_ETC
|
|
|
|
Location of the files ```commands.sh```, ```mycommands.sh```, ```token```, ```botadmin```, ```botacl``` ...
|
|
|
|
```bash
|
|
|
|
unset BASHBOT_ETC # keep in telegram-bot-bash (default)
|
|
|
|
export BASHBOT_ETC "" # keep in telegram-bot-bash
|
|
|
|
|
|
|
|
export BASHBOT_ETC "/etc/bashbot" # unix like config location
|
|
|
|
|
|
|
|
export BASHBOT_ETC "/etc/bashbot/bot1" # multibot configuration bot 1
|
|
|
|
export BASHBOT_ETC "/etc/bashbot/bot2" # multibot configuration bot 2
|
|
|
|
```
|
|
|
|
|
|
|
|
e.g. /etc/bashbot
|
|
|
|
|
|
|
|
#### BASHBOT_VAR
|
|
|
|
Location of runtime data ```data-bot-bash```, ```count```
|
|
|
|
```bash
|
|
|
|
unset BASHBOT_VAR # keep in telegram-bot-bash (default)
|
|
|
|
export BASHBOT_VAR "" # keep in telegram-bot-bash
|
|
|
|
|
|
|
|
export BASHBOT_VAR "/var/spool/bashbot" # unix like config location
|
|
|
|
|
|
|
|
export BASHBOT_VAR "/var/spool/bashbot/bot1" # multibot configuration bot 1
|
|
|
|
export BASHBOT_VAR "/var/spool/bashbot/bot2" # multibot configuration bot 2
|
|
|
|
```
|
|
|
|
|
|
|
|
#### BASHBOT_JSONSH
|
|
|
|
Full path to JSON.sh script, default: './JSON.sh/JSON.sh', must end with '/JSON.sh'.
|
|
|
|
```bash
|
|
|
|
unset BASHBOT_JSONSH # telegram-bot-bash/JSON.sh/JSON.sh (default)
|
|
|
|
export BASHBOT_JSONSH "" # telegram-bot-bash/JSON.sh/JSON.sh
|
|
|
|
|
|
|
|
export BASHBOT_JSONSH "/usr/local/bin/JSON.sh" # installed in /usr/local/bin
|
|
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
### Change config values
|
|
|
|
|
|
|
|
#### BASHBOT_URL
|
|
|
|
Uses given URL instead of offical telegram API URL, useful if you have your own telegram server or for testing.
|
|
|
|
|
|
|
|
```bash
|
|
|
|
unset BASHBOT_URL # use Telegram URL https://api.telegram.org/bot<token> (default)
|
|
|
|
|
|
|
|
export BASHBOT_URL "" # use use Telegram https://api.telegram.org/bot<token>
|
|
|
|
|
|
|
|
export BASHBOT_URL "https://my.url.com/bot" # use your URL https://my.url.com/bot<token>
|
|
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
#### BASHBOT_TOKEN
|
|
|
|
|
|
|
|
#### BASHBOT_WGET
|
|
|
|
Bashbot uses ```curl``` to communicate with telegram server. if ```curl``` is not availible ```wget``` is used.
|
|
|
|
If 'BASHBOT_WGET' is set to any value (not undefined or not empty) wget is used even is curl is availible.
|
|
|
|
```bash
|
|
|
|
unset BASHBOT_WGET # use curl (default)
|
|
|
|
export BASHBOT_WGET "" # use curl
|
|
|
|
|
|
|
|
export BASHBOT_WGET "yes" # use wget
|
|
|
|
export BASHBOT_WGET "no" # use wget!
|
|
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
#### BASHBOT_SLEEP
|
|
|
|
Instead of polling permanently or with a fixed delay, bashbot offers a simple adaptive polling.
|
|
|
|
If messages are recieved bashbot polls with no dealy. If no messages are availible bashbot add 100ms delay
|
|
|
|
for every poll until the maximum of BASHBOT_SLEEP ms.
|
|
|
|
```bash
|
|
|
|
unset BASHBOT_SLEEP # 5000ms (default)
|
|
|
|
export BASHBOT_SLEEP "" # 5000ms
|
|
|
|
|
|
|
|
export BASHBOT_SLEEP "1000" # 1s maximum sleep
|
|
|
|
export BASHBOT_SLEEP "10000" # 10s maximum sleep
|
|
|
|
export BASHBOT_SLEEP "1" # values < 1000 disables sleep (not recommended)
|
|
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
### Testet configs as of v.07 release
|
|
|
|
**Note: Environment variables are not stored, you must setup them before every call to bashbot.sh, e.g. from a script.**
|
|
|
|
|
|
|
|
#### simple Unix like config, for one bot. bashbot is installed in '/usr/local/telegram-bot-bash'
|
|
|
|
```bash
|
|
|
|
# Note: all dirs and files must exist!
|
|
|
|
export BASHBOT_ETC "/etc/bashbot"
|
|
|
|
export BASHBOT_VAR "/var/spool/bashbot"
|
|
|
|
|
|
|
|
/usr/local/telegram-bot-bash/bashbot.sh start
|
|
|
|
```
|
|
|
|
|
|
|
|
#### Unix like config for one bot. bashbot.sh is installed in '/usr/bin'
|
|
|
|
```bash
|
|
|
|
# Note: all dirs and files must exist!
|
|
|
|
export BASHBOT_ETC "/etc/bashbot"
|
|
|
|
export BASHBOT_VAR "/var/spool/bashbot"
|
|
|
|
export BASHBOT_JSONSH "/var/spool/bashbot"
|
|
|
|
|
|
|
|
/usr/local/bin/bashbot.sh start
|
|
|
|
```
|
|
|
|
|
|
|
|
#### simple multibot config, everything is keept inside 'telegram-bot-bash' dir
|
|
|
|
```bash
|
|
|
|
# config for running Bot 1
|
|
|
|
# Note: all dirs and files must exist!
|
|
|
|
export BASHBOT_ETC "./mybot1"
|
|
|
|
export BASHBOT_VAR "./mybot1"
|
|
|
|
|
|
|
|
/usr/local/telegram-bot-bash/bashbot.sh start
|
|
|
|
```
|
|
|
|
|
|
|
|
```bash
|
|
|
|
# config for running Bot 2
|
|
|
|
# Note: all dirs and files must exist!
|
|
|
|
export BASHBOT_ETC "./mybot2"
|
|
|
|
export BASHBOT_VAR "./mybot2"
|
|
|
|
|
|
|
|
/usr/local/telegram-bot-bash/bashbot.sh start
|
|
|
|
```
|
|
|
|
|
|
|
|
#### [Prev Notes for Developers](7_develop.md)
|
|
|
|
|
2019-05-18 18:25:18 +00:00
|
|
|
#### $$VERSION$$ v0.80-dev3-0-g31a5d00
|
2019-05-16 14:43:44 +00:00
|
|
|
|