Skip to main content

If you are thinking of self-hosting # you may find this interesting.

https://news.ycombinator.com/item?id=31971684

Things can be kinda.. heavyweight. Or as one comment puts it, and generalizing to # projects in general:

"This is something I've noticed a lot of open core projects suffer from. They make architecture decisions that make sense for their huge, multi-tenant production system but correspondingly make self-hosting on a single node feel like administering a rube goldberg machine."

Gitlab Architecture Overview | Hacker News

news.ycombinator.com
#gitlab #opencore
in reply to smallcircles (Humane Tech Now)

Classic James P.
Classic James P.
• •
This is why you should instead host #, and they're even getting # support, so it can be federated! (Pull requests work between instances.)
One good instance is # @codeberg.

cc @ta180m
#codeberg #activitypub #gitea @​
in reply to smallcircles (Humane Tech Now)

Adrian
Adrian
• •
To be fair, as another commenter notes, GitLab provides documentation on how to do configuration in "a memory-constrained environment": https://docs.gitlab.com/omnibus/settings/memory_constrained_envs.html
Unknown parent

Lien Rag
Lien Rag
• •
Are discussions/tickets/issues/whatever alos transfered when migrating from Github to Gitea/Codeberg ?

@james @humanetech @codeberg @ta180m
@smallcircles (Humane Tech Now) @​ @Classic James P.
in reply to Lien Rag

​
​
• •
GitHub discussions can't be exported, but PRs, issues, wikis, releases, and milestones can all be transferred when migrating from GitHub to any Gitea instance.
⇧