StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>The <a href="https://github.com/git-ftp/git-ftp" rel="nofollow noreferrer">git-ftp</a> script might be what you are looking for. It takes the changes local git repository and syncs it to a remote git repo over ftp.</p> <p>I used it by hosting a git repo created using the <a href="http://www.bluishcoder.co.nz/2007/09/how-to-publish-git-repository.html" rel="nofollow noreferrer">--bare option</a>. Put it on my ftp server.</p> <p>than ran ./git-ftp.py. It prompts for ftp username, password, ftp host, local git repo path, remote git repo path (the location of the bare repository).</p> <p>Then it connects to the ftp git repo and then sends the diffs alone. (it uses the git-python library to get that info needed).</p> <p>The script has few issues. It seems to be prompting for username details always and I had to comment out line 68. </p> <pre><code>#ftp.voidcmd('SITE CHMOD 755 ' + node.name). </code></pre> <p>But those things can be easily fixed.</p> <p><strong>Alternative</strong></p> <p>If you are on a nix platform an alternative is to use <a href="http://curlftpfs.sourceforge.net/" rel="nofollow noreferrer">curlftpfs</a>. It will mount your ftp account as a device directory from which you can do all normal git operations (push, pull). Of course this solution ain't git specific.</p> <p>You need to use the bare option as mentioned above on the repo shared on FTP as well as run <a href="http://www.kernel.org/pub/software/scm/git/docs/git-update-server-info.html" rel="nofollow noreferrer">git update-server-info</a> within the repo before sharing it over FTP.</p> <p><em>Caution</em>: This isn't a good idea if you plan to have multiple users to write to your git repo. As FTP has no mechanism to LOCK access. You will end up with a corrupt repo. Test before taking to production.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload