This is looking good, but a couple comments first:

• We're going to do the js server in server.js updates comments variable after get request to "comments.json" #17
• As you can see in the discussion there, we actually also want to make sure we re-read the file when POSTing, otherwise we could lose data while writing to disk.

So if you could make the right changes in the other implementations, that would be awesome!

I'll figure out how to reset my fork and get it submitted. Should I submit
the python and ruby files as one pull request or two?

Thanks,
Darren

On Mon Feb 02 2015 at 12:45:11 PM Paul O’Shannessy notifications@github.com
wrote:

This is looking good, but a couple comments first:

• We're going to do the js server in server.js updates comments variable after get request to "comments.json" #17
  server.js updates comments variable after get request to "comments.json" #17
• As you can see in the discussion there, we actually also want to
  make sure we re-read the file when POSTing, otherwise we could lose
  data while writing to disk.

So if you could make the right changes in the other implementations, that
would be awesome!

—
Reply to this email directly or view it on GitHub
#20 (comment).

Keeping it in this PR is fine.

Also, it looks like our bot wasn't set up right for this repo. Can you sign the CLA - https://code.facebook.com/cla? We'll need that before we can merge the changes.

Ah, picked this up with a combo of other changes tonight. But if we missed anything or you have other suggestions, let me know!

Thanks - got hung up trying to figure out git rebasing. Maybe next time.