[tpfour]

Gitea isn't meant to replace Github... it's meant to be a self-hosted alternative to it. That's subtly different.

I use it for as my local git server on Debian 9. Binary is in the /home/me/gitea directory. Run the usual gitea setup, then copy this to /home/me/.config/systemd/user/gitea.service:

  [Unit]
  Description=Gitea (Git with a cup of tea)
  After=syslog.target
  After=network.target

  [Service]
  RestartSec=2s
  Type=simple
  WorkingDirectory=/home/me/gitea
  ExecStart=/home/me/gitea/gitea web
  Restart=always

  [Install]
  WantedBy=default.target

Then just systemctl --user daemon-reload && systemctl --user enable gitea. Then visit localhost:3000 and add it to your remotes (git remote add local ...) and you can push your changes to your own gitea instance.

[dspillett]

> Gitea isn't meant to replace Github... it's meant to be a self-hosted alternative to it. That's subtly different.

Furthermore it is not unusual to see people run Gitea, GitLab, or just stock git, for their main repository and use GitHub as a public mirror. This takes advantage of GitHub's inertia, and acts as an extra backup.

The way git is design to be distributed makes this easy to achieve for the actual repositories. Issue tracking, CI, and everything else that isn't actually git (the core source control feature-set) isn't as easy of course, as that is more product specific.

[hk__2]

> Then visit localhost:3000 and add it to your remotes (git remote add local ...) and you can push your changes to your own gitea instance.

Why would you want to run a git server on your personal computer?

[tpfour]

For me it has the following advantages:

- In-browser viewing of diffs and code - Issues management - Showing code to clients/other devs is simpler and prettier. - Can push to local and run tests on a fresh repo pulled in a VM

Honestly as with mostly everything, it can be achieved by other means. It's just what feels good to me. It's extremely lightweight but robust and fits well in my work environment. That is all code editing is done in Emacs with millions of opened tabs in Chrome. I make extensive use of workspaces in xfce and I just Ctrl-Alt-(Right/Left) my way around going back and forth Emacs/Chrome. I could just have a file manager opened and double click on every file, or open them in Emacs, but that isn't always necessarily faster (for me).

Tldr: Personal preference.

[arwineap]

If you have ssh enabled with an accessible git repo; you already do!

[JetSpiegel]

Just don't forget to create `--bare` repositories on the server.