Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Poll: Self Hosting Git Repositories

news.ycombinator.com

Post reply on HN
Print view View original

71–80 of 86 posts

Re: Poll: Self Hosting Git Repositories

#71

Post by sieabah »

DoctorDabadedoo wrote: post #48
rapnie wrote: post #13

Gitea (originally a fork of Gogs) is moving fast, and they are adding ActivityPub federation support to the software. This will allow you to collaborate with projects hosted on remote Gitea instances (and other software once they add federation support too). If you are working on FOSS then Codeberg [1] is a good Gitea instance, which offer Woodpecker CI and Codeberg Pages. [1] https://codeberg.org

Gitea is love. There are not a lot of shenanigans and it just does the job. If you want vcs with an online interface it's great for personal use and smaller teams. If you want fancier stuff like integrated CI/CD that is more common out there, Gitlab is an option, but running it by yourself it's not as simple (as gitea), for example.

Gitlab is extremely simple to run yourself. I've been doing it for 2 years at this point. What is really difficult about the operation?

Re: Poll: Self Hosting Git Repositories

#74

Post by jason_slack »

iveqy wrote: post #21

if it's for personal use and no access rights are needed, just use ssh. If you need to add more people, but don't require access right for the git repos (i.e. everyone will be able to force push). Still use ssh, but create a git user and git-shell as the shell to improve security. If you want to go one step up, I was looking at soft-serve, however it's too immature yet. So I added a git-shell-commands folder and adde…

> reviews

Are you saying that I can self-host and have the same "review" functionality as GitHub when reviewing PR's?

Re: Poll: Self Hosting Git Repositories

#75

Post by teekert »

whitesilhouette wrote: post #65
teekert wrote: post #49

Earlier quoted context omitted.

Do you mean use VSCode with Remote-SSH and just work on a server?

What you are talking about is remotely accessing and working on a codebase. That has nothing to do with repository management. As mprime1 replied, it's more on the lines of firing up the terminal to create the git repository. Then go back to your local system and git clone/pull the thing. Then you fire up your local VSCode and work on it and then finally push the changes. This way the whole team can work seamlessly a…

Thanx for the explanation, so if you create the repo on the server, can you just got clone server.ip then? How do you clone it? Does that git init —bare command create a server?

Re: Poll: Self Hosting Git Repositories

#76

Post by brynb »

I made Redwood, a general purpose p2p/distributed database (and blob store) with pluggable merge algorithms (including some cool CRDTs, like what @josephg is working on).

Turns out it makes for a great self-hosted git solution, so I made a git remote plugin that allows you to interact with it using regular vanilla git commands: https://github.com/redwood/redwood/tree/libp2p-connectivity2...

Re: Poll: Self Hosting Git Repositories

#77

Post by jarbus »

rapnie wrote: post #13

Gitea (originally a fork of Gogs) is moving fast, and they are adding ActivityPub federation support to the software. This will allow you to collaborate with projects hosted on remote Gitea instances (and other software once they add federation support too). If you are working on FOSS then Codeberg [1] is a good Gitea instance, which offer Woodpecker CI and Codeberg Pages. [1] https://codeberg.org

Was just about to say this, I’m so excited for Gitea to get federation support and think they could really give GitHub a run for their money. I think a lot of major foss projects would switch over to a self hosted instance if it didn’t require users to create an additional account for every instance

Re: Poll: Self Hosting Git Repositories

#79

Post by saurik »

teekert wrote: post #75
whitesilhouette wrote: post #65

Earlier quoted context omitted.

What you are talking about is remotely accessing and working on a codebase. That has nothing to do with repository management. As mprime1 replied, it's more on the lines of firing up the terminal to create the git repository. Then go back to your local system and git clone/pull the thing. Then you fire up your local VSCode and work on it and then finally push the changes. This way the whole team can work seamlessly a…

Thanx for the explanation, so if you create the repo on the server, can you just got clone server.ip then? How do you clone it? Does that git init —bare command create a server?

git clone teekert@ssh.example.com:path/like/scp

If you also want public access over http you can activate one of the default hooks (so a single "rename a file" command on the server) and then export it using literally any web server software (as it is a folder of dumb files).

Re: Poll: Self Hosting Git Repositories

#80

Post by teekert »

saurik wrote: post #79
teekert wrote: post #75

Earlier quoted context omitted.

Thanx for the explanation, so if you create the repo on the server, can you just got clone server.ip then? How do you clone it? Does that git init —bare command create a server?

git clone teekert@ssh.example.com:path/like/scp If you also want public access over http you can activate one of the default hooks (so a single "rename a file" command on the server) and then export it using literally any web server software (as it is a folder of dumb files).

Ah! Somehow I was assuming some magic in the cloning, some server-client relation. There is not I guess, and that is actually logical. Also refreshing in a way.
Post reply on HN