Hot off the gemcutter: Lockdown version 1.5.0
First off, you didn’t miss anything, version 1.4.0 wasn’t actually released. Just before pushing the gem to gemcutter I decided to make an improvement to the set_user_group logic. I felt the need to make it a bit smarter and let you know if you were assigning a public or protected user group to a custom user group.
So here’s what’s in this release:
1) Delayed the parsing of init.rb to the first request. I had a report of Glassfish timing out on startup and other issues when running running db:migrate with some plugins.
2) Improved set_user_group method logic to detect reuse of public or protected permission.
I know there are a couple of other issues on the lighthouse account and I will get to them when I can.
thanks,
andy
Comments
Server Restart and Lockdown
I’ve been using lockdown for a while, but I still don’t understand whether to restart my server or not for these 2 cases :
- when I update the init.rb, do I have to restart ?
- when I add a new action in one of my controller, for example the ‘user’ controller, but I don’t update the init.rb because I already put
set_permission(:admin_articles
with_controller(:admin__articl
and assigned it to one of my user_group, do I have to restart ?
Up until now I’ve always restarted the server for those 2 cases, but I think it’s quite inconvenient. Perhaps some insight about this matter ?.
thx for your good work.