Skip to content
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

"Current Action" endpoint #7

Open
3 of 7 tasks
austinpray opened this issue May 26, 2015 · 2 comments
Open
3 of 7 tasks

"Current Action" endpoint #7

austinpray opened this issue May 26, 2015 · 2 comments
Milestone

Comments

@austinpray
Copy link
Member

@ridhoq and I are going to commit to getting the current action endpoint squared away tomorrow evening. Anybody is free to attend, just coordinate we @ridhoq and I. We don't have a definite time but will commit to one if it makes it easier for you to attend.

For the "current action" endpoint we are going to :

  • Determine what the JSON response looks like. This is what the bot will be consuming.
  • Document API usage in the README
  • Scaffold repo Start Fresh #5
  • Scaffolding includes setting up Redis
  • Write failing tests for the response
  • Write code to satisfy test
  • Ship to heroku Hosting #4
@ridhoq
Copy link
Contributor

ridhoq commented May 26, 2015

Did we decide if we were storing the current action in memory or in Redis? If Redis (which is probably the best option) we will have to configure that as well.

@austinpray
Copy link
Member Author

It needs to be in Redis so we can horizontally scale

@ridhoq ridhoq mentioned this issue May 26, 2015
@austinpray austinpray added this to the 1.0.0 milestone Jun 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants