Building an API in 60 seconds, without any server setup
31–40 of 72 posts
Re: Building an API in 60 seconds, without any server setup
#32Anyone know if this would work with Mailguns cool email signature parsing library? http://blog.mailgun.com/open-sourcing-our-email-signature-pa... as in, easily build an api for it?
Talon is now supported. Feel free to make all the cool mailgun api's you want!
Re: Building an API in 60 seconds, without any server setup
#33Re: Building an API in 60 seconds, without any server setup
#34It would be sort of cool to implement cryptanalysis tools as APIs using this. Like "submit your data and we'll tell you what it might be". I built some tools in python the first time I was working on the Matasano crypto challenges but Go is a better choice. Would be nice if it was supported.
Re: Building an API in 60 seconds, without any server setup
#35Re: Building an API in 60 seconds, without any server setup
#36Re: Building an API in 60 seconds, without any server setup
#37Earlier quoted context omitted.
Talon is now supported. Feel free to make all the cool mailgun api's you want!
Maybe the paid version of your site could support virtualenvs.
Re: Building an API in 60 seconds, without any server setup
#38Earlier quoted context omitted.
Maybe the paid version of your site could support virtualenvs.
Super curious, what would you use the virtualenv for? Each script run happens in its own container. Is it to import your own libraries that we don't support yet?
Yeah. I don't have a use for this as-yet but I can see organisations wanting to import their preconfigured envs in.
Re: Building an API in 60 seconds, without any server setup
#39I'm not sure I understand what this is. Free hosted PaaS for single files, essentially? I know nothing about where the code is running? Is it performant? Is it reliable? How are they covering server costs / at what point would I be asked to pay, and how much?
Great questions. Let me answer them one at a time!
Where is the code running? Every script run happens in its own sandbox on our machines. We use docker, it's awesome. People are asking for dedicated machines specifically for their company, and others are asking to hook into their own machines. Once we figure out how people/companies want to use the site, we'll put up some options for where code will be run. I'm totally open to feedback and would love to hear what you think.
I'm measuring costs right now. But I'm seeing that when we get a fair pricing model up - if you could hit these api's only when you need them, rather than have a dedicated server for them, you'd save a money. A really different way of looking at PaaS + Apis... and I'm super excited about it. Right now, I'm just trying to collect as much awesome feedback as possible for use cases, and then we'll have a better idea for how users would want to be charged. Right now, people are asking for a simple request-based model. Would love your thoughts on this as well.
Thanks again for the questions. You're awesome.
paul@blockspring.com 312.834.7265