2,411
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 7:
Line 7: + + + + + + + + + + + + + + + + +
Added signature
--[[User:Judgej|Judgej]] 10:59, 21 October 2008 (UTC)
--[[User:Judgej|Judgej]] 10:59, 21 October 2008 (UTC)
I think it would be useful to separate the i-bay namespace and the subversion namespace. For example, if the repositories were under http://{server-name}/svn/{repository-name} then they would not limit the i-bay names and vice-versa. There may be issues with permissions (maybe the same name cannot be used as an SVN repo and and i-bay?)
I think it would be useful to separate the i-bay namespace and the subversion namespace. For example, if the repositories were under http://{server-name}/svn/{repository-name} then they would not limit the i-bay names and vice-versa. There may be issues with permissions (maybe the same name cannot be used as an SVN repo and and i-bay?)
It is not just i-bay names - it is folders too. If I create an SVN repo called 'test' and create a folder called 'test' in the primary i-bay html folder, then a browser pointed to http://server/test will hook up to the i-bay folder rather than the SVN web view. I'm not sure if this would be considered a bug?
It would also be nice - and probably only possible if the repos were stored in a true i-bay - to be able to point a sub-domain at the SVN repose, e.g. http://svn.mydomain.com/repo-name That would be another way to keep the namespaces apart.
:Please a raise bugs in the bugtracker if you like to make suggestions on changes, the wiki is not the proper tool for that. <small>— [[User:Cactus|Cactus]] ([[User talk:Cactus|talk]] | [[Special:Contributions/Cactus|contribs]]) </small> 15:51, 31 October 2008 (UTC)
== Group Permissions Problem ==
--[[User:Judgej|Judgej]] 13:09, 21 October 2008 (UTC)
Something else I think is an issue here: setting group permissions. The i-bays include the groups 'Everyone' and 'Admin' when setting their permissions. There are no such groups in the subversion control panel. How, for example, would you set up a repository that allows read-only access to 'Everyone' but write access only to specific groups (requiring usernames and passwords for user in that group).
Playing around with the permissions at the monent, it seems to be a very blunt instrument - you can either access it or not, and I suspect it could be because 'Everyone' is automatically given read-only access to repository once it is opened to the WAN. I'm not sure this is a sensible approach. As a user of a repository, I may want to access it from both inside the network and outside, but I may not want anybody who has not given a valid login to be able to view the contents of a repository.
Of course, it maybe that I just haven't found the documentation yet, and so am completely misunderstanding the way this contributino works. If there is any documentation, I would love to see it, but I haven't located it yet.
:Please a raise bugs in the bugtracker if you like to make suggestions on changes, the wiki is not the proper tool for that. <small>— [[User:Cactus|Cactus]] ([[User talk:Cactus|talk]] | [[Special:Contributions/Cactus|contribs]]) </small> 15:51, 31 October 2008 (UTC)
