4 ms·

Interesting. I am just trying to decide between self-hosting Forgejo and other options for hosting Git in own private network.

by nicce 1y ago

omani 1y ago
am using gitea. but thinking of switching to serve (charm).
- sesm 1y ago
  I'm also using gitea, running on RPI5. Setup took like 15 mins, highly recommend.
  - omani 1y ago
    mine is running on an rpi zero w (v1). super low power consumption.
icy 1y ago
Could also consider running a Tangled knot (lightweight, headless git servers): https://tangled.org https://tangled.org
- rustman123 1y ago
  Does this support private repositories with collaboration?
  - icy 1y ago
    Not yet, unfortunately. Mostly due to protocol limitations—we use AT (https://atproto.com https://atproto.com) for federation.
    - xeonmc 1y ago
      can tangled support a forum-styled or subreddit-like thread discussion interface, on a per-repo basis so that "anyone could start a subreddit" via creating a discussion-only repo?
      - linguaz 1y ago
        Wondering if something like this could be implemented on tangled with public-inbox: https://public-inbox.org/README.html https://public-inbox.org/README.html > public-inbox implements the sharing of an email inbox via git to complement or replace traditional mailing lists. Readers may read via NNTP, IMAP, POP3, Atom feeds or HTML archives. > public-inbox stores mail in git repositories as documented in https://public-inbox.org/public-inbox-v2-format.txt https://public-inbox.org/public-inbox-v2-format.txt and https://public-inbox.org/public-inbox-v1-format.txt https://public-inbox.org/public-inbox-v1-format.txt > By storing (and optionally) exposing an inbox via git, it is fast and efficient to host and mirror public-inboxes.
      - icy 1y ago
        We’ve considered this a lot. Our issues implementation is threaded—perhaps more Stack Overflow-like. We’re thinking of renaming it to Discussions, and having the actual issue tracker be collaborators-only.
- nicce 1y ago
  That looks definitely interesting!
01HNNWZ0MV43FF 1y ago
Forgejo is working okay for me. Hard to justify using SSH for Git. Principle of least power and all that
- skydhash 1y ago
  Git is distributed, so there's no least power and all that. Everyone has full power over their own copy. What you want is one copy being the source of truth. You can always use HTTP for read-only access to that copy with a limited set of people having write access to update the copy. Patches can be shared via anything (git has built-in support for email).
- deleted 1y ago
  [deleted]
orblivion 1y ago
One of my favorite tools available for Linux is called gitolite. It's in the Debian repo. https://gitolite.com/gitolite/ https://gitolite.com/gitolite/ If you think the bare bones example is interesting and want something simple just for you or a small group of people, this is one step up. There's no web interface. The admin is a git repository that stores ssh public keys and a config file that defines repo names with an ACL. When you push, it updates the authorization and inits new repositories that you name. I put everything in repos at home and a have multiple systems (because of VMs) so this cleaned things up for me considerably.
- deltarholamda 1y ago
  gitolite is great. It's simple and extremely lightweight.
PaulKeeble 1y ago
A lot of people do host Forejo but unless you are actually working with other people and they need a reduction in access via pull requests it doesn't do much other than provide a pretty GUI to look at. The bare SSH approach makes more sense for personal projects.
bluehatbrit 1y ago
I really like forgejo, but the git hosting bit is really just one feature for me. Their ci/cd runners, package repos and such are all things I need and forgejo includes in one nice bundle. If I was just using it for git hosting I'd probably go for something more light weight to be honest.

Interesting. I am just trying to decide between self-hosting Forgejo and other options for hosting Git in own private network.

by nicce 1y ago

Interesting. I am just trying to decide between self-hosting Forgejo and other options for hosting Git in own private network.

omani 1y ago

am using gitea. but thinking of switching to serve (charm).

sesm 1y ago
I'm also using gitea, running on RPI5. Setup took like 15 mins, highly recommend.
- omani 1y ago
  mine is running on an rpi zero w (v1). super low power consumption.

icy 1y ago

Could also consider running a Tangled knot (lightweight, headless git servers): https://tangled.org https://tangled.org

rustman123 1y ago
Does this support private repositories with collaboration?
- icy 1y ago
  Not yet, unfortunately. Mostly due to protocol limitations—we use AT (https://atproto.com https://atproto.com) for federation.
  - xeonmc 1y ago
    can tangled support a forum-styled or subreddit-like thread discussion interface, on a per-repo basis so that "anyone could start a subreddit" via creating a discussion-only repo?
    - linguaz 1y ago
      Wondering if something like this could be implemented on tangled with public-inbox: https://public-inbox.org/README.html https://public-inbox.org/README.html > public-inbox implements the sharing of an email inbox via git to complement or replace traditional mailing lists. Readers may read via NNTP, IMAP, POP3, Atom feeds or HTML archives. > public-inbox stores mail in git repositories as documented in https://public-inbox.org/public-inbox-v2-format.txt https://public-inbox.org/public-inbox-v2-format.txt and https://public-inbox.org/public-inbox-v1-format.txt https://public-inbox.org/public-inbox-v1-format.txt > By storing (and optionally) exposing an inbox via git, it is fast and efficient to host and mirror public-inboxes.
    - icy 1y ago
      We’ve considered this a lot. Our issues implementation is threaded—perhaps more Stack Overflow-like. We’re thinking of renaming it to Discussions, and having the actual issue tracker be collaborators-only.
nicce 1y ago
That looks definitely interesting!

01HNNWZ0MV43FF 1y ago

Forgejo is working okay for me. Hard to justify using SSH for Git. Principle of least power and all that

skydhash 1y ago
Git is distributed, so there's no least power and all that. Everyone has full power over their own copy. What you want is one copy being the source of truth. You can always use HTTP for read-only access to that copy with a limited set of people having write access to update the copy. Patches can be shared via anything (git has built-in support for email).
deleted 1y ago
[deleted]

orblivion 1y ago

One of my favorite tools available for Linux is called gitolite. It's in the Debian repo. https://gitolite.com/gitolite/ https://gitolite.com/gitolite/ If you think the bare bones example is interesting and want something simple just for you or a small group of people, this is one step up. There's no web interface. The admin is a git repository that stores ssh public keys and a config file that defines repo names with an ACL. When you push, it updates the authorization and inits new repositories that you name. I put everything in repos at home and a have multiple systems (because of VMs) so this cleaned things up for me considerably.

deltarholamda 1y ago
gitolite is great. It's simple and extremely lightweight.

PaulKeeble 1y ago

A lot of people do host Forejo but unless you are actually working with other people and they need a reduction in access via pull requests it doesn't do much other than provide a pretty GUI to look at. The bare SSH approach makes more sense for personal projects.

bluehatbrit 1y ago

I really like forgejo, but the git hosting bit is really just one feature for me. Their ci/cd runners, package repos and such are all things I need and forgejo includes in one nice bundle. If I was just using it for git hosting I'd probably go for something more light weight to be honest.