jankaritech / hubot Goto Github PK

Create Makefile with support for

• Building and installing to system (be it either /usr/bin or ~/.local/bin )
• Support to setup systemd service as mentioned in #10

Currently, the bot only notifies for meeting reminders.
Add support for responding to commands like hubot such as

• @ScrumMasters
• @whos-on-leave
  and more ...

The library https://github.com/RocketChat/Rocket.Chat.Go.SDK supports real-time message listening and more.

As an administrator
I want to have all log-files in /var/log/....
So that my system is not cluttered with log-files everywhere

currently the config file must be placed in the folder where the bin is, but if we start it by systemd or similar it will be called using the full path /var/www/rocket.chat/teamup/teamup-rocketchat-bot and the config file cannot be found

Tasks

• GOOS and GOARCH combinations can put in a separate md file
• Update Systemd service file with relevant details
• More details if necessary

Currently, the bot crashes showing message

TEAMUP-ROCKETCHAT-BOT 2023/01/11 09:05:30 Looking for configuration at "/var/www/rocket.chat/teamup/config.yml". Setting directory specified by configuration for log output.
TEAMUP-ROCKETCHAT-BOT 2023/01/11 09:05:30 open /tmp/teamup-rocket-chat.log: permission denied
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x529229]

goroutine 1 [running]:
log.(*Logger).Output(0x0, 0x1?, {0xc000128200, 0x33})
	/usr/local/go/src/log/log.go:179 +0x89
log.(*Logger).Fatal(0xc0001281c0?, {0xc000125f00?, 0x441?, 0x7c41f0?})
	/usr/local/go/src/log/log.go:231 +0x45
main.main()
	/tmp/hubot/teamup-rocketchat-bot/main.go:307 +0x158

TODO:

• Replace the above crash message with it's cause
  E.g. The bot has crashed due to following error: error_message

As an admin
I want to remind users about different calendars

As an admin
I want to be able to have different templates for different calendars

• in Readme
• in module name

This should be done in multiple PRs

• when starting the bot with invalid configuration it just silently fails not telling the user what went wrong
• giving wrong Rocket.Chat details just logs Unauthorized in the log file. This is not enough to debug the issue