# using the following JSON-encoded payload: # When entering a URL, OpenProject will POST to this resource when repositories are created # This allows OpenProject to take control over the given path to create and delete repositories # repositories are to be created or deleted. # You may either specify a local path on the filesystem or an absolute URL to call when

# Use this command to the default SCM vendor command (taken from path). # Configuration of Source control vendors The following is an excerpt of the configuration and contains all required information to set up your data. It contains a YAML configuration section for repository management residing under the namespace scm. Managed repositories need to be enabled manually for each SCM vendor individually using the configuration.yml. You can create repositories explicitly on the filesystem using managed repositories. You can explicitly create local repositories for a project and configure repository access using permission the existing access-control functionality on a per-project level. This functionality is extended with managed repositories, whose life spans are actively controlled by OpenProject.

Using the default configuration, OpenProject allows you to link existing Subversion and Git repositories from the local filesystem (For Subversion, you can also integrate repositories from other servers using basic auth credentials).Īfter linking the repositories, you may browse the repository through OpenProject.

We support integration with the Apache webserver to create and serve repositories on the fly along with contributions to the fine-grained project authorization system of OpenProject. OpenProject can (by default) browse Subversion and Git repositories, but it does not serve them to git/svn clients.

Webdav client with checkout capability