Common configuration scenarios¶

• Common configuration scenarios
  • Force repository creation for all projects
    • Only one local repository per project
  • Local repositories or no repository
  • Secure repositories
  • Retain the old behaviour

Here are tips on how to configure SCM Creator for common tasks:

Force repository creation for all projects¶

This configuration will be useful if you plan to use Redmine for hosting projects with source codes and all repositories should be located on your server (no external repositories should be used).

• Configure all enabled SCMs to use SCM Creator;
• Disable SCMs which are not used by SCM Creator;
• Set auto_create to force;
• Set force_repository to true;
• Set only_creator to true;
• Set deny_delete to true.

Only one local repository per project¶

The same configuration as above but you want users to be able to create only one repository.

• All steps as above;
• Set max_repos to 1.

Local repositories or no repository¶

This configuration is similar to the previous one but allows projects without any repository.

• Configure all enabled SCMs to use SCM Creator;
• Disable SCMs which are not used by SCM Creator;
• Set auto_create to force;
• Set only_creator to true.

Secure repositories¶

Using local repositories is unsecure and can lead to information disclosure as described here so this configuration is recommended to everyone. With such configuration SCM Creator is used as a workaround for the previously mentioned vulnerability.

• Disable Filesystem SCM;
• Set allow_add_local to false;
• Set allow_pickup to false.

Retain the old behaviour¶

As it was mentioned in the previous configuration options allow_add_local and allow_pickup are set to false by default this way changing the default behaviour of Redmine. Of course, this can be unwanted.

• Set allow_add_local to true;
• Set allow_pickup to true.