There is no "supported" way to deal with corrupted git repos that doesn't require server downtime #524
Labels
Laid to Rest
We honestly don't plan to fix this issue but it still represents an active problem with the software
V3
Things labelled with this probably won't be fixed ever in suite version 3
The reclone button recreates static directories, leading to data loss (or at least it claims to, I haven't tested for obvious reasons).
and libgit2sharp likes to randomly hold file locks on random git directories or files (not to mention you'd still have to manually mirror the git config).
So right now, the "official" solution to dealing with corrupted git repos is to shut down the server, backup the static folder, reclone, recompile, restore the static folder, launch.
Not workable for obvious reasons.
The "unofficial" solution to dealing with corrupted git repos is to upgrade tgs3 to the same version so it will bug out and not restart the service, then shut down the tgs service, then manually reclone the git repo, copy the git config from the old repo, then re-launch the service.
The text was updated successfully, but these errors were encountered: