Thanks for the reply. I'll give that a read, looks like some good 
information there. 

Can you tell me if this would be a correct description?

Locally, I've got my dev folder. On the server, I set up a git repository 
in the folder that contains, as well as another repository 
in the folder that contains the files.
This means I'll have 3 repos. I can push commits to the test repo, then 
when I'm happy with it, I can push them to the live site?
Since Coda allows just one server to be defined (I do hope they change 
that...) then perhaps I should connect it to the test domain, and then use 
the GitHub app to push the files to the main domain when they're good to 
go? I figure the files always come from my local, and they don't travel 
from the test domain to the live domain when ready.

On Saturday, May 26, 2012 4:57:15 AM UTC-4, Serge Matveenko wrote:
> On Sat, May 26, 2012 at 4:08 AM, Heronymo Allen <> 
> wrote: 
> It's up to you how do you want to setup your server environment to 
> deploy your code. You may setup your webserver directory as another 
> git repo clone and use 'git pull' to deploy your code from central 
> repo (like github). It's fine for development or testing server. But 
> its usually better to use special deployment mechanisms for production 
> servers if you need to build or test your code before deploying. 
> I advise you to read 

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To view this discussion on the web visit
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to