Selfhosted

40173 readers

963 users here now

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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

160

Selfhost your own gitea instance - selfhosted, lightweight github alternative (4rkal.com)

submitted 2 months ago* (last edited 2 months ago) by 4rkal@lemmy.world to c/selfhosted@lemmy.world

36 comments fedilink hide all child comments

I've recently set up my own Gitea instance and I figured I'd share a simple guide on how to do it yourself. Hopefully this will be helpful to anyone looking to get started.

If you have any feedback please feel free to comment it bellow.

you are viewing a single comment's thread
view the rest of the comments

[–] cizra@lemm.ee 11 points 2 months ago (4 children)

I started running my own Gitea instance because I wanted a private place to host my Obsidian notes.

I don't have the time to read the article now, but permit a question: what do you use Gitea for?

I'm holding my dotfiles on a SSH server, clone/push over SSH, and it's enough to do Git. I don't need a ticket system, or wiki or anything (I use plaintext notes).

$ cat ~/.ssh/config
Host srv
  Hostname srv.mywhatever.com

$ git clone srv:/path/to/repo
$ cd repo
$ git push

[–] 4rkal@lemmy.world 2 points 2 months ago (1 children)

Great question

I always found setting up a git server from scratch to be quite confusing and I also like the webui that gitea offers.

But recently I have also started moving some of my github projects there so having a link (with a readme and everything) that I can share with others is important.

[–] cizra@lemm.ee 4 points 2 months ago (1 children)

If you have a place to host Forgejo/Gitea, you have a place to store a Git server. Set it up like this:

$ git clone --bare myrepo myrepo.bare
$ scp -r myrepo.bare srv:
$ cd myrepo
$ git remote add origin srv:myrepo.bare
# or
$ git remote set-url origin srv:myrepo.bare

Now git push etc work similar to GitHub, but you're using your server (named srv in SSH config, as shown in my previous post) as the remote storage.

Selfhosted Gitea is a way to get a wiki, bug tracker or whatnot - collaborate, for example, but it's not necessary to have a Git server for your personal use.

[–] asap@lemmy.world 5 points 2 months ago* (last edited 2 months ago)

Selfhosted Gitea is a way to get a wiki, bug tracker or whatnot - collaborate, for example, but it's not necessary to have a Git server for your personal use.

No, but it is amazing for browsing your repos and visually seeing what you did in a past commit or a branch, while your IDE is open to your latest code. Or copying and pasting something that you need from a different repo.

For Git experts, sure they can probably do all that better inside their IDE or CLI, but for us plebs, having your own Forgejo is incredible 😍

I have mine configured to disable the wiki and issues, etc, it's just the repo browser.

load more comments (2 replies)