rear - Admin interface for the Espresso framework. Demo at http://rear.rbho.me/ .
Wanderlust - Some notes on effective use of Vagrant after a couple of years of use.
Nitrous.io - The former action.io web development platform, now with a new name and more funding.
Introducing TowTruck: A Collaboration Service for Every Website - Things like chat, co-browsing, and co-authoring as a service from Mozilla.
Security Incident Update …
- till's blog: Wanderlust
CHEF-3658 - Admin clients should not be able to de-admin the last admin user
CHEF-3662 - knife client reregister fails against Chef 11 Server
CHEF-3666 - Postgresql recipe is overzealously guarding configuration files behind bootstrap variable
CHEF-3673 - Bookshelf URL is not configurable
CHEF-3674 - Psql doesn't work by default, since /opt/chef-server/embedded/bin is not in the path
CHEF-3675 - Bookshelf cannot be …
- Opscode Blog: Cycle Computing Puts Chef 11 Through its Paces w/10K+ AWS Servers
- Opscode Blog: AWS OpsWorks Uses Opscode Chef as Default Automation Engine
- Engine Yard Developer Blog: Why Chef Should Manage Deploying Your Application
- till's blog: Cooking PHPUnit (and a chef-solo example on top)
- OnRails.org: Moving (again) http://onrails.org from Heroku to EC2
- Signal vs. Noise: Looking for one more person to join our operations team
- Replication Utilities for Failover and Admin
Transparency
- Many new INFORMATION SCHEMA Tables
- - INNODB METRICS
- - Meta Data Information Tables
- - Buffer Pool Information Tables
- Improved PERFORMANCE SCHEMA
- - Reduced Overhead
- - Table Access instrumentation
- - Statements instrumentation
- - Stages Instrumentation
- - Aggregations by User, Host etc
- - Network IO Instrumentation
- Improved EXPLAIN
- Optimizer Tracing
- Pennysmalls: Much faster Rails tests if you use MyISAM
- igvita.com: Schema-Free MySQL vs NoSQL
- Junior developer: Rails test data not getting rolled back
- Simple thoughts - articles: The Internal Storage Mechanism For Globalize for Rails Model Translations
- Signal vs. Noise: Keeping your slave warm
- oldmoe: 101 Reasons Why PostgreSQL is a better fit for Rails than MySQL
We've added Tackle Football as a new sport. We've also added new stats for both Tackle and Flag football. You can turn them on under the Admin -> General -> Manage Statistics page.
1. Login to New Relic as an Admin and go to the SSO configuration page. From the New Relic title bar, select (your account name) > Account Settings > Integrations > Single Sign On .
2. Use the information on the SSO Configuration page to add ‘ New Relic' as a service provider or application in your SSO federation system.
3. Upload the certificate that your Identity Provider signs with and enter the Identity Provider's remote login URL.
4. Save, …
- 4 Lines of Code: Aircraft-carrier of Authentication
- Practicing Ruby: Rails Modularity for Lazy Bastards
- Hackido: Quick Tip: Page caching and POST in Rails
- RailsLab: Yehuda Katz & Justin George Talk Rails 3
- RailsBridge News: Do One Thing for Rails 3 on January 16th and 17th
- MySQL Performance Blog: Baron Schwartz interviewed on WebPulp.tv
…that industry, would you rather imagine seeing the Emergency Room Doctor talk or the Admin who's goal it is to make monetary decisions and get funding?" Imagine the admin came and spoke from a Doctor's point of view... "Working with live bodies in the heat of the moment is hard work..." and explaining what he's seen from his nice observation room. Does he know what they feel? Does he know the pain and sweat that goes into it? The nuances that really matter when …
You can access the User app via http://appname.herokuapp.com and the Admin app via http://appname-admin.herokuapp.com.
Summary
With this system in place, you can now provide different configurations for your User and Admin apps. In my particular app, I change the number of worker processes used in my Unicorn configuration file, and I remove the Admin user verification system from the User application completely. When I start to get lots of users to this application, the User…
- CRAZ8: Many Sites in a single Heroku application
- Andrzej on Software: Rails MVC: How to deal with fat models
- Rails on Edge: Rails Forum Tutorial for Beginners (Part 1 of 3)
- Plataformatec Blog: Understanding Devise roles
- The Pug Automatic: Don't include all helpers
- Viget.com Blogs: Authentication in RailsAdmin with SimplestAuth
…include: an announcement over the dates for this year's Rails Rumble, releases of Active Admin 0.5 and Bundler 1.2, as well as Aaron Patterson looking at a difference in Object#respond_to? in the forthcoming Ruby 2.0.
Featured
The Rails Rumble is Back! Dates and Details Announced
The popular 48 hour Ruby development contest is back and will run this October 13th and 14th. Registration opens on October 1st. Learn all about it here.
Active Admin 0.5.0 Released …
- Signal vs. Noise: 37signals invests in The Starter League
- New Relic: I Don't Always Monitor My Rails Apps, But When I Do I Use New Relic
- A Fresh Cup: Double Shot #914
- Invisible Blocks: Out of Love with Active Record
- Katz Got Your Tongue?: August Tokaido Update
- Phusion Corporate Blog: Why Rails 4 Live Streaming is a big deal
ApplicationHelper is still included in all views. Admin:: UsersHelper is only included in Admin:: UsersController views. If that controller inherits from Admin:: BaseController , then Admin:: BaseHelper will be included as well.
And here's a nice (and fairly obvious) trick: you can still use regular Ruby modules to organize your methods into more than one file.
For example, I like to have a LayoutHelper that the application layout template can use: app/helpers/layout_helper.rb …
- DevInterface Blog: Rails Best Practices 3: Increase Controller's readability
- Daddy Fixes Everything: Ruby on Rails Ubuntu Server VM with VMPlayer
- Litany Against Fear: Riding Rails at the New York Times Notes
- Plataformatec Blog: Default views in Rails 3.0 with custom resolvers
- Railsmine: ActiveAdmin Tutorial
- Blog on Applicake's ideas, Ruby on Rails and Internet start-ups: Who really needs Amazon cloud?
Admin access
When you're first building an app, you'll typically write two classes: the "thing" (what your app's all about) and the user. Envisioning authentication and authorization, you prepare to add roles, since they're flexible and you're trying to add admin capabilities. Stop. Take a deep breath and resist the urge.
Instead of introducing another gem, think about the feature you're adding: admin access. For an MVP, this typically means a check …
- RubyFlow - Search for jruby: rolify 2.0 - Role management library with resource scoping