[jasoncodes]

Unfortunately GitHub's OAuth API doesn't let us get read access to private repos without also having write access. http://developer.github.com/v3/oauth/#scopes

We would like to make write access optional later on for users who only need to deploy public repos. I'm not sure if this is actually possible or not though. It'd be great if GitHub added more authentication options.

[freerobby]

It would be useful if you had a demo or explanation of the process before requiring Oauth. The bottleneck for me is that I don't want to Oauth via Github until I know I'm going to use your product.

[twe4ked]

Yeah, we will try to get a screen cast out soon. We didn't spend to much on the marketing side of things.

[zrail]

Agreed. I can't tell from a single miniature screenshot what your product actually does.

[borski]

Could you elaborate here about your product and what it does, in detail? That would get me to sign up. :)

[twe4ked]

At the moment Koi Deploy allows you to add GitHub repositories as 'Projects' and set up multiple Heroku instances for that project. You can then schedule or instantly deploy your application from any branch/git ref with the click of a button.

The deploy process:

* Turns on maintenance mode

* Does a backup of your database using pgbackups (support for others later)

* Pushes your code to Heroku

* Runs migrations

* Turns off maintenance mode

* Sends you an email to notify you of success or failure

In the future we would like to add support for a bunch more features including provisioning new Heroku instances and showing you the commits that will be pushed. We want to become the place to do managed deployment to Heroku. It's to easy to forget to do a backup or forget to turn on maintenance mode when deploying manually. At our day job, we have 10s of Heroku instances and being able to see the status of multiple deploys at once is going to be a major win for us.

[borski]

Interesting. We deploy to Heroku multiple times every day and use the 'preboot' heroku labs option - turning on maintenance mode every time we deploy would be bad, since we deploy so often.

It would be nice to automatically run any new migrations or seeds though. Right now we have a crazy set of shell scripts that work, but could almost certainly be better. ;)

[twe4ked]

We're planning on having options for things like maintenance mode on a per deploy basis with project defaults. We're also looking into supporting the Heroku preboot labs feature.