Should I implement the
destroy actions on a controller whose corresponding model uses Devise's
In other words, should I keep the CRUD interface even though Devise manages the registration process for me?
If you want to manage your
Users (or whatever your Devise model is called) via a CRUD interface, you'll need to have those actions available. Unless I'm mistaken, if you manage your
Users with a CRUD setup, you'll need to remove the
:registerable from the model.
If you want need/want a CRUD interface for your
Users, you can remove the CRUD actions (Devise will work fine without a CRUD interface, or CRUD actions in your controller).