I’m looking to self-host a GitHub alt on a cheap Linux VPS for personal use. Any rec?

0 points

I wouldn’t self host any git unless it was unimportant. Too easy to dick up disks.

permalink
report
reply
10 points

Well thats what backups are for, but may be start with a mirror or with unimportant stuff for at least a year ;) Also proprietary service can delete your data, too. This happens especially when you are using the generous free tier and they decide to make more money. See Evernote, Gitlab, Heroku…

permalink
report
parent
reply
-5 points

🙄 if I had a dime for every time I’ve heard an engineer say I got this for backups…

permalink
report
parent
reply
7 points

Well guess what. They say that cause they’re damn right.

permalink
report
parent
reply
5 points
*

You wouldn’t host anything important without doing it properly.

That should be obvious, man.

permalink
report
parent
reply
-2 points

Not even remotely close to true. Services are mostly half assed. Doing them correctly is time consuming and expensive.

permalink
report
parent
reply
0 points

Gitlab at least used to be the open source release of GitHub. I ran it in my lab for a while but stopped as I was using github anyway. It was easy to setup and maintain but it used a lot of resources. I ran it on a vm, there is likely a docker build as well.

permalink
report
reply
2 points

GitLab and GitHub were always developed separately by completely different people and have never shared code.

permalink
report
parent
reply
80 points

Strong recommend for Forgejo. It’s a community fork of gitea that’s actively maintained by the community and a great open source nonprofit.

It’s actually a drop in replacement for gitea if you are using that now.

Super lightweight. Super snappy, and it supports GitHub Actions style CI/CD.

permalink
report
reply
15 points
*

Big +1 for Forgejo, also they are actively working on implementing Federation, i.e. in the future Forgejo servers will be able to exchange information as a federated network, just like good old Lemmy 😊 If you want to try the toolchain (Forgejo+Woodpecker CI), it’s what Codeberg.org (run by the German nonprofit organization of the same name) offers freely.

permalink
report
parent
reply
1 point

what’s the benefits of being federated for code?

permalink
report
parent
reply
1 point

This will allow you to browse & contribute to projects hosted on other instances without having an account there. Imagine using the GitHub search to find a project on Gitlab, then opening an issue there without ever even leaving GitHub. The protocol is called ForgeFed.

permalink
report
parent
reply
7 points

The actions are amazing, and I was also able to integrate them with tailscale so I can build and deploy everything within my network automatically.
I run it in a vps with 1cpu and 2gb ram along several other services.

permalink
report
parent
reply
15 points

Gitea.

permalink
report
reply
1 point

Isn’t this a spin-off of gogs?

I still need to convert.

permalink
report
parent
reply
2 points
*

Skip it and go right to forgejo : it’s the current tip of the iceberg.

permalink
report
parent
reply
1 point

Maybe, depends on the migration path. Gitea proved impossible to migrate to.

permalink
report
parent
reply
2 points

The majority of maintainers stayed with Gitea. Forgejo is not the tip, they still pull the majority of their commit from gitea directly.

permalink
report
parent
reply
0 points

Apparently. When I wound up choosing Gitea for my own purposes, I don’t recall even learning about Gogs somehow.

permalink
report
parent
reply
1 point

I picked gogs before I knew about the gitea fork. (Maybe even before the fork)

permalink
report
parent
reply
1 point

@khoi@slrpnk.net probably others already suggested, gitea is as lightweight as you can go with a nice interface and features

permalink
report
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 4.9K

    Monthly active users

  • 3.6K

    Posts

  • 80K

    Comments