From: Luciano Rocha <luciano@eurotux.com>
To: Marcus <prima@wordit.com>
Cc: git@vger.kernel.org
Subject: Re: Invalid path on new Git installation
Date: Tue, 27 May 2008 16:14:06 +0100 [thread overview]
Message-ID: <20080527151406.GA16378@bit.office.eurotux.com> (raw)
In-Reply-To: <8345bd80805270758j1315234bwf3b16607c95c9620@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
On Tue, May 27, 2008 at 03:58:05PM +0100, Marcus wrote:
> Can anybody help me with defining a valid path to a Git repo on a new
> installation?
> I just built Git on a webserver (a VPS so I have root access). When I
> try clone or push I get this error:
>
> fatal: '/git/watchsite.git': unable to chdir or not a git archive
> fatal: The remote end hung up unexpectedly
> fetch-pack from 'ssh://me@mydomain.com/git/projectname.git' failed.
>
> Why this when I can use wget on this path:
> wget mydomain.com/git/projectname.git/file.html
> The above successfully downloads the file, so the path is valid, right?
ssh://me@mydomain.com/git/projectname.git means the folder
/git/projectname.git in host mydomain.com
http://mydomain.com/git/projectname.git/file.html means whatever folder
your webserver is mapping /git/projectname.git to. Usually,
/var/www/html/git/projectname.git.
> I also did "git init" on the remote repo (not sure if that's necessary?).
What is the correct path on the remote? Note that ssh://host/dir isn't
the same as host:dir (both are acceptable), as the latter means ~me/dir,
while the former means /dir.
You could switch to the me@host:path location, or add a ~/:
ssh://me@host/~/dir
--
Luciano Rocha <luciano@eurotux.com>
Eurotux Informática, S.A. <http://www.eurotux.com/>
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-05-27 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 14:58 Invalid path on new Git installation Marcus
2008-05-27 15:14 ` Luciano Rocha [this message]
2008-05-27 15:42 ` Marcus
2008-05-27 15:51 ` Johannes Sixt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080527151406.GA16378@bit.office.eurotux.com \
--to=luciano@eurotux.com \
--cc=git@vger.kernel.org \
--cc=prima@wordit.com \
/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.
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 NNTP newsgroup(s).