Version 1 vs 2
Version 1 vs 2
Edits
Edits
- Edit by • rezzonico, Version 2
- Sep 13 2016 22:26
- Edit by • rezzonico, Version 1
- Sep 13 2016 22:26
Original Change | Next Change » |
Edit Older Version 1... | Edit Older Version 2... |
Content Changes
Content Changes
**Here you will learn how to create a simple repository and handle permissions**
Click on the //Create a new repository// button on your landing page.
{F135915}
Choose to create a Git repository
{F135917}
All you need to indicate in the next screen is a name for your repository
{F135919}
Now, let's set some policies
{F135921}
Default policies are quite liberal, we will have to edit that
{F135924}
We wish to give read access to some individual users. For that, we have to create a custom policy
{F135927}
...we can just add some users to the //Allow// list:
{F135929}
You can also set similar policies for Edit (this means: managers of the repository) and Push (this means contributors).
{F135931}
Now, you can go back to //Basics// and //Activate Repository//.
{F135933}
Let's have a look at your repository now by clicking on //View Repository//.
{F135936}
You can see access URLs for https (you need a VCS password for this) and ssh (you need to upload a SSH key for this), Those are the URLs to be put after `git clone` in your command line. The //Manage Repository// link will take you back to the configuration menu.
**Here you will learn how to create a simple repository and handle permissions**
Click on the //Create a new repository// button on your landing page.
{F135915}
Choose to create a Git repository
{F135917}
All you need to indicate in the next screen is a name for your repository
{F135919}
Now, let's set some policies
{F135921}
Default policies are quite liberal, we will have to edit that
{F135924}
We wish to give read access to some individual users. For that, we have to create a custom policy
{F135927}
...we can just add some users to the //Allow// list:
{F135929}
You can also set similar policies for Edit (this means: managers of the repository) and Push (this means contributors).
{F135931}
Now, you can go back to //Basics// and //Activate Repository//.
{F135933}
Let's have a look at your repository now by clicking on //View Repository//.
{F135936}
You can see access URLs for https (you need a VCS password for this) and ssh (you need to upload a SSH key for this), Those are the URLs to be put after `git clone` in your command line. The //Manage Repository// link will take you back to the configuration menu.
{F135944}
**Here you will learn how to create a simple repository and handle permissions**
Click on the //Create a new repository// button on your landing page.
{F135915}
Choose to create a Git repository
{F135917}
All you need to indicate in the next screen is a name for your repository
{F135919}
Now, let's set some policies
{F135921}
Default policies are quite liberal, we will have to edit that
{F135924}
We wish to give read access to some individual users. For that, we have to create a custom policy
{F135927}
...we can just add some users to the //Allow// list:
{F135929}
You can also set similar policies for Edit (this means: managers of the repository) and Push (this means contributors).
{F135931}
Now, you can go back to //Basics// and //Activate Repository//.
{F135933}
Let's have a look at your repository now by clicking on //View Repository//.
{F135936}
You can see access URLs for https (you need a VCS password for this) and ssh (you need to upload a SSH key for this), Those are the URLs to be put after `git clone` in your command line. The //Manage Repository// link will take you back to the configuration menu.
{F135944}
c4science · Help