pksunkara / alpaca

Given a web API, Generate client libraries in node, php, python, ruby

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

A mechanism to deploy to a package registry

v9n opened this issue · comments

Speaking of packagist and composer,
I found that it's easier to work on same directory with 2 branches:

  • master: for php source itself which is generated from alpace
  • alpace: hold JSON configuration

I then use a custom makefile to generate the API, copy to a temporary folder, the checkout to master branch, copy file back and commit.

I experiment with it for a bit https://github.com/kureikain/bandwidth-php (check out master and alpaca branch)

Though I feel it's tricky. Do you have any idea/method so I can work on same directory but maintain the API JSON file and the generate file at same time but keep them separate so when I published to registry, the API JSON file won't leak into PHP source.

Thanks for asking a good question. I would like to think on this a bit.