4 ms·
I would think git's distributed nature would make this a lesser issue. You would just have to set up another remote target and push/pull from that (say on AWS o
by sureshv 12y ago
I would think git's distributed nature would make this a lesser issue. You would just have to set up another remote target and push/pull from that (say on AWS or some other provider).
- e12e 12y agoSure. But not having access to the tickets database might cripple a team pretty badly. One reason I'm still toying with the idea of trying fossil[1] "for real" and/or find/make a tool that distributes issues within mercurial/git like http://www.bugseverywhere.org/ http://www.bugseverywhere.org/ Note-to-self: looks like hattawiki might be a nice companion on the path to "distributed everything": http://hatta-wiki.org/Install http://hatta-wiki.org/Install [1] https://www.fossil-scm.org/ https://www.fossil-scm.org/
- pedrocr 12y agoFor a distributed wiki try gollum. It's the wiki engine behind the github wikis and it's basically a wiki where the database is a git repo. I love it for family use. I can put up a nice web interface for everyone else to edit and yet I use git push/pull and my normal text editor. Works great.