Services/VCS: Difference between revisions
From DcUsers
No edit summary |
No edit summary |
||
Line 22: | Line 22: | ||
* you can create private repositories at will in your home directory |
* you can create private repositories at will in your home directory |
||
* ask an administrator if you need a project-specific space in ''/srv/projects/'' on ''vcs.duckcorp.org'' to store the project private repositories in it |
* ask an administrator if you need a project-specific space in ''/srv/projects/'' on ''vcs.duckcorp.org'' to store the project private repositories in it |
||
For the following steps, ask an administrator if you don't have shell access. |
|||
=== Git === |
=== Git === |
||
A Git repository needs to be a ''bare'' repository, created like this: |
|||
mkdir myrepo.git |
|||
cd myrepo.git |
|||
git init --bare |
|||
A public repository should have a proper short description defined. Either edit the ''description'' file into the bare repository. |
|||
To activate access via the Git protocol, you need to activate it: |
|||
cd myrepo.git |
|||
touch git-daemon-export-ok |
|||
To activate access via the HTTP protocol, you need to enable updating the Git internal references: |
|||
cd myrepo.git |
|||
mv hooks/post-update.sample hooks/post-update |
|||
Access methods sumup: |
|||
* Direct SSH access: <tt>ssh://login@vcs.duckcorp.org/srv/vcs/git/...</tt> |
* Direct SSH access: <tt>ssh://login@vcs.duckcorp.org/srv/vcs/git/...</tt> |
||
* [https://vcs-git.duckcorp.org/ Git via HTTP (read-only)] |
* [https://vcs-git.duckcorp.org/ Git via HTTP (read-only)] |
Revision as of 16:31, 1 October 2017
Description | A few VCS tools are available to DC users. | |||
---|---|---|---|---|
Prerequisite | Write access is currently limited to people having a shell account. No prerequisite for read access. | |||
Account | Global (registration required) | IPv6 Ready | Yes | |
Security Notes | This service is secure. |
Access
Use the following URL to access public repositories:
https://vcs.duckcorp.org/
Various VCS are possible: git, Mercurial, SVN, Bazaar…
If you have shell access, public repositories are also available in /srv/vcs/ on vcs.duckcorp.org
Managing a Repository
If you have shell access:
- ask an administrator if you need a space for public repositories
- you can create private repositories at will in your home directory
- ask an administrator if you need a project-specific space in /srv/projects/ on vcs.duckcorp.org to store the project private repositories in it
For the following steps, ask an administrator if you don't have shell access.
Git
A Git repository needs to be a bare repository, created like this:
mkdir myrepo.git cd myrepo.git git init --bare
A public repository should have a proper short description defined. Either edit the description file into the bare repository.
To activate access via the Git protocol, you need to activate it:
cd myrepo.git touch git-daemon-export-ok
To activate access via the HTTP protocol, you need to enable updating the Git internal references:
cd myrepo.git mv hooks/post-update.sample hooks/post-update
Access methods sumup:
- Direct SSH access: ssh://login@vcs.duckcorp.org/srv/vcs/git/...
- Git via HTTP (read-only)
- Git via Git protocol using git://vcs-git.duckcorp.org/... to access /vcs/git/...
- Git browser