Rails4 + Devise + Authority + Rolifyで管理者権限付きの管理画面作成 - Qiita
掲題の件、最初はcancanを使おうと思ってたのですが開発がとまっているようでしたので、 Rails4 + Devise + Authority + Rolifyで管理者権限付きの管理画面を作成しました。 開発も活発で、使いやすかったため、今後また別の案件で使いたいと思ったのでメモに残したいと思います。 簡単な流れ こちらのサイトを参考にしました Deviseのインストールおよび設定(省略) rails generate devise:install rails generate devise User Authorityのインストール rails generate authority:install Authorityは、実際に各controllerのactionごとに、そのactionを実行できる条件を記述したりすることができます。 またUserが指定した権限をもっているかどうかをチェ
Authentication with Warden, devise-less
Authentication with Warden, devise-less For most of us, using warden means using devise. Devise served me well but it's big and there's a lot of convention that you need to abide by. Getting up & running with devise is fairly simple. Warden needs a little bit more to get started and I'm going to show you how to implement it to have a similar setup. Warden is great. But it might not be as simple to
How To: Test with Capybara
Acceptance tests for your application may require that a test user be logged in. To do this in your application you can either sign in the user using capybara by visiting the sign in url and entering valid credentials, or you can stub the logged in user. Signing in via Capybara is perhaps the most 'correct' way since we want our tests to be as close to real world conditions as possible, however if
Devise and Rails 4 « Plataformatec Blog
This week we released the first release candidate version of Devise that is fully compatible with Rails 4, and we’re bumping its version to 3.0. This version completely drops support for Rails 3.1 and Ruby 1.8.7, only keeping compatibility with both Rails 3.2 and Rails 4, running with Ruby 1.9.3 and 2.0. This rc version took some time to get ready, we’ve been running a rails4 branch for some time
Request Specs With Devise & RSpec - Rawlins
Friday, 22 March 2013 Request Specs With Devise & RSpec Working with request specs for apps secured using Devise can be tricky. I've recently been using the following approach to authenticate mock users for testing. The Problem The problem is that if you're using Devise within your application for user authentication you'll be securing down your controllers using a before filter. class InvoicesCon
認証に Devise を使っている Rails アプリの Request Specs の書き方 - present
認証に Devise を使っている Rails アプリ の Request Specs の書き方をネットで調べたら、ヒットしたのは Request Specs + Capybara の情報ばかりだった。今 Rails で作っているのは Web API だから、Capybara は要らないんだよな。Request Specs だけでいいのに。そもそも、Request Specs の資料も少ないね。 StackOverflow をはじめ、海外のフォーラムやブログで調べながらトライ&エラーを繰り返した結果、Devise を使っている Rails アプリの Request Spec は次のような書き方に行き着いた。 # coding: utf-8 require "spec_helper" describe "List" do describe "GET /lists" do before do
)
Create new page · heartcombo/devise Wiki
Attach files by dragging & dropping, selecting or pasting them. Loading Uploading your files… We don’t support that file type. Try again with a GIF, JPEG, JPG, MOV, MP4, PNG, SVG or WEBM. Attaching documents requires write permission to this repository. Try again with a GIF, JPEG, JPG, MOV, MP4, PNG, SVG or WEBM. We don’t support that file type. Try again with a GIF, JPEG, JPG, MOV, MP4, PNG, SVG
Rails Tutorials for Devise and RSpec · RailsApps
Thanks so much for this. There are so many Rails tutorials for absolute beginners, and lots of stuff that assumes expert knowledge, but not much, besides practice, to span the gap. Rick Quantz, HackerNews, 13 May 2011 I will be starting a new job here in SF, due in no small part to what I've learned here from the RailsApp Project. Joseph May, 23 Dec 2013 I would like to say thank you for such a pr
Security announcement: Devise v2.2.3, v2.1.3, v2.0.5 and v1.5.4 released « Plataformatec Blog
Hi everybody. I’d like to announce that Devise v2.2.3, v2.1.3, v2.0.5 and v1.5.4 have been released with a security patch. Upgrade immediately unless you are using PostgreSQL or SQLite3. Users of all other databases (including NoSQL ones) require immediate upgrade. Using a specially crafted request, an attacker could trick the database type conversion code to return incorrect records. For some tok
How to "soft delete" user with Devise
I currently use Devise for user registration/authentication in a Rails project. When a user wants to cancel their account, the user object is destroyed, which leaves my application in an undesired state. What is the easiest way to implement a "soft delete", i.e. only removing personal data and marking the user as deleted? I still want to keep all record associations. I assume I will have to first
ルーティング for Devise 2.1 - 黒魔法使いの弟子
DeviseといえばRailsにおける代表的な認証ライブラリです。 バージョンアップに伴いログアウト部分に修正が必要になりました。 修正前はこんなエラーが発生 # viewでdestroy_user_session_pathが使えなくなりました (ﾟДﾟ)ｺﾞﾙｧ！ <%= link_to "ログアウト", destroy_user_session_path %> # エラー The action 'sign_out' could not be found for UsersController Userにおけるサンプル from github destroy_user_sessionがあるのに使えないとかドツボに嵌りそうですね。 ひとまず以下の様な修正をすることでログアウトの問題を修正します。 カスタマイズ また、以前はdevise_for :resources do ... endで色
Active Admin | The administration framework for Ruby on Rails
The administration framework for business critical Ruby on Rails applications. Active Admin is a Ruby on Rails plugin for generating administration style interfaces. It abstracts common business application patterns to make it simple for developers to implement beautiful and elegant interfaces with very little effort. A beautiful interface designed for real people. Global Navigation Customizable g
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
)
How To: Test controllers with Rails 3 and 4 (and RSpec)
Integration Testing
How To: Allow users to edit their account without providing a password
http://retrosteve.com/techbiz/2014/1/21/using-omniauth-facebook-profile-image-with-carrierwave-in-rails-4
Devise gem skip confirmation and skip confirmation via email both at once
How To: Stub authentication in controller specs
Capybara, Devise, CanCan and RSpec integration tests: valid sign in 302 redirects to example.com
How To: Upgrade to Devise 2.0 migration schema style