public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} Development framework with access restriction?
Date: Fri, 30 Sep 2011 16:50:15 -0700	[thread overview]
Message-ID: <CAN0CFw1T_PO12ZhrSQi7n7rYtzYSJiBj6-SKSEWXxRG32+G8gQ@mail.gmail.com> (raw)
In-Reply-To: <20110929084321.5b2e60ed@toxic.dbnet>

>>> svn can restrict access to directories
>>>
>>> http://stackoverflow.com/questions/2288810/how-to-restrict-svn-repository-user-account-to-one-directory
>>
>>That would be perfect if it allowed access per file instead of per
>>directory.  I thought about re-arranging the layout to accommodate
>>that limitation but I don't think it makes sense.

After more research, I think subversion's path-based authorization
*does* in fact work with files and not just folders.  This might be
the solution I've been looking for.  I will report back on this after
more research.

> do you not want him to change it or do you not want him to be able to
> read your code?

I do not want him to be able to read or write any files except for the
specific file or files I want him to work on.  This becomes
complicated because he needs to be able to test his changes in a
working version of the system as he goes.  The files to be worked on
contain server-side website code all of which I don't want to give
away to the dev.

- Grant



  reply	other threads:[~2011-09-30 23:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-26 20:01 [gentoo-user] {OT} Development framework with access restriction? Grant
2011-09-26 21:37 ` Michael Orlitzky
2011-09-27 11:27   ` Mick
2011-09-29  1:18   ` Grant
2011-09-29  2:23     ` Grant
2011-09-29  6:57       ` Jonas de Buhr
2011-09-29  7:32         ` Mick
2011-09-30 23:53           ` Grant
2011-10-01 11:07             ` Florian Philipp
2011-10-01 23:27               ` Grant
2011-10-02 22:41                 ` Mick
2011-10-03 22:01                   ` Grant
2011-10-03 22:12                     ` Michael Mol
2011-09-29  8:13       ` Neil Bothwick
2011-09-29 17:23         ` Michael Orlitzky
2011-09-30 23:59           ` Grant
2011-10-01  0:23             ` Michael Orlitzky
2011-10-01 23:46               ` Grant
2011-10-02 19:04                 ` Michael Orlitzky
2011-10-03 21:54                   ` Grant
2011-10-03 22:00                     ` Michael Mol
2011-10-04  4:25                     ` Michael Orlitzky
2011-09-27 12:19 ` Jonas de Buhr
2011-09-29  1:23   ` Grant
2011-09-29  6:43     ` Jonas de Buhr
2011-09-30 23:50       ` Grant [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-10-01  5:58 Pandu Poluan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAN0CFw1T_PO12ZhrSQi7n7rYtzYSJiBj6-SKSEWXxRG32+G8gQ@mail.gmail.com \
    --to=emailgrant@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox