plankton@programming.dev to Programmer Humor@programming.dev · 1 年前What comes to mind?programming.devimagemessage-square53fedilinkarrow-up1574arrow-down14cross-posted to: bikinibottomtwitter@lemmy.world
arrow-up1570arrow-down1imageWhat comes to mind?programming.devplankton@programming.dev to Programmer Humor@programming.dev · 1 年前message-square53fedilinkcross-posted to: bikinibottomtwitter@lemmy.world
minus-squarePumpkin Escobar@lemmy.worldlinkfedilinkEnglisharrow-up8·1 年前It has been on my list to figure out how to move to forgejo, need to do it soon before the migration process breaks or gets awful.
minus-squareOpisek@lemmy.worldlinkfedilinkarrow-up11·1 年前If you’re using docker: change your image name from gitea to forgejo. Repull. Done. Baremetal should be just as simple. Migrations are as easy as leaving all the data in-place and changing the binary at this moment in time.
minus-squaresorter_plainview@lemmy.todaylinkfedilinkarrow-up3·1 年前The project already started to diverge. If you have an older version don’t update until you migrate.
minus-squarewewbull@feddit.uklinkfedilinkEnglisharrow-up3·1 年前Migration is seamless. Uninstall one binary and install the other.
It has been on my list to figure out how to move to forgejo, need to do it soon before the migration process breaks or gets awful.
If you’re using docker: change your image name from gitea to forgejo. Repull. Done. Baremetal should be just as simple. Migrations are as easy as leaving all the data in-place and changing the binary at this moment in time.
The project already started to diverge. If you have an older version don’t update until you migrate.
Migration is seamless. Uninstall one binary and install the other.