ruby - Rails devise user architecture for social network -


im creating social network app rails , devise user authentication gem. have more 1 type of user , dont know how proceed.

my usertype1 , usertype2 have little in common dont know if sti way go.

should have both user types inherit devise user or should create each 1 devise.

last, should create social fields in user type or create profile model type of info

any appreciated

the first type of user customer has basic fields first name, last name, profile photo, , home address.

the second type of user agent has many other fields, first name, last name, profile photo, business informations(address, phone ..etc), specialty, category, title, website, social accts, , other fields.

the difference in functionality between 2 great, agent user act friend, tag, create events, listings etc... , customer create lsitings, contact agents, , search listings.

i rethink idea of having 2 models user types. instead, consider having slim user model , use associations (like user.profile, user.details) hold attributes. save lot of headaches preventing addressing different "user" models in devise code.


Comments

Popular posts from this blog

Delphi XE2 Indy10 udp client-server interchange using SendBuffer-ReceiveBuffer -

Qt ActiveX WMI QAxBase::dynamicCallHelper: ItemIndex(int): No such property in -

Enable autocomplete or intellisense in Atom editor for PHP -