services:rcs:start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
services:rcs:start [2014/12/12 13:38] – Changed code to monospace font behrmj87 | services:rcs:start [2014/12/12 13:56] – glaubitz | ||
---|---|---|---|
Line 7: | Line 7: | ||
==== 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 56: | Line 56: | ||
==== Collaborating with other users ==== | ==== Collaborating with other users ==== | ||
+ | |||
+ | This section shall demonstrate how a second user would clone the repository from the server, make changes, commit them and eventually push them back to the repository. | ||
+ | |||
+ | To simulate this scenario in this example, we just create a new empty folder called //repo2// where we clone a second local working copy into. This is basically the same as if a second user clones the remote repository into their home directory. | ||
+ | |||
+ | To clone the remote repository we just created, it's best practice to specify the remote repository using the full hostname of the server (servername + domain) as well as the full path on the server (as opposed to using ''/ | ||
+ | |||
+ | After cloning, we change into the //myrepo// directory of the repository and verify the commit history using the already known '' | ||
{{: | {{: | ||
+ | |||
+ | Now, we just create a second file as described in the section above. Then use '' | ||
{{: | {{: | ||
+ | |||
+ | Changing back to the first user who just needs to call '' | ||
{{: | {{: | ||
+ | |||
+ | |||
+ | |||
+ | ===== Short summary of useful git commands ===== | ||
+ | |||
+ | * '' |
services/rcs/start.txt · Last modified: 2014/12/15 09:09 by behrmj87