8 ms·

I use Gitea for personal git server, they have a curated list of things can do with it: https://gitea.com/gitea/awesome-gitea https://gitea.com/gitea/awesome-gi

by a012 6y ago

I use Gitea for personal git server, they have a curated list of things can do with it: https://gitea.com/gitea/awesome-gitea https://gitea.com/gitea/awesome-gitea What I like about it is the old UI of Github, mean time to start from scratch is very fast and low maintenance.

h_anna_h 6y ago
Please avoid gitea. I can't say anything about the other software but gitea is known for having accessibility issues, see https://github.com/go-gitea/gitea/issues/7057 https://github.com/go-gitea/gitea/issues/7057 Edit: the reason that I posted this was not due to some hypothetical blind people but rather because I have been in a situation where I want to show a cool project to a friend with vision issues but I can't because the project is hosted on a gitea instance. I posted this because I was unaware of this issue until recently and presumed that there would be others here who are also not aware of this.
- stonesweep 6y ago
  I tried out Gitea hosted via codeberg, and within a week disabled my account - Gitea allows usernames to be reused, there were bugs allowing people to push repos into other people's accounts (someone ran rampant on codeberg), you can view private repos via the Pages system and whatnot. In many of the issues, the current state is "it's a problem with Gitea" such as: https://codeberg.org/Codeberg/Community/issues/356 https://codeberg.org/Codeberg/Community/issues/356 HN readers are downvoting you, but Gitea's problems are real and they exist. Enough of them are listed in codeberg's issue pages that I felt the software/platform is very buggy and has a lot of security issues as just a generic user with one week of experience, much less an admin.
  - kenniskrag 6y ago
    > there were bugs allowing people to push repos into other people's accounts (someone ran rampant on codeberg), you can view private repos via the Pages system and whatnot. Do you have a bug report? I'm a gitea user and want to reproduce it.
    - stonesweep 6y ago
      I dug up the first one real quick for you, at the time I was just reviewing issues to see if I could help (codeberg) and browsed the list - you can farm here, and they tend to create an upstream issue in Gitea and link to it for many of the items (provide a good feedback loop to upstream): https://codeberg.org/Codeberg/Community/issues/355 https://codeberg.org/Codeberg/Community/issues/355 (edit: grammar)
- HexDecOctBin 6y ago
  Why is this being downvoted? Have people always been this selfish? I know that this website presents a corporate money-minded version of the Hacker ethos, but this level of psychopathy? Downvoting pleas for accessibility because you don't need it? Really?
  - dec0dedab0de 6y ago
    I'm guessing because it is a reply to someone saying they use it as a personal server. That is sort of like telling someone not to buy a sports car because it cant fit a wheelchair.
    - h_anna_h 6y ago
      My intent was to inform the people that were going to read the comment and decide to try gitea due to it of the issue. Although I would say that my comment would also be relevant to that user as long as their personal server is public and they do not want to exclude people with vision issues from viewing the projects that they host.
      - dec0dedab0de 6y ago
        I understood what you were saying. I was just trying to explain why some people would take offense to it. If you started with "if you intend for others to access your server" then I cant imagine any reasonable person would have had a problem with it, and there is no sense worrying about unreasonable people.
      - microtherion 6y ago
        I for one appreciate learning about the accessibility issues. It's something to keep in mind if I ever wanted to rely on my personal repo for a project shared with other people, and it's an aspect I cannot easily test myself, and generally don't think of testing myself until it's I've already committed myself to a particular solution.
  - eeZah7Ux 6y ago
    > I know that this website presents a corporate money-minded version of the Hacker ethos That would be an oxymoron. The https://en.wikipedia.org/wiki/Hacker_ethic https://en.wikipedia.org/wiki/Hacker_ethic is anti-corporate by definition. > but this level of psychopathy? Many times I've seen people downvoted to hell for pointing out accessibility issues around heavy websites.
- mekster 6y ago
  And for such a rare case we have to give up on using Gitea? Why not just point out its problem and let the users decide?
  - fao_ 6y ago
    > Why not just point out its problem and let the users decide? Is that not what the comment was saying?
    - MrGilbert 6y ago
      Nope, the comment started with: > Please avoid gitea. Gitea [...] is known for having accessibility issues, see [...] Which is not the same as saying: > Gitea [...] is known for having accessibility issues, see [...] The first one offers a clear request of action combined with an explaining fact, while the ladder just shows the fact and leaves the action item up to the reader.
      - fao_ 6y ago
        Right, but I don't see a tangible difference. People are responsible for themselves, if someone is going to stop using Gitea based on the fact that a random internet commenter decided to put "Please avoid Gitea" at the start of their explanation of flaws, isn't that their choice? I'm not sure how those three extra words "remove" anyone's "choice", can you explain why you think that is the case? Thanks.
ausjke 6y ago
gitea like everything else won't make everyone happy but for me it's a godsend, it's my personal git server for the last two years and I use it daily. however if you have special requirement like a large team, or accessiblity(which I didn't check) you can try something else. The point here is that, it's much easier to use gitea than to use git+gitolite+nginx unless you want to spend more time with sysadmin instead of development itself.
m463 6y ago
My journey went like this: I ran git in a container "like you're supposed to" with https access but I wanted better management than adding user access to apache. So I decided to upgrade to gitea. It was a pretty involved installation but I finally got it going. I set up a gitea cotnainer and was able to use it for a while. But one day it stopped working and I had to spend a bunch of time diagnosing why mariadb wasn't coming up. I can't recall exactly what i did (something with ib_logfile) but i finally got it going. And a few days later when checking on it, I noticed it was using a bunch of cpu time. Apparently it uses resources just sitting there idle, like 5% cpu. In the end, I made a git container again. I just used SSH access and one user: git # pacman -S git # useradd -m -G wheel -s /usr/bin/git-shell git # systemctl enable sshd repos are in ~/git/foo.git and ~/git/bar.git, ~/.ssh/authorized_keys for the hosts I give automated access to, password for others. $ git clone git@gitmachine:git/foo.git I liked the idea of git+https. And running gitea seemed like it would be like having my own git infrastructure!! But in my experience, git is easy with a minimal setup.
- simias 6y ago
  I recommend looking into gitolite, it's very simple and low maintenance and makes managing access a lot easier and with much more granularity than authorized_keys. It's basically just a simple perl script and a couple configuration files. It just work in my experience. If you end up scaling to the point where you have dozens of users and need to make regular changes to the config it becomes rather cumbersome, but for small groups of people (with a couple of build bots and the like that need read-only repo access) it's very well suited.
- dpedu 6y ago
  A database server? Gitea is as "involved" as you make it - mariadb certainly is not a requirement for Gitea. I've been using Gitea with sqlite for a couple years and upgrades have never ever been more complex than replacing the image with a new one. If minimality is a concern then you really can't get any simpler than `./gitea`.
  - m463 6y ago
    hmmm... I guess I learned something new from you. I followed these instructions setting it up: https://wiki.archlinux.org/index.php/gitea https://wiki.archlinux.org/index.php/gitea I see it does mention sqlite so that would have simplified things. I wonder if it would have prevented the container from using cpu. Now I'll have to spin up the gitea container again and experiment :)
DrBazza 6y ago
Came here to say gitea. It's a single exe, the set up is trivial, and it just runs on my raspberry pi and backs up to my NAS.
a20eac1d 6y ago
How do you handle backups with your instance? I have a simple bash script that sync the entire data directory to Backblaze and I'd love to hear easier or better ways to do this.
- a012 6y ago
  Yes, a bash script will do.

by a012 6y ago

h_anna_h 6y ago

Please avoid gitea. I can't say anything about the other software but gitea is known for having accessibility issues, see https://github.com/go-gitea/gitea/issues/7057 https://github.com/go-gitea/gitea/issues/7057 Edit: the reason that I posted this was not due to some hypothetical blind people but rather because I have been in a situation where I want to show a cool project to a friend with vision issues but I can't because the project is hosted on a gitea instance. I posted this because I was unaware of this issue until recently and presumed that there would be others here who are also not aware of this.

stonesweep 6y ago
I tried out Gitea hosted via codeberg, and within a week disabled my account - Gitea allows usernames to be reused, there were bugs allowing people to push repos into other people's accounts (someone ran rampant on codeberg), you can view private repos via the Pages system and whatnot. In many of the issues, the current state is "it's a problem with Gitea" such as: https://codeberg.org/Codeberg/Community/issues/356 https://codeberg.org/Codeberg/Community/issues/356 HN readers are downvoting you, but Gitea's problems are real and they exist. Enough of them are listed in codeberg's issue pages that I felt the software/platform is very buggy and has a lot of security issues as just a generic user with one week of experience, much less an admin.
- kenniskrag 6y ago
  > there were bugs allowing people to push repos into other people's accounts (someone ran rampant on codeberg), you can view private repos via the Pages system and whatnot. Do you have a bug report? I'm a gitea user and want to reproduce it.
  - stonesweep 6y ago
    I dug up the first one real quick for you, at the time I was just reviewing issues to see if I could help (codeberg) and browsed the list - you can farm here, and they tend to create an upstream issue in Gitea and link to it for many of the items (provide a good feedback loop to upstream): https://codeberg.org/Codeberg/Community/issues/355 https://codeberg.org/Codeberg/Community/issues/355 (edit: grammar)
HexDecOctBin 6y ago
Why is this being downvoted? Have people always been this selfish? I know that this website presents a corporate money-minded version of the Hacker ethos, but this level of psychopathy? Downvoting pleas for accessibility because you don't need it? Really?
- dec0dedab0de 6y ago
  I'm guessing because it is a reply to someone saying they use it as a personal server. That is sort of like telling someone not to buy a sports car because it cant fit a wheelchair.
  - h_anna_h 6y ago
    My intent was to inform the people that were going to read the comment and decide to try gitea due to it of the issue. Although I would say that my comment would also be relevant to that user as long as their personal server is public and they do not want to exclude people with vision issues from viewing the projects that they host.
    - dec0dedab0de 6y ago
      I understood what you were saying. I was just trying to explain why some people would take offense to it. If you started with "if you intend for others to access your server" then I cant imagine any reasonable person would have had a problem with it, and there is no sense worrying about unreasonable people.
    - microtherion 6y ago
      I for one appreciate learning about the accessibility issues. It's something to keep in mind if I ever wanted to rely on my personal repo for a project shared with other people, and it's an aspect I cannot easily test myself, and generally don't think of testing myself until it's I've already committed myself to a particular solution.
- eeZah7Ux 6y ago
  > I know that this website presents a corporate money-minded version of the Hacker ethos That would be an oxymoron. The https://en.wikipedia.org/wiki/Hacker_ethic https://en.wikipedia.org/wiki/Hacker_ethic is anti-corporate by definition. > but this level of psychopathy? Many times I've seen people downvoted to hell for pointing out accessibility issues around heavy websites.
mekster 6y ago
And for such a rare case we have to give up on using Gitea? Why not just point out its problem and let the users decide?
- fao_ 6y ago
  > Why not just point out its problem and let the users decide? Is that not what the comment was saying?
  - MrGilbert 6y ago
    Nope, the comment started with: > Please avoid gitea. Gitea [...] is known for having accessibility issues, see [...] Which is not the same as saying: > Gitea [...] is known for having accessibility issues, see [...] The first one offers a clear request of action combined with an explaining fact, while the ladder just shows the fact and leaves the action item up to the reader.
    - fao_ 6y ago
      Right, but I don't see a tangible difference. People are responsible for themselves, if someone is going to stop using Gitea based on the fact that a random internet commenter decided to put "Please avoid Gitea" at the start of their explanation of flaws, isn't that their choice? I'm not sure how those three extra words "remove" anyone's "choice", can you explain why you think that is the case? Thanks.

ausjke 6y ago

gitea like everything else won't make everyone happy but for me it's a godsend, it's my personal git server for the last two years and I use it daily. however if you have special requirement like a large team, or accessiblity(which I didn't check) you can try something else. The point here is that, it's much easier to use gitea than to use git+gitolite+nginx unless you want to spend more time with sysadmin instead of development itself.

m463 6y ago

My journey went like this: I ran git in a container "like you're supposed to" with https access but I wanted better management than adding user access to apache. So I decided to upgrade to gitea. It was a pretty involved installation but I finally got it going. I set up a gitea cotnainer and was able to use it for a while. But one day it stopped working and I had to spend a bunch of time diagnosing why mariadb wasn't coming up. I can't recall exactly what i did (something with ib_logfile) but i finally got it going. And a few days later when checking on it, I noticed it was using a bunch of cpu time. Apparently it uses resources just sitting there idle, like 5% cpu. In the end, I made a git container again. I just used SSH access and one user: git # pacman -S git # useradd -m -G wheel -s /usr/bin/git-shell git # systemctl enable sshd repos are in ~/git/foo.git and ~/git/bar.git, ~/.ssh/authorized_keys for the hosts I give automated access to, password for others. $ git clone git@gitmachine:git/foo.git I liked the idea of git+https. And running gitea seemed like it would be like having my own git infrastructure!! But in my experience, git is easy with a minimal setup.

simias 6y ago
I recommend looking into gitolite, it's very simple and low maintenance and makes managing access a lot easier and with much more granularity than authorized_keys. It's basically just a simple perl script and a couple configuration files. It just work in my experience. If you end up scaling to the point where you have dozens of users and need to make regular changes to the config it becomes rather cumbersome, but for small groups of people (with a couple of build bots and the like that need read-only repo access) it's very well suited.
dpedu 6y ago
A database server? Gitea is as "involved" as you make it - mariadb certainly is not a requirement for Gitea. I've been using Gitea with sqlite for a couple years and upgrades have never ever been more complex than replacing the image with a new one. If minimality is a concern then you really can't get any simpler than `./gitea`.
- m463 6y ago
  hmmm... I guess I learned something new from you. I followed these instructions setting it up: https://wiki.archlinux.org/index.php/gitea https://wiki.archlinux.org/index.php/gitea I see it does mention sqlite so that would have simplified things. I wonder if it would have prevented the container from using cpu. Now I'll have to spin up the gitea container again and experiment :)

DrBazza 6y ago

Came here to say gitea. It's a single exe, the set up is trivial, and it just runs on my raspberry pi and backs up to my NAS.

a20eac1d 6y ago

How do you handle backups with your instance? I have a simple bash script that sync the entire data directory to Backblaze and I'd love to hear easier or better ways to do this.

a012 6y ago
Yes, a bash script will do.