zehtomer

4 ms·

1. 1.▲
   by zehtomer 7y ago

   We're looking into improving the disconnect/reconnect flow! Hopefully will have some progress on that soon.
2. 2.▲
   by zehtomer 7y ago

   We don't, this is using a private API.
3. 3.▲
   by zehtomer 7y ago

   On the listen side, you can run `stripe listen --print-json` which will output the entire object. You can also resend events by doing `stripe events resend <event_id>`. We'll see about documenting both better!
4. 4.▲
   by zehtomer 7y ago

   Hi all! I'm one of the folks who's been working on this for the past few months. I'm happy to answer some questions about the CLI or how it was built (using Go and websockets for pushing data). If you have any ideas or feedba
5. 5.▲
   by zehtomer 9y ago

   I'm going to try to do some follow up posts in the next few weeks around building this and I'll work to incorporate some of that in there. It was definitely interesting getting this going.
6. 6.▲
   by zehtomer 9y ago

   As bpicolo said, lots of Python. The API itself is a Python service running on Pyramid/uWSGI. Our focus on services internally means that the API delegates our REST requests to other internal services when resolving the data. As far as
7. 7.▲
   by zehtomer 9y ago

   Hey! I fixed reviews so the example should work now and pushed out a change to the developer site to fix a broken example I noticed.