Skip to content

Commit

Permalink
Merge pull request #171: Bashbot Version 1.30
Browse files Browse the repository at this point in the history
Bashbot Version 1.30
  • Loading branch information
gnadelwartz authored Jan 18, 2021
2 parents 11daa48 + 5f21fcb commit ad532cc
Show file tree
Hide file tree
Showing 75 changed files with 1,631 additions and 1,231 deletions.
22 changes: 11 additions & 11 deletions README.html
Original file line number Diff line number Diff line change
Expand Up @@ -316,10 +316,10 @@ <h3>Your very first bashbot in a nutshell</h3>
<pre><code>/start

You are Botadmin
*Available commands*:
*• /start*: _Start bot and get this message_.
*• /help*: _Get this message_.
*• /info*: _Get shorter info message about this bot_....
Available commands:
/start: _Start bot and get this message_.
/help: _Get this message_.
/info: _Get shorter info message about this bot_....

/info

Expand All @@ -329,12 +329,12 @@ <h3>Your very first bashbot in a nutshell</h3>
<h3>Log files</h3>
<p>Bashbot actions are logged to <code>BASHBOT.log</code>. Telegram send/receive errors are logged to <code>ERROR.log</code>. Start bashbot in debug mode to see all messages sent to / received from Telegram, as well as bash command error messages.</p>
<p>To enable debug mode, start bashbot with debug as third argument: <code>bashbot start debug</code></p>
<pre><code>├── logs
│   ├── BASHBOT.log # log what your bot is doing ...
│   ├── ERROR.log # connection errors from / to Telegram API
│   │
│   ├── DEBUG.log # stdout/stderr of you bot (debug mode enabled)
│   └── MESSAGE.log # full text of all message send/received (debug mode enabled)</code></pre>
<pre><code>|__ logs
| |__ BASHBOT.log # log what your bot is doing ...
| |__ ERROR.log # connection errors from / to Telegram API
| |
| |__ DEBUG.log # stdout/stderr of you bot (debug mode enabled)
| |__ MESSAGE.log # full text of all message send/received (debug mode enabled)</code></pre>
<hr />
<h2>Security Considerations</h2>
<p>Running a Telegram Bot means it is connected to the public and you never know what's send to your Bot.</p>
Expand Down Expand Up @@ -390,6 +390,6 @@ <h3>Blocked by telegram?</h3>
<p>@Gnadelwartz</p>
<h2>That's it all guys!</h2>
<p>If you feel that there's something missing or if you found a bug, feel free to submit a pull request!</p>
<h4>$$VERSION$$ v1.21-0-gc85af77</h4>
<h4>$$VERSION$$ v1.30-0-g3266427</h4>
</body>
</html>
22 changes: 11 additions & 11 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -104,10 +104,10 @@ Now open the Telegram App on your mobile phone and start a chat with your bot (_
/start
You are Botadmin
*Available commands*:
*• /start*: _Start bot and get this message_.
*• /help*: _Get this message_.
*• /info*: _Get shorter info message about this bot_....
Available commands:
/start: _Start bot and get this message_.
/help: _Get this message_.
/info: _Get shorter info message about this bot_....
/info
Expand All @@ -124,12 +124,12 @@ Start bashbot in debug mode to see all messages sent to / received from Telegram
To enable debug mode, start bashbot with debug as third argument: `bashbot start debug`

```
├── logs
│   ├── BASHBOT.log # log what your bot is doing ...
│   ├── ERROR.log # connection errors from / to Telegram API
│   │
│   ├── DEBUG.log # stdout/stderr of you bot (debug mode enabled)
│   └── MESSAGE.log # full text of all message send/received (debug mode enabled)
|__ logs
| |__ BASHBOT.log # log what your bot is doing ...
| |__ ERROR.log # connection errors from / to Telegram API
| |
| |__ DEBUG.log # stdout/stderr of you bot (debug mode enabled)
| |__ MESSAGE.log # full text of all message send/received (debug mode enabled)
```

----
Expand Down Expand Up @@ -238,4 +238,4 @@ See `mycommnds.sh.dist` for an example.

If you feel that there's something missing or if you found a bug, feel free to submit a pull request!

#### $$VERSION$$ v1.21-0-gc85af77
#### $$VERSION$$ v1.30-0-g3266427
Loading

0 comments on commit ad532cc

Please sign in to comment.