git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: H <agents@meddatainc.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Location limits on development, staging and production environments
Date: Mon, 29 Jan 2018 20:08:54 +0100	[thread overview]
Message-ID: <baf15388-adb4-ddce-889f-3e71b1574044@meddatainc.com> (raw)

I am a newcomer to git looking to set up a web development environment where individual computers are used for development, the development.git, staging.git and production.git repositories are stored on an external server reachable by password-less ssh and the staging and production websites are on yet another server, also reachable by password-less ssh from the git-server (and the development machines).

Locating the three git repositories on an external server works fine but I have not been able to have the staging and production deployment files on another server. I believe this is what is referred by GIT_WORK_TREE and based on what I found on the web I created a post-receive hook of staging.git with the two lines:

#!/bin/sh
GIT_WORK_TREE=user@1.2.3.4:/var/www/html/dev.whatever git checkout -f master

I believe this should deploy the files from the development work tree.

The above, however, fails. Should it work? I am running git 1.7.1 on CentOS 6.


             reply	other threads:[~2018-01-29 19:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 19:08 H [this message]
2018-01-29 21:02 ` Location limits on development, staging and production environments Bryan Turner
2018-01-30 14:48   ` H
2018-01-31 16:54     ` H

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=baf15388-adb4-ddce-889f-3e71b1574044@meddatainc.com \
    --to=agents@meddatainc.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).