Open graybill opened 13 years ago
I don't know why I didn't think of this sooner:
http://weworkinphilly.com/people.json?column=created_at&order=desc&page=1 http://weworkinphilly.com/projects.json
etc.
Any drawbacks on this technique?
Long story short: yes, we can use this. I'd like to spruce it up into some cleaner crud calls before we do. Also would be nice to use a subdomain like api.weworkinphilly.com
If you do a pull, your dev copy will always return json to any request sent to the 'api' subdomain. We need to either specifically set up the api subdomain or do wildcard subdomains for wwip.com to finish this up. http://devcenter.heroku.com/articles/custom-domains
Example: http://api.weworkinphilly.com/projects Example: http://api.weworkinphilly.com/people/24
hmm. api.weworkinphilly.com domain doesn't work. any thoughts @graybill @alexknowshtml? not sure where this one left off.
Find a way to publish data for developers. The /changes data is probably a good place to start and already has RSS.