This guide explains how to use the ToolsCloud Manager tool to manage your ToolsCloud environment.

The ToolsCloud Manager tool can be accessed through the URL <COMPANY>.toolscloud.net/toolscloud/manager .

How to configure advanced properties in your environment

In the ToolsCloud Manager main screen, click on “Advanced Configuration. In the next screen, you can configure settings like how the emails are sent by Redmine, how much memory you want your JBoss server to use, and more. All fields in this form have a contextual help that explains what information to put in any of them.

Checking the status and restarting the application servers

The ToolsCloud environment uses two application servers:

  1. Apache, used by Redmine, Git and Subversion
  2. JBoss, used by Nexus and Hudson

Clicking in the “Application Servers Management” option, in the main ToolsCloud screen, you can see these application servers logs and you can stop or restart them, if needed.

Configuring access to Subversion

By default, no LDAP group has access permissions to the Subversion repository. To change this, do:

  1. In ToolsCloud Manager main screen, click on “Managing Subversion Access”
  2. In the next screen, you’ll see a list of access rules configured in the system. If you want to add a new rule, click on “Add new access rule”
  3. In the “Subversion Path” field, inform the path you want to restrict access to. For example, if the Subversion URL of the path you want to protect is https://mytoolscloud.toolscloud.net/repos/myProject, fill this field with “/myProject”. I.e., use always as path whatever is after the base Subversion URL, which in this example is https://mytoolscloud.toolscloud.net/repos. If you want to change permissions over the whole repository, use “/” in this field. Note that if a user has an access permission in one directory, he will have the same permission in all the subdirectories. For example, if a user has read and write permission in the “/” directory and only read permission in the “/myProject” directory, the permission on the “/” directory wins, so he will have read and write access to the “/myProject” directory as well.
  4. Select the LDAP group you want to give a permission access. By default, there is only one group available, the “employees” group, but you can create as many groups as you want. To do that, use the phpldapadmim tool and create a new group add new groups in the “ou=groups/ou=svn-groups” subtree.
  5. Select the permission you want to give to the group: read only or read and write.
  6. Click on the “Create” button.

You can also delete and edit access rules using the same interface.

Attention! Changes in the access rules will not be immediately applied to Subversion. Wait about 10 minutes to have the new rules applied to the repository.

Configuring access to GIT

If you want to change the access permissions to GIT, do the following:

  1. In the ToolsCloud Manager tool, select the “GIT Access Management” option
  2. In the next screen, select “Git Access Control”
  3. In the next screen, you will see a list of the access rules configured in the environment. If you want to add a new rule, click on “Add new access rule”
  4. In the “GIT Path” field, inform the path you want to restrict access. For example, if the GIT URL of the path you want to protect is  https://mytoolscloud.toolscloud.net/git/repository.git/myProject, put in this field “/repository.git/myProject”. I.e., use always the path after GIT base URL, which in this example is  https://mytoolscloud.toolscloud.net/git . Note that if a user has an access permission in one directory, he will have the same permission in all the subdirectories. For example, if a user has read and write permission in the “/repository.git” directory and only read permission in the “/repository.git/myProject” directory, the permission on the “/repository.git” directory wins, so he will have read and write access to the “/repository.git/myProject” directory as well.
  5. Select the LDAP group you want to give permission to. By default, there is only one group available, the “employees” group, but you can create as many groups as you want. To do that, use the phpldapadmim tool and create a new group add new groups in the “ou=groups/ou=git-groups” subtree.
  6. Select the permission you want to give to the group: read only or read and write.
  7. Click on the “Create” button.

You can also delete and edit access rules using this same interface.

How to create new GIT repositories

By default, the GIT installed in your environment has already a repository called “repository.git”. You can create other repositories if you want:

  1. In the ToolsCloud Manager tool, select the “GIT Access Management” option
  2. In the next screen, select “Manage GIT Repositories”
  3. Click on the “Add Repository” option
  4. In the next screen, choose a name for your repository. Since this name will be the name of the directory being created, use a name with no special characters or spaces. You can also give a description for the repository.
  5. Click on “Create”.

You can also delete a repository and edit its description using this same interface.

ATTENTION! If you delete a repository, you will delete all the data on it. This can not be undone. Use this operation with maximum care.