services:rcs:start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
services:rcs:start [2014/12/12 13:26] – glaubitz | services:rcs:start [2014/12/12 13:38] – Changed code to monospace font behrmj87 | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== git on a shared grouphome ===== | ===== git on a shared grouphome ===== | ||
- | Using //git//, it's relatively simple and easy to set up a shared revision control system for a group using a folder which has read and write permissions for everyone who is a member of this group. At the Physics department, we have the // | + | Using '' |
==== Creating the shared git repository on the server ==== | ==== Creating the shared git repository on the server ==== | ||
- | First of all, open a terminal and open an SSH connection to // | + | First of all, open a terminal and open an SSH connection to // |
{{: | {{: | ||
Line 15: | Line 15: | ||
==== Clone a local working copy of the repository on the server ==== | ==== Clone a local working copy of the repository on the server ==== | ||
- | To use the newly created git repository, navigate back into your home directory using the //cd// command without any arguments. Then enter //git clone ssh: | + | To use the newly created git repository, navigate back into your home directory using the '' |
- | After cloning the //myrepo// repository, change into its folder and verify it's empty using the //ls// command: | + | After cloning the //myrepo// repository, change into its folder and verify it's empty using the '' |
{{: | {{: | ||
Line 23: | Line 23: | ||
==== Making changes and committing them to the local working copy ==== | ==== Making changes and committing them to the local working copy ==== | ||
- | Now we're going to demonstrate how to add a new file to the repository. For simplicity' | + | Now we're going to demonstrate how to add a new file to the repository. For simplicity' |
- | After creating a new file into the git repository folder, git is able to see that there a new, untracked files. This can be seen using //git status// (which is always very handy when checking the current status of the local working copy of the git repository). | + | After creating a new file into the git repository folder, git is able to see that there a new, untracked files. This can be seen using '' |
{{: | {{: | ||
- | Add the new file to the git repository by entering | + | Add the new file to the git repository by entering |
{{: | {{: | ||
- | To commit the changes, type //git commit -m " | + | To commit the changes, type '' |
- | **Note**: Unlike | + | **Note**: Unlike |
{{: | {{: | ||
- | Before we push the changes to the remote repository, we can verify the changes using the command | + | Before we push the changes to the remote repository, we can verify the changes using the command |
{{: | {{: | ||
Line 45: | Line 45: | ||
==== Push the local changes to the repository on the server ==== | ==== Push the local changes to the repository on the server ==== | ||
- | To push the changes to the server, we use //git push//. The //push// command requires information about the remote repository to be used (called //origin// by default) as well as the development branch to be pushed to the server (//master// by default if you didn't specify any additional branches). | + | To push the changes to the server, we use '' |
- | //git remote// lists the remote repositories that are currently available (additional can be defined using //git remote add//) while //git branch -a// lists the available branches. | + | '' |
- | Thus, in this case we need to run //git push origin master// to push our changes to the repository in the grouphome folder: | + | Thus, in this case we need to run '' |
{{: | {{: | ||
- | This is all that's needed to set up a remote git repository, clone a local working copy as well as push changes to the server. The rest of the description now describes how a second user can clone the repository, make their changes, push them and have the first user copy those new changes to their local repository using the //git pull// commmand. | + | This is all that's needed to set up a remote git repository, clone a local working copy as well as push changes to the server. The rest of the description now describes how a second user can clone the repository, make their changes, push them and have the first user copy those new changes to their local repository using the '' |
==== Collaborating with other users ==== | ==== Collaborating with other users ==== |
services/rcs/start.txt · Last modified: 2014/12/15 09:09 by behrmj87