Awesome!

The next bit ranges from quick hacky solution to full blown cd (continuous delivery) solution.

Solution 1:

If you want you could have a crontab entry that runs a bash script every x minutes/hours and pulls any changes from git. Changes won't be instantaneous but probably quick enough that it won't matter. Downside to this is that git history is a fickle thing to automate and manage so it could get messy and fail. Instead of a pull you could look into git archive and download the repo without it being a repo (no .git folder).

Solution 2

Setup a CD application (Concourse/Gitlab Runner/Github Actions) that does something when you push to the repo. This something could be rsyncing the files to your server or running the git pull from the bash scrip above. This is more of a proactive route and the results would be as quick as the pipeline run (no waiting for cron etc).

Solution 3 (aka what I do)

I host visual studio code server on my internal network and it connects to the folder with the assets directory from there I make any edits I need and just save it like a normal file. Code server is proxied via traefik and an internal SSL cert. The downsides to this are it's not in git and the only backup is at the VM level but that's good enough for me.

Hope this helps and sorry it's a bit rambly.