From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} Development framework with access restriction?
Date: Sun, 2 Oct 2011 23:41:24 +0100 [thread overview]
Message-ID: <201110022350.06088.michaelkintzios@gmail.com> (raw)
In-Reply-To: <CAN0CFw1yQ9DD7T3+rZBgrMzsUjG1XBh_Kkd1VjJLM4G3TyyhOw@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1279 bytes --]
On Sunday 02 Oct 2011 00:27:23 Grant wrote:
> >>> I'm not sure if you are overcomplicating this by trying to use Unix
> >>> permission. Have you instead considered webdav? You can restrict this
> >>> to particular (apache) users/groups, directories, files. It also uses
> >>> lockfiles so with two users editing a file simultaneously will cause a
> >>> warning when you try to save it.
> >>
> >> How does webdav relate to something like subversion? Do they
> >> compliment each other or are they substitutes?
> >>
> >> - Grant
> >
> > WebDAV has no version control. It is just an extension to HTTP for
> > distributed authoring. It supports locking files and methods which make
> > it more filesystem-like. AFAIK SVN uses WebDAV for its HTTP transfer
> > protocol.
>
> Got it. It sounds like I could use WebDAV in conjunction with
> subversion or git. I'll look into that.
The reason I mentioned webdav(s) earlier was because you can have granular
control of what each user can access. You need specify only what
directory/file you want them to be able to access and they shouldn't have
access to anything else.
Also, you don't need to give them shell access - which I find
(psychologically) more reassuring. ;-)
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-10-02 22: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 [this message]
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
-- 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=201110022350.06088.michaelkintzios@gmail.com \
--to=michaelkintzios@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