Want to automatically reflect Git repository updates to multiple client PCs

git-push is not suitable for deployment purposes.I think we should consider another method.

I felt that this question was a XY problem or hammer nail disease.

git-pushI think there is a misunderstanding about the command itself.

git push:

The git push command communicates with other repositories, calculates what is in your local database and not in the destination repository, and then pushes the difference to the destination repository.This command usually authenticates in some way because it requires write access to the destination repository.

• (Assumed) git-push updates the Git repository on PCs 1, 2, and 3, not the source code (version-managed files checking out to the working directory).
  • Requires git-checkout to update files in the working directory.
• We need an authentication mechanism for users who did を in the figure to write to PCs 1, 2, and 3.
  • For example, SSH protocol requires an SSH server on PCs 1, 2, and 3.

• Requires git-checkout to update files in the working directory.

• For example, SSH protocol requires an SSH server on PCs 1, 2, and 3.

Other things that came to mind:

• Adding remote repository settings and setting up an authentication server are troublesome as PC4,5,6... and users increase.

If there are no conditions other than those mentioned in the questionnaire, wouldn't it be easy to set up a shared directory on the NAS and mount it on PC1, 2 and 3 respectively?
I think Git hook is available as a way to update files to be placed in the shared directory.