Rails方式-命名空间 [英] The Rails Way - Namespaces

问题描述

我对如何做"The Rails Way"有疑问.对于具有面向公众的界面和管理界面的应用程序，Rails社区对如何做到这一点的普遍共识是什么?

I have a question about how to do something "The Rails Way". With an application that has a public facing side and an admin interface what is the general consensus in the Rails community on how to do it?

命名空间，子域还是完全放弃?

Namespaces, subdomains or forego them altogether?

推荐答案

对于管理界面，实际上并没有真正的推道"-您可以在许多应用程序中找到每种可能的解决方案. DHH暗示他更喜欢名称空间(具有HTTP Basic身份验证)，但这仅是一个简单的含义，而不是正式的Rails意见之一.

There's no real "Rails way" for admin interfaces, actually - you can find every possible solution in a number of applications. DHH has implied that he prefers namespaces (with HTTP Basic authentication), but that has remained a simple implication and not one of the official Rails Opinions.

也就是说，最近我发现该方法取得了很好的成功(命名空间+ HTTP Basic).看起来像这样:

That said, I've found good success with that approach lately (namespacing + HTTP Basic). It looks like this:

routes.rb:

routes.rb:

map.namespace :admin do |admin|
  admin.resources :users
  admin.resources :posts
end

admin/users_controller.rb:

admin/users_controller.rb:

class Admin::UsersController < ApplicationController
  before_filter :admin_required
  # ...
end

application.rb

application.rb

class ApplicationController < ActionController::Base
  # ...

  protected
  def admin_required
    authenticate_or_request_with_http_basic do |user_name, password|
      user_name == 'admin' && password == 's3cr3t'
    end if RAILS_ENV == 'production' || params[:admin_http]
  end
end

authenticate_or_request_with_http_basic上的条件触发在生产模式下或将?admin_http=true附加到任何URL时触发HTTP Basic身份验证，因此您可以在功能测试中对其进行测试，并在浏览开发站点时手动更新URL.

The conditional on authenticate_or_request_with_http_basic triggers the HTTP Basic auth in production mode or when you append ?admin_http=true to any URL, so you can test it in your functional tests and by manually updating the URL as you browse your development site.

这篇关于Rails方式-命名空间的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！