Menu
▾
▴
#4 Basic security
ReviewMonk would be more useful to me if it had some sort of basic security. Just a cheesy login/password would be great. Or even a single password (and no login name).
My use case: I'm sitting in a coffee shop, and want to have somebody else take a look at something. I'm on a public network. I don't want to expose my code to everybody here.
I know I could set up Apache in front of it, or figure out VPNs, or something like that. I've set up security on Apache a couple times, and I really don't want to ever do it again.
(I hope this doesn't go against the purpose of ReviewMonk too much.)
Logged In: NO
This is basically the one thing left that I want/need, so I'm taking a whack at it... --Ken
Logged In: YES
user_id=1776870
Originator: NO
In general, in this case I'd usually set up some basic apache auth (with .htaccess and htpaswd) and poke a hole through my firewall to let my friend in. But, since I usually run ReviewMonk on mongrel, I'm not sure if there's any simple auth built in for mongrel.
Looking at the Rails 2.0 Preview, there's a section on "Action Pack: HTTP Loving"...
http://weblog.rubyonrails.org/2007/9/30/rails-2-0-0-preview-release
It looks like there is an easy way to integrate simple HTTP auth in your rails app now. When I upgrade to Rails 2.0 (which will likely be once it's stable), I'll look at incorporating this into a config file and making it an optional setting for ReviewMonk users.