Selfhosted

40183 readers

748 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

[email protected]

157

Forgejo forks its own path forward (forgejo.org)

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

30 comments fedilink hide all child comments

This is from last month, but I haven't seen any discussion of it. Seems like Forgejo is now a hard fork of Gitea, instead of being a soft fork like it was over the previous year.

The main reason I'm posting it now is this: "As such, if you were considering upgrading to Forgejo, we encourage you to do that sooner rather than later, because as the projects naturally diverge further, doing so will become ever harder. It will not happen overnight, it may not even happen soon, but eventually, Forgejo will stop being a drop-in replacement."

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

[–] [email protected] 4 points 7 months ago (7 children)

Interesting. Is there a migration path?

[–] [email protected] 9 points 7 months ago (5 children)

If you deployed with docker composr you just change the image and hit redeploy. Super simple.

[–] [email protected] 3 points 7 months ago (4 children)

Appreciate that, sounds super easy

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

It is. Did that when this was first announced

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

Huh, using their instructions for docker compose, I use docker pull codeberg.org/forgejo/forgejo:7.0.0 and it errors for manifest unknown. Removing the version tag so it default to latest doesn't help.

Do I need to make an account and docker login? That seems like it should be unnecessary for a simple pull.

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

Login isn't necessary, but there is no :latest tag published so you need to pull a version that exists. The current version is at codeberg.org/forgejo/forgejo:1.21.8-0 or at :1.21 if you want one that tracks patch updates (as found in the container registry).

[–] [email protected] 2 points 7 months ago

Ah, the docs reference V.7.0.0 so that's what I was trying with.

TY, that got her transitioned. The config actually pops a notice that 1.21.9 is available but I don't see that it's in the registry yet. I do like the :latest tag because then I can use watchtower, but I can understand why some people would want to specify the version.

load more comments (2 replies)

load more comments (3 replies)