There are many options for free repository storage and hosting, one is enough. This guide recommends GitHub for its excellent documentation and good feature set. [1]
If you lack a GitHub account, here are instructions.
Note
Each combination of user and workstation requires a different ssh key. Use the following command will generate missing ssh keys for a user:
if [ ! -f ~/.ssh/id_rsa ]; then ssh-keygen -N '' -f ~/.ssh/id_rsa; fi
Copy your SSH key to the clipboard with the console command:
cat ~/.ssh/id_rsa.pub | xclip |
There is no need to start from scratch when creating a documentation project. Instead, clone or fork someone else’s open source work. With your GitHub account,
GitHub will make a copy of the repository for you, and then switch to view your copy.
Once you own a repository on GitHub, you will want to clone it. The GitHub repository is remote, and cloning makes a local copy which you can edit. Here is the console command:
git clone (link_to_your_project) ~/Projects/doc-publish
There are two parameters to the git clone command. First is your project name, which is the text following “Git Read-Only” in the image below. (But copy the text from your fork of the repository please, so it will have your name instead of “AAltsys.”) The second parameter is the folder name to create for the project.
You may have noticed: doc-publish contains a repository from GitHub. Committed changes in the doc-publish folder are updated to GitHub with the command:
git push
Footnotes
[1] | Wikipedia shows a comparison of options for free repository hosting at http://en.wikipedia.org/wiki/Comparison_of_open_source_software_hosting_facilities. |