GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: Muhammad Rizki <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: GNU/Weeb Mailing List <[email protected]>,
	Alviro Iskandar Setiawan <[email protected]>
Subject: Re: [PATCH v2 0/3] New Discord bot and full refactor scripts
Date: Sat, 27 Aug 2022 23:00:53 +0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 27/08/2022 17.40, Ammar Faizi wrote:
> On 8/27/22 10:02 AM, Muhammad Rizki wrote:
>> Good morning, sir
>> In this series I created a Discord bot, the functionality and features
>> still the same with the Telegram bot, this series contains full refactor
>> both Discord and Telegram bot scripts which is more cleaner.
>>
>> Refactors:
>> Moving the atom related files outside the bot scripts which is can be
>> reusable with each other bot scripts.
>> Moving the database related files and create a directory for themselves,
>> this method is more clean so it's more easier to develop and maintain.
>> Mass refactor for Telegram and Discord bot scripts.
>> Combine the SQL file for Discord and Telegram bot, so we don't have to
>> make a new database.
> 
> Can you tell a bit how to setup and test this?
> 

How to setup:
- Install the package first with `requirements.txt` in the `dscord` or 
`telegram` directory
- Set the environment in the `daemon` workdir like `discord.env` or 
`telegram.env`
- Set the `config.py` for discord or telegram
- Run the bot by running `python3 dc.py` or `python3 tg.py` in the 
daemon workdir

The reason I naming the discord directory with `dscord` is because for 
preventing conflict with `discord.py` library, if you have any question 
just tell me, thanks.

  reply	other threads:[~2022-08-27 16:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-27  3:02 [PATCH v2 0/3] New Discord bot and full refactor scripts Muhammad Rizki
2022-08-27  3:02 ` [PATCH v2 1/3] Move the Telegram bot source code Muhammad Rizki
2022-08-27  3:02 ` [PATCH v2 2/3] First release Discord bot Muhammad Rizki
2022-09-03  0:29   ` Ammar Faizi
2022-08-27  3:02 ` [PATCH v2 3/3] Full refactor bot scripts Muhammad Rizki
2022-08-27 10:40 ` [PATCH v2 0/3] New Discord bot and full refactor scripts Ammar Faizi
2022-08-27 16:00   ` Muhammad Rizki [this message]
2022-08-29  3:39     ` Ammar Faizi
2022-09-03  0:42     ` Ammar Faizi
2022-09-03  0:45       ` Ammar Faizi
2022-09-03  1:01         ` Muhammad Rizki
2022-09-03  9:44           ` Ammar Faizi
2022-09-03  9:46             ` Ammar Faizi
2022-09-03 10:05             ` Muhammad Rizki
2022-09-03 10:32               ` Ammar Faizi
2022-09-03 10:34                 ` Ammar Faizi
2022-09-03 10:40                   ` Ammar Faizi
2022-09-03 10:58                     ` Muhammad Rizki
2022-09-03 10:52                   ` Muhammad Rizki
2022-09-03 10:43                 ` Muhammad Rizki
2022-09-03  0:56       ` Muhammad Rizki
2022-09-03  1:00         ` Ammar Faizi
2022-09-03  0:29 ` Ammar Faizi
2022-09-03  1:28 ` Ammar Faizi
2022-09-03  3:09   ` Muhammad Rizki
2022-09-03  9:56   ` Alviro Iskandar Setiawan
2022-09-03  9:58     ` Ammar Faizi
2022-09-03 10:06       ` Alviro Iskandar Setiawan
2022-09-03 10:12         ` Ammar Faizi
2022-09-03 10:43           ` Alviro Iskandar Setiawan
2022-09-03 11:09             ` Ammar Faizi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox