Selfhosted

38707 readers

677 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:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

824

I love my Gitea. Any tips and tricks? (sh.itjust.works)

submitted 8 months ago by [email protected] to c/[email protected]

75 comments fedilink hide all child comments

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

[–] [email protected] 5 points 8 months ago (1 children)

Is running a docker container a lot of overhead?

Ernestly asking, since my opinion is skewed cause im use to running containers.

[–] [email protected] 6 points 8 months ago* (last edited 8 months ago) (1 children)

Absolutely. Every service you run, whether containerized or not, is software you have to upgrade, maintain, and back up. Containers don't magically alleviate the need for basic software/service maintenance.

[–] [email protected] 2 points 8 months ago (1 children)

Yes, but doesn't that also apply for a machine running bare git?

Not containers also adds some challenges with posibly having dependecies problems. I'd say running bare git is not a lot easier than having a container with say forgejo.

[–] [email protected] 2 points 8 months ago* (last edited 8 months ago) (1 children)

No. It's strictly more complexity.

Right now I have a NAS. I have to upgrade and maintain my NAS. That's table stakes already. But that alone is sufficient to use bare git repos.

If I add Gitea or whatever, I have to maintain my NAS, and a container running some additional software, and some sort of web proxy to access it. And in a disaster recovery scenario I'm now no longer just restoring some files on disk, I have to rebuild an entire service, restore it's config and whatever backing store it uses, etc.

Even if you don't already have a NAS, setting up a server with some storage running SSH is already necessary before you layer in an additional service like Gitea, whereas it's all you need to store and interact with bare git repos. Put the other way, Gitea (for example) requires me to deploy all the things I need to host bare repos plus a bunch of addition complexity. It's a strict (and non-trivial) superset.

[–] [email protected] 1 points 8 months ago (1 children)

I dont know. 😆 im really just trying to get it in case -for example- of needing to advice someone in such a case :) my confusion probably comes from the fact that I have never host anything outside containers.

I still see it a bit diferent. A well structured container structure with configs as files instead of bare commands, back up volumes would be the same effort... But who knows. Regarding the rest like proxies, well you do not really need one.

Thanks taking the time to explain you point tho!

[–] [email protected] 1 points 8 months ago* (last edited 8 months ago)

Honestly the issue here may be a lack of familiarity with how bare repos work? If that's right, it could be worth experimenting with them if only to learn something new and fun, even if you never plan to use them. If anything it's a good way to learn about git internals!

Anyway, apologies for the pissy coda at the end, I've deleted it as it was unnecessary. Keep on having fun!