openvpn-install VS Gitea

and for OpenVPN: https://github.com/Nyr/openvpn-install

I'm trying to establish a private torrenting setup using qBittorrent on my local whitebox server machine using Ubuntu 22.04 and a Virtual Private Server (VPS) as a VPN using Ubuntu 22.04 and OpenVPN (I used https://github.com/Nyr/openvpn-install). My local machine, acting as a private tracker seedbox, has qBittorrent installed and configured to use port 15986 for inbound connections with tun0 as the network interface.

Hello, I installed an OpenVPN server on my Centos server using the easy install script here https://github.com/Nyr/openvpn-install.git My client is MacOS and it works fine for the most part BUT I need to access devices on the server's LAN When I'm using my home internet, I can access the server fine but everything that is not in the same subnet as what OpenVPN gave me does not work. When using LTE and network sharing on my computer, I can still access the server and now I can also access devices on the server's LAN that is not in the same subnet as OpenVPN. I don't understand why it behave like this and I want to always be able to access the server's LAN when connecting to the VPN.

https://github.com/Nyr/openvpn-install

My idea would be to create a Debian VM on Proxmox, and install OpenVPN using Nyr script (https://github.com/Nyr/openvpn-install) and create a user for each of my friends.

I bounced away from Gitea because they don't (last time I checked) have OIDC. I started[0] trying to revive-and-drive a previous PR[1] to add it, but the test failures are beyond my motivation to investigate and resolve.

[0] https://github.com/go-gitea/gitea/pull/33945

[1] https://github.com/go-gitea/gitea/pull/25664

It’s coming: https://github.com/go-gitea/gitea/pull/20311

I would be willing to guess that self hosting gitea as a backup mirror is less work than doing the same for Bluesky. But, just speculating

As I mentioned in a previous post - you can use "git" without Github by hosting an instance of the open-source Gitea service.

https://github.com/go-gitea/gitea

As mentioned in the last post, I keep my notes in git repositories. I originally used Obsidian for years as my note-taking application of choice after migrating away from Google Keep, using the vast library of community plugins (namely obsidian-livesync and obsidian-git) to back up and sync my notes on an interval to my 3 remotes; GitHub, my private Gitea instance for my private "second brain" type notes, and my Otterwiki instance (a wiki that runs on a git server of markdown files).

The solution to this is to use fake e-mails.

I can't say what Forgejo has over Gitea, but I can tell you Forgejo is missing everything from the 888 merged PRs in Gitea 1.23: https://github.com/go-gitea/gitea/releases/tag/v1.23.0-rc0

Repo license support, integrated Arch package repository, automatic issue suggestions, and the new review+homepage UIs would be notable ones for me.

See this issue: https://github.com/go-gitea/gitea/issues/1029

For years, "self-hosting" Gitea wasn't done because it was missing a bunch of useful collaboration features. Now, it looks like that gap has been closed. All of the specific features mentioned in that issue seem to have been fixed, and the big remaining task is figuring out below to actually migrate all the existing data out of GitHub -- which doesn't seem to be super high on the priority list.

We're not, and they're still in the process of discussion. It seems a bit early to fork and witch-hunt [0]:

> So clarification here: you asked me about that, but I haven’t been able to respond to you due to my illnesses and I’m just getting back on my feet now. So it’s not that it hasn’t been well received, it’s that I’ve been physically unable to respond to you.

[0]: https://github.com/go-gitea/gitea/pull/24257#issuecomment-23...

Yeah, I'm actually doing that with Gitea: https://about.gitea.com/

Some people went with the forgejo fork: https://forgejo.org/ though Gitea itself was a fork of Gogs, if I remember correctly: https://gogs.io/

I also ran GitLab in the past: https://about.gitlab.com/ but keeping it updated and giving it enough resources for it to be happy was troublesome.

There's also GitBucket: https://gitbucket.github.io/ and some other platforms, though those tend to be a little bit more niche.

Either way, there's lots of nice options out there, albeit I'd still have to admit that just using GitHub or cloud GitLab version would be easier for most folks. Convenience and all.