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

Gitea – Alternative to GitLab and GitHub

gitea.io

Post reply on HN
Print view View original

81–90 of 124 posts

Re: Gitea – Alternative to GitLab and GitHub

#81

Post by falsedan »

patkai wrote: post #76

Just wondering if it's time to start to decouple the client and the server. I did that with mail and use a native client only, and hosting a git repo on DO or similar should not be too big of an issue either.

For a solo dev, running a remote is a great idea and way cheaper than paying for GH private repos. You're giving up some availability and disaster recovery, but as a solo dev those aren't big problems (spin up a new host, configure your SSH keys, push). I did this years ago!

When the remote is shared (with other devs or tools), then you have the hassle of provisioning accounts, updating keys when they get lost, implementing ACLs, setting them, recording who changes what refs for audit trails, availability/backups becomes an actual problem, managing disk space + garbage collection, etc. The time you spend on those interruptsion is time (and concentration) that you're not spending on what you want to do. That's where the value proposition of GitHub comes in…

GitHub then has the value-adds/lock-in of easy webhook integrations, gh-pages branch, issues, wiki, and the web UI.

If all you want is somewhere to push code that's always available & private to you, then I'd look into using some could-based object store to host your repo. If you want to share the repo with other devs/tools… let me know where to find 99 other people willing to spend $5/month on this kind of thing.

Re: Gitea – Alternative to GitLab and GitHub

#82

Post by bshacklett »

Boulth wrote: post #53
sago wrote: post #23

Git is a distributed version control system. Every repo can be the master repo. 'Master' is purely a function of convention. It is worth stressing that you need no software to 'host' git. Every git repository is 'self hosting', by design. Tools like this primarily provide a web client to a repository not intended as a working copy, with some optional non-git code collaboration tools, such as issues, and an inbox of p…

I agree, additionally git has a built in server for sharing repos over the network. What I'd personally like to see is a repo viewer similar to Github but implemented purely in JavaScript and cloning repos in the fly just like the native git does. Git.js ( https://github.com/yonran/git.js ) has something like that but it looks old and ugly.

There are some real world problems with that: * Many networks limit access between wireless clients, preventing the connection between develop ER machines. * Host based firewalls often prevent services from listening on client machines. Getting security exceptions for this can be difficult to impossible in some organizations. * Discovery and initial remote config can be painful. While largely trivial from a technical perspective, this kind of thing can cause resistance from many end users.

I'm not arguing against your suggestion, but these are things that need to be solved if this workflow is ever going to see mainstream adoption. Network infrastructure and security has been geared towards centralization for a long time. That's going to need to change if we want to empower distributed applications of this nature (which I believe we do).

Re: Gitea – Alternative to GitLab and GitHub

#84

Post by falsedan »

simias wrote: post #63
sago wrote: post #23

Git is a distributed version control system. Every repo can be the master repo. 'Master' is purely a function of convention. It is worth stressing that you need no software to 'host' git. Every git repository is 'self hosting', by design. Tools like this primarily provide a web client to a repository not intended as a working copy, with some optional non-git code collaboration tools, such as issues, and an inbox of p…

The more I think about it the more I think Fossil[1] has the right approach by bundling bug tracking and wiki within the VCS. If git did the same thing (and the tools were usable) then nobody would worry about github "going bad" or anything like that. Changing your host would be as simple as changing your 'origin', anybody could replicate all the information easily. When I first heard about Fossil it sounded a bit li…

I feel like asking a poject manager to fiddle with some SCM system to get through grooming could be a bit unreasonable. I can't see how Fossil does ticketing to see if it's PM-friendly…

I feel like code reviews naturally should be stored alongside the code it's reviewing, and like the PoC shown by git-appraise from Google[0]

0: https://github.com/google/git-appraise

Re: Gitea – Alternative to GitLab and GitHub

#85

Post by falsedan »

ahauxuueei wrote: post #68
k__ wrote: post #56

Earlier quoted context omitted.

AFAIK the Linux Kernel doesn't have a single source of truth.

You are mistaken. Linux kernel dev branch single source of truth is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin... The stable branches have their single source of truth repositories, too.

I think replying to "it doesn't have a single source of truth" with "actually there are multiple single sources of truth" kind of makes the OP's case for them.

Re: Gitea – Alternative to GitLab and GitHub

#86

Post by olavgg »

merb wrote: post #62
francis-io wrote: post #28

Does Gitea still not have a good mechanism for backup and restore? I wanted to move away from Gogs but this is a show stopper for me.

well I think besides gitea dump there isn't really another way of backup.

I use ZFS snapshots with send & receive, works very well!

Re: Gitea – Alternative to GitLab and GitHub

#87

Post by falsedan »

Freak_NL wrote: post #18
PaulRobinson wrote: post #7

Entertainingly the code is hosted on github. :-) I'd have more confidence in it if it could self-host and I was able to see gitea inside of a gitea instance and that was the main workflow. Like this, it feels like maintainers aren't prepared to eat their own dog food just yet. That's fine, but I'll take a pass until that's fixed.

You could open a well-worded issue for it (“Gitea code base should be hosted on gitea instance”) and track that. There is a chance that the developers will close it as a WONTFIX of course.

> well-worded issue

Your example is not well-worded; it's a demand. I'd expect a well-worded issue to share some story about how you were working to achieve some goal, so you tried setting up gitea to self-host the gitea repo, and were surprised that it didn't work (and share the errors etc. that you saw). Then the devss can prioritise your issue by understanding how blocked you are by the missing behaviour, and even propose a workaround or alternative way of achieving your goal.

Re: Gitea – Alternative to GitLab and GitHub

#88

Post by projectramo »

k__ wrote: post #56
tjoff wrote: post #43

Earlier quoted context omitted.

For the vast majority of use cases centralization is an essential feature. You want that single source of truth, then you can have tons of branches etc. outside but without that single source everything falls apart if you are a team of more than one person. I'd argue that even a single developer really benefit from a "centralized" repository. It helps with maintainability, backups, syncing between machines (oh, my wo…

AFAIK the Linux Kernel doesn't have a single source of truth.

Before I read the other responses, I assumed it was just Linus’ personal repo

Re: Gitea – Alternative to GitLab and GitHub

#89

Post by angelsl »

falsedan wrote: post #85
ahauxuueei wrote: post #68

Earlier quoted context omitted.

You are mistaken. Linux kernel dev branch single source of truth is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin... The stable branches have their single source of truth repositories, too.

I think replying to "it doesn't have a single source of truth" with "actually there are multiple single sources of truth" kind of makes the OP's case for them.

What are you saying??

There is a single source of truth for a particular version of Linux.

Re: Gitea – Alternative to GitLab and GitHub

#90

Post by fergie »

sago wrote: post #23

Git is a distributed version control system. Every repo can be the master repo. 'Master' is purely a function of convention. It is worth stressing that you need no software to 'host' git. Every git repository is 'self hosting', by design. Tools like this primarily provide a web client to a repository not intended as a working copy, with some optional non-git code collaboration tools, such as issues, and an inbox of p…

You’re not paranoid, and it does matter. Distributed systems definitely struggle to stay distributed. Git is a great example, as are most cryptocurrencies, which despite being distributed by design, generally come to rely on centralised wallets and trading platforms.

The web itself seems to be be becoming more centralised- more people spend more time on fewer websites. Websites are increasingly being hosted on a tiny number of mega cloud services, rather than millions of independent server rooms.

Centralisation is a real concern.

Post reply on HN