by Tdarcos » Sun Dec 08, 2019 7:56 am
Now, if Jonsey can have whichever port GIT uses opened to traffic on his server I wouldn't mind using it as a repository, although since Github developed Atom, I don't know if it supports external repositories other than Github. If that is the case, it means I have to use an external Git client (like Tortoise Git), instead of Atom's built-in client.
Another possibility: open the port for SMB traffic and put a Samba daemon on it. Then the server can look, for all intents and purposes, as a Windows machine (or Windows Share). I did that with my Buffalo NAS when it was on my router at home as a intranet device. I referenced it as \\buffalo, or assigned a drive letter to any subdirectory and it looked and worked just like a SUBSTed drive.
For some reason it does not work here, or rather, it no longer works, as it worked perfectly for about a day and a half maybe six weks ago and then just stopped working. I'm not sure why.
Secondary side note: I need to check on this, but if the communication methods are documented such that they can all use the same port, a single port number can be used, otherwise the specific ports for Git, Mercurial (Hg), SVN and CVS all need to be registered with IETF as a known TCP port (hell, even DOOM has port 666 registered wuth IETF, it should not be too difficult) and if there is not a definitive reference to the technical specification for the protocols, it (or they) need(s) to be made and published.
Now, if Jonsey can have whichever port GIT uses opened to traffic on his server I wouldn't mind using it as a repository, although since Github developed Atom, I don't know if it supports external repositories [i]other[/i] than Github. If that is the case, it means I have to use an external Git client (like Tortoise Git), instead of Atom's built-in client.
Another possibility: open the port for SMB traffic and put a Samba daemon on it. Then the server can look, for all intents and purposes, as a Windows machine (or Windows Share). I did that with my Buffalo NAS when it was on my router at home as a intranet device. I referenced it as \\buffalo, or assigned a drive letter to any subdirectory and it looked and worked just like a SUBSTed drive.
For some reason it does not work here, or rather, it no longer works, as it worked perfectly for about a day and a half maybe six weks ago and then just stopped working. I'm not sure why.
Secondary side note: I need to check on this, but if the communication methods are documented such that they can all use the same port, a single port number can be used, otherwise the specific ports for Git, Mercurial (Hg), SVN and CVS all need to be registered with IETF as a known TCP port (hell, even DOOM has port 666 registered wuth IETF, it should not be too difficult) and if there is not a definitive reference to the technical specification for the protocols, it (or they) need(s) to be made and published.