svn - How to restrict access to a staging environment -


our workflow has developers working on locally hosted copies of our web application svn source control. have post-commit hooks deploy each new revision designated staging environment running on subdomain.

my question is, best way restrict access these staging sites can't stumbled across or god forbid indexed search engines?

we'd avoid ip based, have remote developers working unavoidably dynamic ips.

i have initial ideas such simple form can hit login credentials either a) give access cookie that's checked when running in staging environment, or b) register current ip address allowed determinate length of time.

if can share ideas, previous experience or best practice appreciated

if you're using apache simple , basic protection should .htaccess file. if doesn't satisfy needs security, should think implementing own security mechanism.

the best solution put staging server in closed network , allow access via secure vpn.


Comments

Popular posts from this blog

c++ - Convert big endian to little endian when reading from a binary file -

C#: Application without a window or taskbar item (background app) that can still use Console.WriteLine() -

unicode - Are email addresses allowed to contain non-alphanumeric characters? -