Skip to Content

Changes for page Repository Access

Last modified by 5fbc055b7cc103006957e1ae on 2012-06-15 02.55:08
From version 1.1
edited by 5fbc055b7cc103006957e1ae
on 2012-06-15 12.17:54
Change comment: There is no comment for this version
To version 2.1
edited by 5fbc055b7cc103006957e1ae
on 2012-06-15 02.55:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,35 +1,44 @@
1 -(% style="" %)
2 -=== {{id name="RepositoryAccess-Publicaccess"/}}Public access ===
1 += {{id name="RepositoryAccess-Publicaccess"/}}Public access =
3 3  
4 -The Clazzes.org subversion and maven repositories can be accessed read-only by anonymous users. The URLs all follow the same schema, just replace {{code language="none"}}project-name{{/code}}. Generally, the svn and maven urls for all projects should also be written on their homepage. If you are not sure about the project name, you can visit [[https:~~/~~/maven.clazzes.org/org/clazzes/>>url:https://maven.clazzes.org/org/clazzes/||style="" shape="rect"]] and browse the list of projects there, or contact the project lead.
3 +=== {{id name="RepositoryAccess-SourceCode"/}}Source Code ===
5 5  
6 -(% style="" %)
5 +The Clazzes.org subversion and maven repositories can be accessed read-only by anonymous users. The URLs all follow the same schema, just replace {{code language="none"}}project-name{{/code}}. Generally, the svn and maven urls for all projects should also be written on their homepage. If you are not sure about the project name, you can visit [[https:~~/~~/maven.clazzes.org/org/clazzes/>>url:https://maven.clazzes.org/org/clazzes/||shape="rect"]] and browse the list of projects there, or contact the project lead.
6 +
7 7  * Subversion: http:~/~/svn.clazzes.org/svn/project-name/
8 8  * Maven Releases: http:~/~/maven.clazzes.org/org/clazzes/project-name
9 9  * Maven Snapshot-Releases: (% class="nolink" %)http:~/~/maven-snapshots.clazzes.org/org/clazzes/project-name
10 10  
11 -(% style="" %)
12 -=== {{id name="RepositoryAccess-Authenticatedaccess"/}}Authenticated access ===
11 +=== {{id name="RepositoryAccess-SoftwarePackagesforLinux"/}}Software Packages for Linux ===
13 13  
14 -(% style="" %)
13 +We provide .deb packages of some software for Debian and derived linux distros. A full list of the available software can be found at [[https:~~/~~/deb.clazzes.org/>>url:https://deb.clazzes.org/||shape="rect"]]. You can directly download source snippets for your {{code language="none"}}sources.list[.d]{{/code}} from there too.
14 +
15 +We highly recommend using {{code language="none"}}apt-transport-https{{/code}} to install the packages from https, but all URLs work as http too.
16 +
17 +To trust our archiver key, run the following command in a terminal as root:
18 +
19 +{{code language="none"}}
20 +wget -O - https://www.clazzes.org/gpg/pba-archiver.clazzes.org.asc |apt-key add -
21 +{{/code}}
22 +
23 +=== {{id name="RepositoryAccess-WindowsInstallers"/}}Windows Installers ===
24 +
25 +Some of our software packages are also available as Windows installers for 32 and 64 bit architectures from our [[downloads>>url:http://download.clazzes.org/||shape="rect"]] area.
26 +
27 += {{id name="RepositoryAccess-Authenticatedaccess"/}}Authenticated access =
28 +
15 15  Every project has a designated user name (usually the same as the project name), which may upload files subversion and maven repositories via ssh. Trusted user's ssh-keys are added to the authorized key list of the project-user. Access may be restricted to svn or include and the maven repository.
16 16  
17 -(% style="" %)
18 18  Write-enabled URLs for projects are built according to the following schema:
19 19  
20 -(% style="" %)
21 21  * Subversion repository: svn+ssh:~/~/project-name@svn.clazzes.org/svn/project-name
22 22  * Maven repository base URL: scpexe:~/~/project-name@maven.clazzes.org/var/www/htdocs/maven.clazzes.org
23 23  * Maven snapshot repository base URL: scpexe:~/~/project-name@maven.clazzes.org/var/www/htdocs/maven-snapshots.clazzes.org
24 24  * In place of {{code language="none"}}scpexe:{{/code}} you may be able to use {{code language="none"}}sftp:{{/code}} or {{code language="none"}}scp:{{/code}}
25 25  
26 -(% style="" %)
27 -==== {{id name="RepositoryAccess-Troubleshootingauthenticatedaccess"/}}Troubleshooting authenticated access ====
38 +=== {{id name="RepositoryAccess-Troubleshootingauthenticatedaccess"/}}Troubleshooting authenticated access ===
28 28  
29 -(% style="" %)
30 30  Before contacting the administrator or project lead because of technical problems, please make sure you have tried the following:
31 31  
32 -(% style="" %)
33 33  * Your ssh client must accept the clazzes.org server’s host keys before you can commit using {{code language="none"}}ssh+svn{{/code}}. In a terminal, call 
34 34  {{code language="none"}}ssh svn.clazzes.org{{/code}} and {{code language="none"}}ssh maven.clazzes.org{{/code}} once and accept the host key.
35 35  * If you have already made changes in a working copy downloaded via public access you can switch it to ssh-based access without loosing anything: svn switch ~-~-relocate (% class="nolink" %)http:~/~/svn.clazzes.org/project-name(%%) svn+ssh:~/~/util@svn.clazzes.org/svn/project-name
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -655812
1 +655781
URL
... ... @@ -1,1 +1,1 @@
1 -https://clazzes.atlassian.net/wiki/spaces/CLORG/pages/655812/Repository Access
1 +https://clazzes.atlassian.net/wiki/spaces/CLORG/pages/655781/Repository Access