Task:Git over ssh - Revision history

imported_>amigadave: task is apparently complete

2011-02-11T11:37:41Z

task is apparently complete

← Older revision		Revision as of 11:37, 11 February 2011
Line 1:		Line 1:
	{{task\|~~accepted~~}}		{{task\|completed}}


	Garage currently offers git over WebDAV access for software projects. Unfortunately this solution has several limitations. Apart from its slowness it is often unreliable, meaning that commits do not get to the repo properly. In some cases the repositories are completely unavailable (e.g. behind firewalls and proxeis) and there is no way to use hooks (ie. trigger events on certain actions happen to a repository).		Garage currently offers git over WebDAV access for software projects. Unfortunately this solution has several limitations. Apart from its slowness it is often unreliable, meaning that commits do not get to the repo properly. In some cases the repositories are completely unavailable (e.g. behind firewalls and proxeis) and there is no way to use hooks (ie. trigger events on certain actions happen to a repository).

imported_>amigadave: accepted task

2010-04-07T10:56:50Z

accepted task

← Older revision		Revision as of 10:56, 7 April 2010
Line 1:		Line 1:
			{{task\|accepted}}


	Garage currently offers git over WebDAV access for software projects. Unfortunately this solution has several limitations. Apart from its slowness it is often unreliable, meaning that commits do not get to the repo properly. In some cases the repositories are completely unavailable (e.g. behind firewalls and proxeis) and there is no way to use hooks (ie. trigger events on certain actions happen to a repository).		Garage currently offers git over WebDAV access for software projects. Unfortunately this solution has several limitations. Apart from its slowness it is often unreliable, meaning that commits do not get to the repo properly. In some cases the repositories are completely unavailable (e.g. behind firewalls and proxeis) and there is no way to use hooks (ie. trigger events on certain actions happen to a repository).

imported_>amigadave: no need to use tinyurl

2010-04-07T10:55:05Z

no need to use tinyurl

← Older revision		Revision as of 10:55, 7 April 2010
Line 7:		Line 7:
	I would like to keep the "git over WebDAV" as a backup solution, but preserving full access (read / write) via WebDAV while ssh is in use might be tricky. There are places where people are not allowed to establish ssh connections outside of their company network (for various security reasons), so having a plan B for them would be essential.		I would like to keep the "git over WebDAV" as a backup solution, but preserving full access (read / write) via WebDAV while ssh is in use might be tricky. There are places where people are not allowed to establish ssh connections outside of their company network (for various security reasons), so having a plan B for them would be essential.

	Git over ssh has also been [http://~~tinyurl~~.~~com~~/~~ydtl8lq~~ requested] by the community and we promised to deliver it after the server move.		Git over ssh has also been [http://lists.maemo.org/pipermail/maemo-developers/2009-November/022284.html requested by the community] and we promised to deliver it after the server move.

imported_>feri at 07:43, 7 April 2010

2010-04-07T07:43:04Z

← Older revision		Revision as of 07:43, 7 April 2010
Line 3:		Line 3:
	However the biggest advantage of the current solution is the access control. With WebDAV it is relatively easy to limit who can access a certain project and what sort of rights does the person have on that repository.		However the biggest advantage of the current solution is the access control. With WebDAV it is relatively easy to limit who can access a certain project and what sort of rights does the person have on that repository.

	Git over ssh would benefit developers. Access control will pose some challenges. We already have means to store the developers ssh key(s), and we certainly know the groups they belong to, so in theory it should be easy to put these together.		Git over ssh would benefit developers. Access control will pose some challenges. We already have means to store the developers ssh key(s), and we certainly know the groups they belong to, so in theory it should be easy to put these together.

	I would like to keep the "git over WebDAV" as a backup solution, but preserving full access (read / write) via WebDAV while ssh is in use might be tricky.		I would like to keep the "git over WebDAV" as a backup solution, but preserving full access (read / write) via WebDAV while ssh is in use might be tricky. There are places where people are not allowed to establish ssh connections outside of their company network (for various security reasons), so having a plan B for them would be essential.

	Git over ssh has also been[http://tinyurl.com/ydtl8lq requested] by the community and we promised to deliver it after the server move.		Git over ssh has also been [http://tinyurl.com/ydtl8lq requested] by the community and we promised to deliver it after the server move.

imported_>feri: New page: Garage currently offers git over WebDAV access for software projects. Unfortunately this solution has several limitations. Apart from its slowness it is often unreliable, meaning that comm...

2010-04-07T07:40:31Z

New page: Garage currently offers git over WebDAV access for software projects. Unfortunately this solution has several limitations. Apart from its slowness it is often unreliable, meaning that comm...

New page

Garage currently offers git over WebDAV access for software projects. Unfortunately this solution has several limitations. Apart from its slowness it is often unreliable, meaning that commits do not get to the repo properly. In some cases the repositories are completely unavailable (e.g. behind firewalls and proxeis) and there is no way to use hooks (ie. trigger events on certain actions happen to a repository).

However the biggest advantage of the current solution is the access control. With WebDAV it is relatively easy to limit who can access a certain project and what sort of rights does the person have on that repository.

Git over ssh would benefit developers. Access control will pose some challenges. We already have means to store the developers ssh key(s), and we certainly know the groups they belong to, so in theory it should be easy to put these together.

I would like to keep the "git over WebDAV" as a backup solution, but preserving full access (read / write) via WebDAV while ssh is in use might be tricky.

Git over ssh has also been[http://tinyurl.com/ydtl8lq requested] by the community and we promised to deliver it after the server move.