4 ms·
> This is a great way to [...] work on server-side files without laggy typing or manual copying This is the usecase mentioned in the article and it wouldn't wo
by cl3misch 1y ago
> This is a great way to [...] work on server-side files without laggy typing or manual copying
This is the usecase mentioned in the article and it wouldn't work with a bare repo. But if the server your SSH'ing to is just a central point to sync code across machines, then you're right: multiple hoops mentioned in the article are solved by having the central repo bare.
- liveoneggs 1y agoyeah it seems odd that they don't just have remote> $HOME/repos/foo.git and then clone from there locally and remotely
- seba_dos1 1y agoFWIW a single user working on a remote versioned directory is indeed a reasonable use-case for receive.denyCurrentBranch=updateInstead, but IMO the article should have made it clear that it's not necessarily a good choice in general.
- kragen 1y agoSee https://news.ycombinator.com/item?id=45713074 https://news.ycombinator.com/item?id=45713074 for a worked example of how it works with a bare repo.