this post was submitted on 17 Jan 2025
90 points (98.9% liked)

Linux

7306 readers
290 users here now

A community for everything relating to the GNU/Linux operating system

Also check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] pe1uca@lemmy.pe1uca.dev 13 points 3 months ago (1 children)

My question would be, if you're only archiving repos, why do you need a forge?
A simple git clone <repo> to any your archival directory would be enough to store them, there's no need for you to use a forge software.

Are there any other features of gitea you use?

[–] rowdyrockets@lemm.ee 13 points 3 months ago (1 children)

I like having the codebase in an easily presentable way. Git clone with a cron job would work fine but doesn’t tickle my fancy enough.

[–] dnzm@feddit.nl 8 points 3 months ago (1 children)

If you mean a (read-only) web interface, there's also cgit and gitweb.

I mean, it's your party and if Gitea works for you, that's great. It still is a bigger piece of software than what you need (or at least what you've told so far), it's up to you to determine if you're fine with that.

[–] rowdyrockets@lemm.ee 3 points 3 months ago

You can rest assured. I’m fine with it.