Recently I just finished tearing down all my self-host services. Things facing the public internet might be convenient, but heck if I want to face that security nightmare in an ongoing way. All my git repos now live in a "git" folder I share amongst my fileserver and other machines with syncthing, hosting only the bare repos. If I need pull requests or issue tracking, it's got to be something that goes with the repos…
Self-Hosting Git
51–60 of 71 posts
Re: Self-Hosting Git
#52Does anyone have any thoughts on self-hosting https://sourcehut.org/ ? It seems like a very interesting option to me
Re: Self-Hosting Git
#53Recently I just finished tearing down all my self-host services. Things facing the public internet might be convenient, but heck if I want to face that security nightmare in an ongoing way. All my git repos now live in a "git" folder I share amongst my fileserver and other machines with syncthing, hosting only the bare repos. If I need pull requests or issue tracking, it's got to be something that goes with the repos…
Re: Self-Hosting Git
#54Earlier quoted context omitted.
I wouldn't. The last time I tried to use their software I asked if anyone had any insights with how to use it in Docker (much of it is written in Python) and the response I got was cringe worthy. I'm just some person on the internet so take that for what you will.
> the response I got was cringe worthy How so?
Re: Self-Hosting Git
#55What is meant by "big corporates turning open-source into a T-shirt farming service" ? Is the main point being made that, corporations are using open source (ie github) as a platform to commercialize software?
It probably refers to the controversy surrounding hacktoberfest: https://news.ycombinator.com/item?id=24643894
Re: Self-Hosting Git
#56Recently I just finished tearing down all my self-host services. Things facing the public internet might be convenient, but heck if I want to face that security nightmare in an ongoing way. All my git repos now live in a "git" folder I share amongst my fileserver and other machines with syncthing, hosting only the bare repos. If I need pull requests or issue tracking, it's got to be something that goes with the repos…
(nearly) all my projects live in an account on uberspace.com. This is a German shared hosting provider with quite great offerings. You get a shell (ok, no root/sudo because shared hosting) with 10GB space, databases and what not. A vibrant community providing installation resources for a massive amount of tooling: https://lab.uberspace.de/ I am in no way affiliated to them just a happy customer for 10+ years now. btw…
The hard part is remembering to update all of your software, and making sure you do it fast enough in case there is a zero-day.
The worst part is discovering that you installed a simple app and forgot about it; and now hackers got in, encrypted your files and database, and now want a ransom.
Re: Self-Hosting Git
#57Earlier quoted context omitted.
Others with some added functionality like web UI, in increasing line of complexity and features: gitolite gitea, gogs gitlab
There's also Pagure[1], which is in-between Gitea/Gogs and GitLab. Unlike most Git forges, Pagure has features that support decentralized development. For example, Pagure supports submitting pull requests with Git repos on any server (regardless of whether it's running Pagure or not) with its remote pull requests feature. Issues and pull request metadata are all stored as git repos using JSON files as data, making it…
Re: Self-Hosting Git
#58Recently I just finished tearing down all my self-host services. Things facing the public internet might be convenient, but heck if I want to face that security nightmare in an ongoing way. All my git repos now live in a "git" folder I share amongst my fileserver and other machines with syncthing, hosting only the bare repos. If I need pull requests or issue tracking, it's got to be something that goes with the repos…
1. Run Gitea on your server, but make it only available on localhost.
2. Connect to your server via SSH, and use the -L flag to forward the port that Gitea is using e.g.
ssh -L 8888:localhost:8888 me@myserver.com
3. Access Gitea by opening http://localhost:8888 (or whatever port you’re using) in your browser.However, this doesn’t work if you’d like to collaborate with anyone who you don’t trust enough to give SSH access to your machine.
It would also be annoying or impossible to open the web interfaces on mobile devices.
Re: Self-Hosting Git
#59As someone who had countlessly saying [0] this to at least to either setup a self-hosted Git repository or use that as a backup almost a year ago since GitHub made teams free [1] I do welcome anyone moving from GitHub to a self hosted solution. There are are several open-source software projects that have been doing the same thing but on a self-hosted solution. GitLab instance like (GNOME, GTK, etc) or cgit (wireguar…
Linux has even used Github once as a backup solution for hosting the main repo, during a very short period of time. The workflows git has been developed for in the first place has little to do with the non-git and mostly walled garden feature provided by hosted Saas, being Github or even Gitlab.com Of course some projects find it convenient, but I'm not impressed by the embrace/extend approaches, esp when it shapes t…
Re: Self-Hosting Git
#60Does anyone have any thoughts on self-hosting https://sourcehut.org/ ? It seems like a very interesting option to me
I wouldn't. The last time I tried to use their software I asked if anyone had any insights with how to use it in Docker (much of it is written in Python) and the response I got was cringe worthy. I'm just some person on the internet so take that for what you will.
There's no push-button magic for it, presumably because SourceHut the company (ie. Drew) isn't interested in running it in containers, but nothing is stopping you from trying. It's different from most Python software in that you're expected to use your OS's package manager and standard service tooling.