On Mon, Mar 28, 2011 at 10:36 PM, Michael Richter <[email protected]>wrote:
> I just saw an intriguing message in the timeline. "Leaf: Merge the > sub-repo capability into trunk." I can't find anywhere in the help, the > fossil docs nor in the wiki that talks about this. How does one use this > new sub-repo capability? > Sub-repositories is nothing more than the opportunity to create single-signon for two or more separate repositories at a single website. We have an SQLite Consortium member who is using several proprietary SQLite extensions. Previously, they had a separate login for the repository of each extension. Password management was becoming an issue for them, so they requested a unified private website, with a wiki, that gives them access to all of the extensions all at once. Subrepositories provide this. Suppose the subrepos are named abc.fossil, def.fossil, and ghi.fossil. The name of the main repository is xyz.fossil. All the repositories files live in the same directory, say. Suppose the xyz.fossil repository is accessible as: https://domain/path/to/xyz. Then you create entries in the xyz.fossil SQLite database like this: INSERT INTO config(name,value) VALUES('subrepo:abc','user1:abc.fossil'); INSERT INTO config(name,value) VALUES('subrepo:def','user2:def.fossil'); INSERT INTO config(name,value) VALUES('subrepo.lmnop','user3:ghi.fossil'); Those entries activate subrepositories so that users can log once to xyz but access the other repositories using URLs like: https://domain/path/to/xyz/abc/timeline https://domain/path/to/xyz/def/timeline https://domain/path/to/xyz/lmnop/timeline The access permissions to the subrepositories are those for user1, user2, and user3, respectively. The client company has many individuals at several office locations who all need access to the subrepositories. But on the subrepos for the proprietary SQLite extensions, we only have a single login for the client as a whole. The subrepo mechanism allows the various users at the client company to each have their own username and password but still share access to the subrepos using a unified login name. We only allow the client "Reader" capabilities when accessing the subrepos. But for the main repo that contains the project wiki and other resources, the client has full "Setup" capability so that they can do whatever they want on their private repo without accidentally making undesirable changes to the subrepos. > > -- > "Perhaps people don't believe this, but throughout all of the discussions > of entering China our focus has really been what's best for the Chinese > people. It's not been about our revenue or profit or whatnot." > --Sergey Brin, demonstrating the emptiness of the "don't be evil" mantra. > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
