Services/VCS: Difference between revisions

From DcUsers
No edit summary
No edit summary
 
(2 intermediate revisions by one other user not shown)
Line 12: Line 12:
https://vcs.duckcorp.org/
https://vcs.duckcorp.org/


Various VCS are possible: git, Mercurial, SVN, Bazaar…
If you have [[Services/Shell|shell access]]:

* public repositories are available in ''/srv/vcs/'' on ''vcs.duckcorp.org''
* you can create private repositories at will in your home directory
If you have [[Services/Shell|shell access]], public repositories are also available in ''/srv/vcs/'' on ''vcs.duckcorp.org''
* you can ask for a project-specific space in ''/srv/projects/'' on ''vcs.duckcorp.org'' and store the project private repositories in it


== Managing a Repository ==
== Managing a Repository ==


If you have [[Services/Shell|shell access]]:
Ask an administrator to create a new repository. Various VCS are possible: git, Mercurial, SVN, Bazaar…
* 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.
If you have [[Services/Shell|shell access]], then you will be able to manage your own


=== 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. Also, make sure that the repository has the proper permissions if you plan to activate Git or HTTP protocols:
chmod -R o+rX myrepo.git

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)]

Latest revision as of 03:31, 21 April 2020

Service 'VCS'
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. Also, make sure that the repository has the proper permissions if you plan to activate Git or HTTP protocols:

 chmod -R o+rX myrepo.git

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: