Hosting your own git server can be a fun learning experience used to understand the ins and outs of what goes into maintaining a codebase in private environments. You can set up a working private git-server in no time following the guide if you have a Raspberry-Pi handy. You can also set up on VM or AWS machines or any hosting service with Linux. NOTE: This guide just shows the basic setup, security mechanisms regarding user privileges, and committing restrictions that still need to be set up but are beyond the scope of this article. Let’s get Going! Shall We…. STEP-1: Setting up a New User to Handle Git Repositories For security purposes and ease of use, I’ll be setting up SSH keys for authentication b/w server and clients over the network. Log in to your existing pi user in raspberry-pi and set up a new user for your git-server. a) pi@hostname:~ $ sudo useradd -s /bin/bash -m [username] I’ll name my user and will be referring to it for the rest of the article. git The above command adds a new user, denotes shell to be used and denotes to create the home directory. -s -m Give the password to your new user: b) pi@hostname:~ $ sudo passwd git Fill in the password of your choice and change user to git and cd into git’s home directory. c) pi@hostname:~ $ su git Fill in the password. d) git@hostname:home/pi $ ) And then type to go to git’s home directory. e cd STEP-2: Setting up SSH-key Authentication for Git From your client machine, ssh into git to verify that you can remotely login into the user. a) m108falcon@quadre:~ $ ssh git@[ipaddr] If you have default port 22 set and user is set to active, you’ll be prompted for the password and log in. Enter the creds and you’ll be logged into git user in your raspberry-pi. b) Open new terminal tab, and do the following on the c) client machine. m108falcon@quadre:~ $ ssh-keygen Follow the steps, give a unique name to key and add a password if you wish. d) After the keys have been set up, send your identification pub key to the server e) m108falcon@quadre:~ $ ssh-copy-id -i [location]/unique_key.pub git@[ipaddr] Try logging into git user, if you’re still prompted to log in with a password then: f) m108falcon@quadre:~ $ ssh-agent [your shell] && ssh-add [location]/unique_key if you were logged in passwordless, then you can ignore the above command. STEP-3: Setting up Repositories Raspberry-Pi Within your raspberry-pi logged in as git, make a directory to store all git repositories: a) git@kleintragbar:~ $ mkdir [directory] I Named mine . Within srv, create a directory for the project you want to manage ending with . This is because .git helps Linux differentiate b/w standard directories and git-managed repositories. b) srv .git git@kleintragbar:~ $ cd srv
git@kleintragbar:~/srv $ mkdir [nameofyourrepo].git I Named mine and will be referring to it from now on. c) traceviz.git Initialize bare repository. Bare is needed because remote repositories need to keep track of changes and not have working trees. git@kleintragbar:~/srv/traceviz.git $ git init --bare Local Machine Go to your project directory and initialize git repository. Add a file and do the initial commit. a) m108falcon@quadre:~ $ cd Projects/traceroute_viz
m108falcon@quadre:~/Projects/traceroute_viz $ git init
m108falcon@quadre:~/Projects/traceroute_viz $ git add README.md
m108falcon@quadre:~/Projects/traceroute_viz $ git commit -m 'README' Add a remote address to your git repository. b) m108falcon@quadre:~/Projects/traceroute_viz $ git remote add origin ssh://git@192.168.29.69/home/git/srv/traceviz.git Add the address of your remote repository after c) ssh:// Push to the remote server. d) m108falcon@quadre:~/Projects/traceroute_viz $ git push -u ssh://git@192.168.29.69/home/git/srv/traceviz.git That concludes setting up repositories for pushing code. :) Testing the Pushed Code by Cloning On the client machine, go to a different directory than your project and clone the remote repository. a) m108falcon@quadre:~/Downloads $ git clone git@192.168.29.69:/home/git/srv/traceroute_viz.git And you’ll encounter this error: To fix it, go to your remote machine and modify file in the git server. b) HEAD Original contents of say: c) HEAD And change master to main. You can do so by simply editing files using your favorite editor (nano, vim, emacs, or any other of your choice). d) Delete your earlier cloned repo, and clone a new one and you’ll get all the files you need. e) Now, you’re truly set up with a local remote repository of your own. Have fun managing code with your buddies/roommates. All the best! 👍

Different

Keep

Nominated for 2022 - HackerNoon Contributor of the Year - Raspberry Pi

Nominated for 2022 - HackerNoon Contributor of the Year - Git

Too Long; Didn't Read

Boost your HackerNoon story @ $159.99! 🚀

A Guide on How to Host Your Own Git-Server With Raspberry Pi

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

11 Books Every Software Developer Should Read

12 Common Java Mistakes Made by Newcomers

3 Key Questions You Need To Answer Before You Push That Code

56 Stories To Learn About Beginners To Coding

A Q&A With Ashwin Kumar Uppala, Coach at Major League Hacking, on "Learning in Public" for New Devs

An Important Thing for Beginner Developer

11 Books Every Software Developer Should Read

12 Common Java Mistakes Made by Newcomers

3 Key Questions You Need To Answer Before You Push That Code

56 Stories To Learn About Beginners To Coding

A Q&A With Ashwin Kumar Uppala, Coach at Major League Hacking, on "Learning in Public" for New Devs

An Important Thing for Beginner Developer

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps