I suggest to use the builtin authentication solution, just take a look on padrino-admin, you can use Padrino::Authentication without admin inside any app you need It's pretty simple, role/path based padrinorb.com/api/Padrino/Admin/AccessCo....
I suggest to use the builtin authentication solution, just take a look on padrino-admin, you can use Padrino::Authentication without admin inside any app you need. It's pretty simple, role/path based. padrinorb.com/api/Padrino/Admin/AccessCo....
Using padrino-admin forces you to work with the account model generated by admin (or workaround it); which may not be optimal for the OP. More importantly, there are open security issues (github. Com/padrino/padrino-framework/issues/384) anyone who deploys padrino-admin in production should be aware of.
– pithyless Oct 28 at 14:30.
A standalone authentication solution for Padrino has been discussed, but has not been resolved yet. In the mean time, one popular suggestion is to use padrino-warden. Disclaimer: I'm in a similar situation as OP and have no experience in running personal-warden in production, yet.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.