Home | Clover | Clover.NET | FishEye | Support | Account | Download | Buy Now

Subversion fisheye.access

Using a network Subversion protocol such as http, you can point a FishEye instance at any public repository. This could result in hundreds of people pointing FishEye instances at the one public repository, potentially causing an unintended denial-of-service attack against the repository.

For this reason, FishEye requires an administrator/commiter to set a certain property on a directory in the repository. FishEye queries this property to decide whether it will continue to access the repository; if the property is missing FishEye will immediately disconnect from the repository.

You do not need to set this property if using the file:// protocol.

Setting fisheye:allow

To tell FishEye it is allowed to access your repository, you must set the fisheye.access property to allow on the "URL + path" you have configured in FishEye.

For example, if you have configured FishEye with a URL of svn://foo.com/ and a path of . (or you have left path empty), then you would need to do something like this:

$ svn checkout -N svn://foo.com/ tmpworkspace
$ cd tmpworkspace
$ svn propset fisheye.access "allow" .
$ svn commit -m "grant fisheye access" .

If you configured a path of some/dir then use:

$ svn checkout -N svn://foo.com/some/dir tmpworkspace
$ cd tmpworkspace
$ svn propset fisheye.access "allow" .
$ svn commit -m "grant fisheye access" .
Note
The only value of fisheye.access that the current version of FishEye understands is allow, which grants access to any FishEye instance. A future version of FishEye will have more fine-grained control, allowing you to grant access to individual instances of FishEye.