On Tue, Jun 12, 2012 at 9:15 PM, Mike Meyer <[email protected]> wrote: > We're not talking about a repository that's being served by an HTTP > server, but about the repository that's on his machine. > >> However... once a developer clones the repo, if he has it on a public >> filesystem then all bets are off. > > Exactly. He wants it on a file system that he's where he's using ACLs > to control access to the contents of the file system, and fossil is > apparently refusing to work unless he opens access to those files up > to everyone. That's not acceptable to him.
The Fossil repository should only need to be accessable to the user ID under which Fossil runs. If he is using the Fossil command line, then it runs under his user ID, so it would have access to a repository he owned. Should be the same for using "fossil ui". If he wants/needs to run "fossil server" on his PC, then Fossil should run as a different user ID with a repository owned by the same user ID - or at least the repository has permissions allowing the "Fossil user ID" read/write access. For him to access that same repository with the Fossile command line, the "orthodox" way would be to have the command line treat the Fossil server as if it was on another PC and access it the same as accessing any "remote" repository. If he really wants to directly access the same resposity, the repository would have to have permissions granting both him and the "Fossil user ID" read/write access. While I suppose there could be a bug in Fossil, in my own use of Fossil, repositories I own are only accessable to me, therefore only accessable to Fossil running under my user ID. Other users' repositories are likewise only accessable to them. To share changes, we each have a "fossil server" running under our own IDs that respond to push/pull/sync requests. While I don't know, I'd be surprized if Mercurial had any interface to ACLs, Windows, Linux, Posix or other. For what it is worth, as best I recall, last time I used git, it did not. Like most other apps, including Fossil, it depends on the OS to "decide" whether it has access to any given file. Ultimately, without knowing exactly what your boss was trying to do, it is unlikely to be possible to demonstrate Fossil working in a given scenario. I suppose he could be expecting Fossil to somehow use Windows ACLs to control access to artifacts stored in Fossil's database, but since Fossil's databse is contained in a single file, that is not practical and probably not even possible. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
