Roll you glorious cheese, and the insane people that seek to catch it. All in 4K video.
This is sort of covered in other spots, but not as clearly and from scratch. Here’s a complete guide that shows how to set up your own git server and git clients. I found this setup handy when trying out some more complex git merging commands and experimenting with remotes while learning git.
I tested this on Ubuntu 16.04 by creating an Ubuntu virtual machine and then cloning it. 1 VM for the server, and 2 for clients. I used bridged networking so each would get their own IP address, but that’s not required as long as the VM’s can communicate with each other over TCP/IP.
There are two ways to set the git accounts up. The first way shown has all client users accessing the repository through the same server user account. While each user’s submissions will be labeled correctly in the git log, having everyone use the same system account isn’t safe computing practices for groups. Instead, if you follow the instructions in the optional part you can use individual user accounts and keep things more safe.
First, on the server:
- Make sure ssh is installed on the server:
server$ sudo apt-get install openssh-server
- Make sure sshd is running/listed when you do a ps. If not, reboot or restart it.
server$ ps -A | grep sshd
- Make sure git is installed:
server$ sudo apt-get install git-core
- Add a user to the server that will hold the git repositories
server$ sudo adduser git server$ sudo passwd git server$ su - git server$ mkdir -p .ssh
Next, on your client:
- Make sure git is installed
client$ sudo apt-get install git-core
- Create an ssh key. While not strictly required, it’s a good idea to add a passcode to the key when prompted during key creation.
client$ ssh-keygen -t rsa
This should create a file called id_rsa.pub in your ~/.ssh directory. See documentation on ssh-keygen for full details.
- Copy the ssh key to the server’s git directory:
client$ scp ~/.ssh/id_rsa.pub firstname.lastname@example.org:/home/git/client_id_rsa.pub
Back on server:
- Add the client user’s key to the ssh list in the /home/git/.ssh directory
server$ mkdir ~/.ssh
- Append the client user key to the list of authorized keys
server$ cat ~/client_id_rsa.pub >> ~/.ssh/authorized_keys
- Create a new group called ‘gituser’ we’ll use for users to access our repository in /home/git/
sudo groupadd gituser sudo usermod -a -G gituser git
- Log out completely and back in. You MUST do this for group assignment to take effect orsubsequent chgrp/chmod commands won’t work.
- Make the git repository and tell it to share based on the group the user belongs to.
server$ cd ~git server$ mkdir -p mydepot server$ cd mydepot server$ git init --bare --shared=group Initialized empty Git repository in /home/git/mydepot/
- Set the permissions on the repository directory so that anyone in the new ‘gituser’ group can access it.
chgrp -R gituser /home/git/mydepot chmod -R g+rw /home/git/mydepot chmod g+s `find /home/git/mydepot -type d`
Back on client (if it is a clean client without files for the repo):
- Test your ssh connection by trying to ssh into the server (using the git user)
- Create the local project:
client$ mkdir -p depot/project1 client$ cd depot/project1 client$ git config --global user.email "email@example.com" client$ git config --global user.name "clientUsername"
- Clone the remote to your local system
client$ git clone ssh://git@serverurl_or_ip:/home/git/mydepot/ .
Enter your username password and you’re done. The clone and the remote should be connected. Push/Fetch as normal. See the optional part below if you don’t want to use a global git user account on the server.
Or – Back on client that HAS existing files you want to get to the server:
Lets say you have a client that already has a bunch of files or even a git repository and you want to start using a remote repository. Here’s how you can add those local files into the remote server repository you just created.
- Initialize the repository where your client files are
client$ git init Initialized empty Git repository in <blah> client$ git add . client$ git commit <Write something about this being a commit from the client>
- If you are going to using the git user account for all users, connect the project to your server this way:
client$ git remote add origin ssh://git@serverurl_or_ip:/home/git/mydepot/
If you don’t want to use the git account, then you must first create a user account on the server that matches the client userid (making sure to set the group/user properties on the server account), then use this:
client$ git remote add origin ssh://serverurl_or_ip:/home/git/mydepot/
Enter the password for your username or the ‘git’ server user depending on which one you used.
- Set up git configuration to avoid warnings and push:
client$ git config –global push.default simple
client$ git push –set-upstream origin masterYou will be prompted for the passkey you used when you created your RSA key in the above push step. Enter that passkey (not your git/user account password).
Optional – Using user accounts instead of a global ‘git’ account on the server.
The previous instructions had everyone use the same ‘git’ server user account when checking in – which means everyone must have the ‘git’ server account password. The log will show the right names, but security-wise this isn’t always best to use one global account on servers.
If you have more than one user but want everyone to log in separately, simply create a user account on the server like this:
On client for each client user:
- Create a ssh key on your client as before.
- Copy that key .pub to the server and append it to the authorized_keys file as above.
client$ scp .ssh/myclient_id_rsa.pub git@serverurl_or_ip:/home/git
- Append the client’s public key to the authorized keys
server$ cat ~/myclient_id_rsa.pub >> ~/.ssh/authorized_keys
- Create a user account that matches the userid on the client
server$ sudo useradd client_username server$ sudo passwd client_username
- Make sure the new user account has access to the /home/git/ project directories by setting their group membership:
server$ sudo usermod -a -G client_username
From now on, you don’t need to specify the git user account. Do not put the git@ part into the git clone url and use the username’s password when asked to log in:
client$ git clone ssh://serverurl_or_ip:/home/git/mydepot .
This method works great, but does require that you keep the client and server userid account passwords synced.
Setting up a Windows client:
Once the server is set up, you’re almost there. Microsoft has written a good guide. You’ll need OpenSSH or Windows 10 installed the generate an ssh key (if you don’t have one already).
Set the Youtube video settings to 4320p and watch a 12K video capture of New York downtown from the helicopter mounted Shotover K1 Hammerhead Aerial Camera Array.
Terry Davis is a programmer that has had a very difficult life. After a series of manic episodes, at 44 Terry is now homeless and most believe he has schizophrenia or suffering some other seriously debilitating mental disorder. He was most recently spotted on the streets here in Portland.
What’s unusual about Terry is that he wrote his own operating system: TempleOS. It’s free to download, and is written in HolyC. He even has his own youtube channel. There is even video of him debugging it while living homeless in his car in the middle of parking lots.
His life currently demonstrates the terrible state of mental health care in the United States, and the difficult reality of many homeless. They are often very intelligent, but have disorders that make them non-functional in society.
Warning: his more recent videos have racist and inappropriate sexual language.
Saki is a great author – I think he’s due for a re-discovery. He’s a humorist author that wrote around the turn of the century, but his biting wit and description of high society social foibles is timeless. Here’s a clip:
Clovis continued, “My mother is thinking of getting married.”
His host responded, “Again!”
“It’s the first time.”
“Of course, you ought to know. I was under the impression that she’d been married once or twice at least.”
“Three times, to be mathematically exact. I meant that it was the first time she’d thought about getting married; the other times she did it without thinking.
I’ve always been one that believes when you’re together, be together. Put your !@#$ cell phones away when having dinner together or enjoying a show. I personally believe the Phone Stacking Game should be mandatory. Now Yondr has come out with something almost better. Something I hope catches on.
You are handed one of their little Yondr pouches – slightly larger than a cell phone. You put your cell phone into the pouch and the case locks shut with a little pin/tag similar to those use in department stores on clothes. You can only unlock the pouch and get your phone back out at unlocking stations located at the exit.
This allows you to go to venues where you don’t want cell phones to be distracting the experience yet let each person retain ownership and control of their phone. Even better, if you might get an emergency call, you can hear the ring tone/feel the vibration and immediately exit to see it.
I can see parents using this with children, at movie theaters, or even churches.