That's a great question! None that I know of, but I could put together some
screenshots.
On Sat, Dec 15, 2012 at 4:12 PM, Jakov Sosic jso...@srce.hr wrote:
On 12/11/2012 12:33 AM, Aaron Stone wrote:
Update: thanks to help from GitHub users @igreg and @astratto, Puppet
Dashboard Rails 3 is
On 12/11/2012 12:33 AM, Aaron Stone wrote:
Update: thanks to help from GitHub users @igreg and @astratto, Puppet
Dashboard Rails 3 is now fully compatible with Ruby 1.9! The rails3 and
rails3-aaa branches are up to date as of Dashboard version 1.2.15 plus
the work on those branches.
I'm down to
Update: thanks to help from GitHub users @igreg and @astratto, Puppet
Dashboard Rails 3 is now fully compatible with Ruby 1.9! The rails3 and
rails3-aaa branches are up to date as of Dashboard version 1.2.15 plus the
work on those branches.
I'm down to just 3 test failures, and actively working
Awesome! I had that thought myself :)
On Tuesday, November 20, 2012 11:10:38 AM UTC-8, Aaron Stone wrote:
I've added Devise and OmniAuth, starting with configs for Google OAuth2
(compatible with and can be restricted to apps-for-your-domain) on this
branch:
I've added Devise and OmniAuth, starting with configs for Google OAuth2
(compatible with and can be restricted to apps-for-your-domain) on this
branch:
https://github.com/sodabrew/puppet-dashboard/tree/rails3-aaa
Next week I will tie logins to who-changed-what-and-when accounting,
followed by
