From 6718d241338484b0f33fdad36981e82c5d7140e7 Mon Sep 17 00:00:00 2001
From: "Kay Marquardt (Gnadelwartz)" <kay@rrr.de>
Date: Wed, 9 Sep 2020 17:48:47 +0200
Subject: [PATCH] use zip and or tar files

---
 doc/0_install.md | 26 ++++++++++++++++----------
 1 file changed, 16 insertions(+), 10 deletions(-)

diff --git a/doc/0_install.md b/doc/0_install.md
index c759e61..18fa362 100644
--- a/doc/0_install.md
+++ b/doc/0_install.md
@@ -5,25 +5,25 @@
 1. Go to the directory you want to install bashbot, e.g.
     * your $HOME directory (install and run with your user-ID)
     * /usr/local if you want to run as service
-2. [Download latest release zip from github](https://github.com/topkecleon/telegram-bot-bash/releases) and extract all files. 
+2. [Download latest release zip / tar archive from github](https://github.com/topkecleon/telegram-bot-bash/releases) and extract all files. 
 3. Change into the directory ```telegram-bot-bash```
-4. Activate the bot example commands  ``cp mycommands.sh.dist mycommands.sh```
+4. Activate the bot example commands  ```cp mycommands.sh.dist mycommands.sh```
 5. Run ```./bashbot.sh init``` to setup the environment and enter your Bots token given by botfather.
 
-Edit 'mycommands.sh to your needs.
+Edit ```mycommands.sh``` to your needs.
 Now your Bot is ready to start ...
 
 **If you are new to Bot development read [Bots: An introduction for developers](https://core.telegram.org/bots)**
 
 
-###  Update bashbot
+### Update bashbot
 
-**Note: all files including 'mycommands.sh' may overwritten, make a backup!**
+**Note: all files including ```mycommands.sh``` may overwritten, make a backup!**
 
 1. Go to the directory where you had installed bashbot, e.g.
     * your $HOME directory
     * /usr/local
-2. [Download latest release zip from github](https://github.com/topkecleon/telegram-bot-bash/releases)
+2. [Download latest release zip / tar archive from github](https://github.com/topkecleon/telegram-bot-bash/releases)
 3. Stop all running instances of bashbot
 4. Extract all files to your existing bashbot dir 
 5. Run ```sudo ./bashbot.sh init``` to setup your environment after the update
@@ -32,11 +32,17 @@ If you modified ```commands.sh``` move your changes to ```mycommands.sh```, this
 
 Now you can restart your bashbot instances.
 
+### Get zip / tar archive on command line
+
+```bash
+wget -q https://github.com/$(wget -q https://github.com/topkecleon/telegram-bot-bash/releases/latest -O - | egrep '/.*/.*/.*tar.gz' -o)
+```
+
 
 ### Install from github
 
 The first install can also be done from github, updates should always done from the zip or tar archive to avoid
-overwriting your config and mycommands.sh files.
+overwriting your config and ```mycommands.sh``` files.
 
 1. Go to the directory you want to install bashbot, e.g.
     * your $HOME directory (install and run with your user-ID)
@@ -117,8 +123,8 @@ if tmux ls | grep -v send | grep -q "$copname"; then inproc; fi
 must be replaced by ```send_interactive "${CHATD[ID]}" "${MESSAGE}"```
 
 ### Do not edit commands.sh
-From version 0.60 on your commands must be placed in 'mycommands.sh'. If you update from a version with your commands
-in 'commands.sh' move all your commands and functions to 'mycommands.sh'.
+From version 0.60 on your commands must be placed in ```mycommands.sh```. If you update from a version with your commands
+in 'commands.sh' move all your commands and functions to ```mycommands.sh```.
 
 From version 0.80 on 'commands.sh' will be overwritten on update!
 
@@ -147,5 +153,5 @@ The old format is supported for backward compatibility, but may fail for corner
 
 #### [Next Create Bot](1_firstbot.md)
 
-#### $$VERSION$$ v1.0-19-gc2a110a
+#### $$VERSION$$ v1.0-20-gc292292