Re: Can Git work for us if we are remotely hosted?
- From
Avery Pennarun <apenwarr@gmail.com>
- Date
- Aug 12, 2010, 18:08 UTC
- Message-ID
- <AANLkTin_qwk9FxkhVkvfQyc0AFXOKfKX-b+BzgXas_CW@mail.gmail.com>
- In-Reply-To
- <AANLkTimxYgAwWWoJCxsQ_Rr-eGfWJWoL4Qscw3FBYk9_@mail.gmail.com>
On Thu, Aug 12, 2010 at 1:59 PM, Sultan Shakir <sshakirflhosp@gmail.com> wrote:
Show 15 quoted lines
> On Wed, Aug 11, 2010 at 7:06 PM, Avery Pennarun <apenwarr@gmail.com> wrote: >> On Wed, Aug 11, 2010 at 6:51 PM, Sultan Shakir <sshakirflhosp@gmail.com> wrote: >>> I've been trying to wrap my brain around how I can get Git to work at >>> my organization. The issue is that nearly all of our programs and >>> their IDE are remotely hosted. This means that to even work on a file >>> we have to connect to the network in order to use the application that >>> we code in. We do have access to the backend where the files are >>> stored though. How can we use Git in this situation without setting >>> up another server? >> >> If you want, you could just push/pull to a git repo in a file share on >> one of your existing fileservers. > > Please excuse my ignorance. What do you mean by a "file share" and > "existing fileservers"?
You said you have "access to the backend where the files are stored." Surely that's on a fileserver, like a Windows file sharing service or a samba server or an NFS server, right? Any of those are capable of holding a git repository.
git is much faster if you store files on your local machine as much as possible. But you can push/pull from a shared repository on a samba/NFS/whatever server and that generally won't be a performance problem.
Have fun,
Avery