Tell Gitea where to monitor changes?

I’ve had a few incidents recently where manually created NFOs for media files made using tinyMediaManager have been overwritten with undesired data in the scraping process that app utilizes. I’d like to have an easy method of version control so I can simply open another app and revert unwanted changes if they occur.

I’m given to understand that Gitea would be a viable solution to my problem. I’ve installed Gitea and created a repository, but I’m not sure what to do now to tell Gitea what directory and file type(s) I’d like it to track.

My current setup for the volume mounts, done in the community train app installer (App Version: v1.25.5-rootless; Version: v1.6.3), is:

Storage Config Type Host Path Mount Path
Gitea Config Storage Host Path /mnt/Tank/configs/gitea/appdata N/A
Gitea Data Storage Host Path /mnt/Tank/configs/gitea/gitea-data N/A
Gitea Postgres Data Storage Host Path /mnt/Tank/configs/gitea/pgdata N/A
Additional Storage Host Path /mnt/Tank/media/Shows /media/shows

How should I go about setting this new repository to monitor changes among NFO files located in /media/shows?

Gitea is a git server. Git is a version control/collaboration tool for mainly text files. You manually check in all your changes in a local git repository on your desktop, then push to Gitea for others to synchronise.

Gitea does not track changes of files and does not scale well with binary files.

Why not setup a ZFS snapshot task?

But it could be the backend for something like Gitwatch:

1 Like

My preferred setup for this would be that I manually commit changes to my NFOs whenever I update them (always manually), and then if something goes wrong I can use a web GUI to revert changes among specific files in a file browser.

Why not setup a ZFS snapshot task?

That was my first idea, but I’ve used GitHub desktop a bit before with a local-only repo and, unless I’m misunderstanding, it does exactly what I want. Am I misunderstanding something about what is happening with GitHub desktop, or is this a difference in scope/use between that and Gitea?

But it could be the backend for something like Gitwatch:

I’m not completely unwilling to use something like this program that @dan mentioned, if it does in fact do what I’d want. I already have a folder with a few useful Bash scripts to put it in, but something point-and-click would be nice.

Gitea is a self-hosted Github. A backend for your Github Desktop.

1 Like

Thank you for clarifying. I’ve found LinuxServer has a Docker image for GitHub Desktop, so I’ve gotten that set up as my solution for this.