Composer taking a very long time

Hi,

I’m assuming my setup is wrong, but my repo is taking around 25 minutes on each push to upload. I’m assuming this is to do with composer?

on: push
name: Publish Website
jobs:
  build:
    name: Build and deploy API
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2.1.0
        with:
          fetch-depth: 2
      - uses: shivammathur/setup-php@v2
        with:
          php-version: '7.3'
          tools: composer
      - run: composer install
      - name: Deploy website with FTP
        uses: SamKirkland/FTP-Deploy-Action@3.1.0
        with:
          ftp-server: ${{ secrets.FTP_ADDRESS }}
          ftp-username: ${{ secrets.FTP_UNAME }}
          ftp-password: ${{ secrets.FTP_PWORD }}
          local-dir: ./

Couldn’t find any info anywhere.

Thanks, Tom

[SamKirkland]

This action is dependent on github version tracking to determine which files to upload. Untracked files are re-uploaded every time because the ftp protocol has no way of diffing two files (newer protocols give you a file hash and then its as simple as comparing hashes).

You have a few options here:

1. Switch to a protocol that supports hashing - namely SSH & rsync. You can then use a rsync deploy action to get a true diff-only upload
2. If you must use FTP you can use the older v2 version of this action - note the parameter names are different. It supports “smart diffing” which tries to only upload different files, I removed this feature in v3 because it can be incorrect if the file was changed but the file size remains the same.
3. Wait weeks/months until I get a working solution with this action. I’ve been working on a version that uploads a hash for every file so all files only need to be deployed on the initial run.

[SamKirkland]

I’m assuming the 4th option is simply to track /vendor and drop from action.

Yep! I forgot about that one 😃