Setup and Maintainence

[Timmooo]

Probably not super important but I would count this as key functionality.

Initial setup

• have an initial setup script, this checks that everything is done properly, checks for presence of complete config file (could prompt to fill basic data?), and loads initial modules, asks for details for the bd and creates the initial database if necessary etc
• this could be a bash ./configure script that simply runs everything for you

Starting and stopping the bot

• have a script to start the bot, this would enable it to launch the bot (keep the main rb file elsewhere?) and also create a pid file to enable cronlike jobs
• this script could have a cron option that checks if the pid is current and relaunches if not
• could also have a stop option that cat's the pid and kills it (easier than looking it up), and then clears the pid file (saves having to do this manually too)

Config file

• What should be stored in this? Key modifiable data yes
• Am not certain plugin specific data should go here as this will quickly become an overly large file.
• each plug-in / module should have it's own reference file if needed imo
• config file should stick to the basics: commandprefix, start / stop messages, and probably plugin loading info
• if used would also add in super users / authentication options (in case bot owner is not server admin), and database options
• perhaps parts of this could be modified in initial configuration to save manual configuration? overthinking this? probably.

Will add more to this issue if i think of anything.

[MadnessExpress]

If you have time can you work on this? The main bot file already loads the modules so that won't be needed. It should be able to start the bot in screen as the user running the script without using sudo, there is an example of that in the update.sh script I made. We could roll the update script into it. It should be able to take either a start argument which would run BruhBot.rb or an update argument which runs the code I already made. The bot should only be shutdown from discord using the !shutdown command so that it exits cleanly. The config is already attached to BruhBot.rb, so the start/update script would not need to interact with that.

[MadnessExpress]

Ideally this script would be started with crontab upon reboot, but would also function manually as well.

[Timmooo]

Okay, so ./bruhbot {options}:

• help: returns basic help output - i.e. syntax / options
• start: starts the bot (fails if already running)
• restart: stops and then starts the bot
• stop: send a shutdown signal to the bot (can this be done with a clean call to the shutdown ruby code, or would it have to be killing it? if so not ideal unless it is non-responsive, but could be nice to include in case of incorrect setup)
• update: pulls from git and restarts the bot
• status: checks for pid and returns current status

Probably won't bother with an initial setup one just yet, but could be easy enough to do to create the config file initially by telling users exactly what they need through some q&a stuff?

Note: I am very verbose sometimes.

[Timmooo]

Oh and add in a cron option. This checks if the bot is running, and if not, starts it.

[MadnessExpress]

Stop would have to kill the bot, same with restart. I have a shutdown command built in and I need to make a restart one. Even the stop command will cancel any other running commands so it isn't perfectly clean, but it does cause the bot to go offline immediately, whereas killing it causes it to linger for a bit. But stop and restart might be good to have anyways. On Jul 3, 2016 7:48 AM, "Tim Riddell" notifications@github.com wrote:

Oh and add in a cron option. This checks if the bot is running, and if not, starts it.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/FormalHellhound/BruhBot/issues/25#issuecomment-230149320, or mute the thread https://github.com/notifications/unsubscribe/ALbH3eSBRd4dFFALne2a_G8ktvNWKFhDks5qR6FygaJpZM4IoXD0 .