-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor Code in Python or Golang #92
Comments
Obligatory comment about ruby |
If Ruby's your passion @stain88 - I won't get in your way. I'd be sad to give up the project entirely (I don't know any Ruby, and I don't currently have the bandwidth to learn) - but if you are on fire about it, I can re-pull the code into my repo and refactor it as and individual project....then you can go ahead a re-write it as Ruby for the community. |
nah, not to the extent of forcing you to drop the project. Playing around with a ruby bot on my own to see how that works. |
I’m going to keep it on Node just to throw a monkey wrench in this whole
thread :D
On Jul 31, 2018 at 1:13 PM, Marc Baghdadi <[email protected]> wrote:
nah, not to the extent of forcing you to drop the project. Playing around
with a ruby bot on my own to see how that works.
I'll start having a look at python, since bill is going the go route
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADtinSt_KA3KmrB7u2ivNro37SX8dPUyks5uMLpbgaJpZM4VghVl>
.
|
@angelocordon - the thought would be that we'd keep a version on Node as long as there were slash commands being added, or there was active development happening by one or more participants. Meanwhile, we'd be looking at re-writing the codebase on a different branch/in a different repo. It is small enough at this point that it (ought) to be straightforward. @stain88 - totally up to you (you could still do it in Ruby...). If you'd like to go the Python route, there is Flask or Django for the backend. We could use Redis for storing the message content - or even something like postgres. Django comes with SQLLite, as well. There are also numerous bot frameworks...but I am assuming that we'd do it from "scratch" or "scratch-ish" - although there might be something super-fun out there (it's been a while since I looked into it). Another thought/pattern would be to AWS-Lambda-ize the way @Bill is doing with buddybot. Many options.... |
Refactor the code in Python or Golang for ease of maintenance.
The text was updated successfully, but these errors were encountered: