What is a bare Git repo and why you need them 

Finally I don't need to factor the tempo of the video by 1.5 or 2 to follow it without falling asleep or getting distracted. 😄

Huh, I never actually thought to use them for that purpose. Nice one.

Be careful, if you host all your repos on a local disk you risk losing them if something happens. A huge benefit of remote hosting (like that provided by github) is that you don't have to worry about losing your work for good. In fact, github recently backed up a ton of repositories to a secure arctic facility (arctic code vault) that stores several copies of data in different formats

@@harleyspeedthrust4013 You're absolutely right but I have that covered with daily backups on my NAS, an external HDD and a USB thumbdrive, plus weekly backups on a remote backup service. I have never considered github as a backup solution, just a necessity to host my workflow until I discovered I could just have it locally with this video. You're right though, DO BACKUP FOLKS ;-)

Before I said "Igitigit", but now I say "Super".

Ummm.... Are you short on storage space or something? The bare repo doesn't do anything that the full one doesn't.

For one, other people can't push to a branch in another repo that has the same name and is currently checked out.

@@EngineerMan I see. I must have missed that in the video.

Great! Would be very interesting to see this in convination with git worktree

I think it's Xubuntu if I'm not mistaken. He mentioned this in a few videos, including "10 things you can do with Linux that you can't do with Windows ".

You missed the point of the video. You won't get any source code with a bare repository that is the whole point of it.

heinzerbrew wrong

@@bulletinmybeard How so?

Mercurial/svn share /some/ of these concepts, but will be completely different commands (at the very least). But if you can help it, don't ever use mercurial/svn. The technology is so outdated and strictly worse than git in almost every way. The only benefit something like svn has is that it comes pre-packaged with a GUI and a little easier to get started with. Any serious engineer uses git and is the industry standard.

@@bdafeesh Thanks! Good advice.

Keep in mind he's been programming for 20 years. The best answer to this is to actually build things.

\o/

praise the sun ( son ) of nils torvalds

Yes, if you have the original repo as the bare repo's upstream remote (e.g. if you cloned the bare repo from GitHub), then you can just "git push" from the bare repo. Any commits you've pushed to the bare repo will then get pushed to the upstream.

Yes, particularly useful for internal networks and ones with shared drives.

I think an ftp server would work, you could put it's ip in when you're cloning

Have you looked into using GitLab? www.techrepublic.com/article/how-to-set-up-a-gitlab-server-and-host-your-own-git-repositories/

@@sabrinnnaaaaaaa You can use ssh and set up a shared directory on the server for the repos to live in.

If I understand correctly, the bare repo acts like a fork, so it wouldn't update with the original repo

You have to push to the bare repo, as you would with a remote repo (github, etc).

There's lots and lots of online resources and thus, lots of places to start. It's hard to point to one specific resource, but searching for "getting started with git", "git for beginners" or "git tutorial" will ger you something to work with :)

It depends on what you want. He explains the difference in the video. A bare git repo won't have your workspace. So if you want your complete repo backed up then you need to back up the whole thing. If you just want to be able to restore your project then the bare git will be the bare minimum to backup. Git it?

Self answering: no explanation is needed, it is super extra simple => the fact of cloning the repo from the file system creates a git repo that does not need either ssh or https. When doing git push origin master, it will simpy copy to the filesystem address. Simple and direct like that. I could not believe it.

I think you answered your own question. GitHub likely uses bare repos as the base.

Its becose the command git clone, without --bare creates the workspace.

xubuntu

A computer you do work on. Eg a desktop or laptop

@@benjamincvcvcv7 Ah, gotcha. Thanks for the info!

Mmm... Yes I was wondering why the big fuss? I see so many positive comments here, but from what I can tell the only advantage with the bare git is that it doesn't take up as much space since it is only the git folder. There are people gushing with praise for this video and how useful this tip is, but I don't see what is so great about it. What am I missing?

@@heinzerbrew You use ssh and set up a shared folder on a server for your remotes. So you don't need github, etc.

@@unabonger777 Correct you don't need git hub, you never did before this video. So why are people losing their minds about how awesome this video is? I am not trashing the video. I just don't get some people's reactions.

So you can use a local folder instead of a remote service like github to pull/push from.

@@user-yb1cm4fd6h thanks for response. Think I need to research a bit more 👍

@@user-yb1cm4fd6h ummm you can do that with a regular repository.

Did it all with my bear hands.

There are situations where github isn't the right option. For me they happen a lot. The fact that git can be used in this way is why I fell in love with it to start with. I can start a small project, run "git init" in the folder, and suddenly I've got version control, branches, and the ability to let coworkers collaborate with me by doing "git clone ssh://user@myip:/path/to/the/repo". And if you spread the work across multiple computers, git is giving you a ghetto backup solution anyway, since both machines have the full repo.

I have Russian subtitles?

@@EngineerMan It is the option that appears.

@@EngineerMan haha It generated automatically) RU-vid is kidding

@@EngineerMan but I can help you with Russian subtitles