I had to built some oAuth with Phalcon. Then I share a simplified version of what i have done (i just put all the code in protected method of the controller, feel free to update the structure). You will have to modify a few things. Just look for "specific to your application" comments in the code.
https://gist.github.com/SneakyBobito/6909234

It is based on PHPoAuthLib : https://github.com/Lusitanian/PHPoAuthLib then you have to add it to you autoloader
Then you may add any service available in the lib (but i only tested with google and github).
When you want to add a service : you have to generate an api key/secret key on the specific service and then put them into your config as with the examples of google and GitHub. Finaly add the action that has the same name of the oAuth service (github : GitHubAction google : GoogleAction)

I just noticed that your work is a bit in the same direction that my post. By the way if you want to do some oAuth, let me advice you to use a base oAuth class, it would make things more easy to extend !

This is phalcon unrelated, but i am sure that will help many of you. A documentation generator for API based php applications. All that i found on google are framework dependent solutions. Check out: https://github.com/calinrada/php-apidoc . Feel free to contribute by making PR's

Business logic contained within "Action" classes and not in controllers

PHPUnit integration with shared/overloaded DI services; New DI container generated for each test.

Currently uses service location, but its very easy to use constructor service injection

I'm still in the process of writing out formal documentation explaining everything but feel free to check it out. I'd appreciate any feedback/pull requests and the like. Also let me know if you have any trouble getting it installed and running, there's a quickstart guide in the repo.

What I'd love for the Phalcon community to have is multiple examples of a solid application architecture for others to use as inspiration or a starting point in their app development. This is my attempt at one after about 2 months of working with Phalcon. It naturally applies some of my own design principals (like Actions classes for performing business logic, lightweight bootstrap files, service locator vs. constructor DI, etc) but I'm 100% open to suggestions.

Here is a repository to load ide stubs in your project though composer : https://github.com/gsouf/phalcon-stubs
It's what i use to do when working with phalcon, you dont have to configure your ide to load some stubs. Stubs comes to you when you composer install ;)

Remember to put it in the require-dev section of composer to avoid to download it uselessly in prod.

I just managed to create an RPM package for Phalcon to be used in Amazon Linux. It's the first time I try to create a package but it seems it's working fine! If someone more experienced have suggestions for improvements, please share with use.

For those wanting to test it on AWS EC2 running Amazon Linux, please check the repository: