git-ftp | Upload by FTP the modified files from your last commit | FTP library

This is what I currently use, which I found from The World According to Mike Blog.

This uses ncftp which allows you to upload files via ftp easily.

The README for git-ftp/git-ftp includes:

Windows and OS X: I am very limited in testing on Windows and OS X. Thanks for helping me out fixing bugs on these platforms.

Still, on Windows, you can simply copy the git-ftp in D:\Program Files\Git\bin (you don't even have to be in a bash): any git-xxx file which is in the %PATH% would be executed by git xxx

Check first in a regular CMD (with the appropriate PATH) if git ftp is recognized. (Assuming D:\Program Files\Git\bin is in your %PATH%)

I found the solution. The only command which requires the modification is the git-ftp command. However, I also found that the export command doesn't have anything to do here, so I removed it and the command still worked as I require.

Here how it goes:

you have angular cli installed in your project, the better and faster way would be to use local ng installation to build your project. just add an npm script and call build through npm like this:

I finally solved it pressing the "Clear Runner Caches" button and running it again.

It turns out that my git ftp command --user has been accidentally replace to --auth, here is the error command:

My current solution is as follows.

I've skipped the use of pipelines and removed the exclusion of the ./vendor folder from my .gitignore file. I've created a subdomain with git support, allowing me to pull and deploy my development branch. Did the same for my production/master branch.

The first thing to note is that git aliases only work with shell commands when prefixed with a bang (exclamation mark). I'm not using git-ftp so I can't test your precise command, but I used git remote show origin instead because it's very verbose on one of my repos. I found the following git alias worked fine: sh = "!git remote show origin | awk 'NR<7'" I therefore expect this git alias to be a solution for you:

For some reason somebody deleted the .git-ftp.log file from the server.

So, I re-initialize git-ftp.log file again.

Steps:

1. go to the "Commits" page in your bitbucket repository.
2. Choose the latest commit, then on the right hand side of that page you'll find a "Run pipeline" link with which you can manually trigger pipelines.
3. Select "custom: init" and wait until the pipeline is finished.