2 ms·
I like the simplicity, but does everyone actually log in to the server and edit the files directly in the same repo, or is the repo exposed over SSH and everyon
by imiric 2y ago
I like the simplicity, but does everyone actually log in to the server and edit the files directly in the same repo, or is the repo exposed over SSH and everyone works in forks on their own machines?
The first one doesn't really scale beyond a handful of people, since you risk losing work if the same file is being worked on by multiple people. Vim shouting at you that the file you're editing has changed on disk is not good enough.
I can see how this could work with a central repo, though. It does require everyone aligning on the same conventions and workflow, so you likely still need some software to ensure this is done correctly.
- stephenr 2y agoI assumed they meant a directory within the git repo not just a regular directory on the server filesystem.
- deleted 2y ago[deleted]
- mg 2y agoEverybody works on a fork on their own machine. Since everybody pulls the changes of the others and sees if something collides with their own changes, its pretty much possible to do it manually. Thats how I started this approach. It's really just a 0815 git based workflow. Just not for code but for a tasklist. Meanwhile I wrote a bit of tooling around it. But using it is not at all a must.
- keybored 2y ago0815?
- N-Krause 2y agoAn expression that, at least in Germany, means "the bare minimum/default". It originates from a German machine gun: https://de.wikipedia.org/wiki/08/15_(Redewendung) https://de.wikipedia.org/wiki/08/15_(Redewendung) (German Wikipedia, there seems to be no English version)
- keybored 2y agoThanks. That’s interesting. :-)