plankton@programming.dev to Programmer Humor@programming.dev · 4 天前What comes to mind?programming.devimagemessage-square85fedilinkarrow-up1636arrow-down15
arrow-up1631arrow-down1imageWhat comes to mind?programming.devplankton@programming.dev to Programmer Humor@programming.dev · 4 天前message-square85fedilink
minus-squarePumpkin Escobar@lemmy.worldlinkfedilinkEnglisharrow-up11·3 天前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-squarewewbull@feddit.uklinkfedilinkEnglisharrow-up5·3 天前Migration is seamless. Uninstall one binary and install the other.
minus-squareOpisek@lemmy.worldlinkfedilinkarrow-up12·3 天前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·3 天前The project already started to diverge. If you have an older version don’t update until you migrate.
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.
Migration is seamless. Uninstall one binary and install the other.
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.