-
Notifications
You must be signed in to change notification settings - Fork 380
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Action is very slow as compared to other #28
Comments
Hey, thanks for bringing this to my attention. I'll try to help debug the issue. I followed a very similar workflow for years (using FileZilla to keep my local and source control in sync). That's the exact use case for this github action :) On another note the other deployment action you reference is actually just a fork of this one from a few months ago, the only real differences are mine is up to date with SFTP support. If you deploy via FTP instead I expect the deployment times to be similar. |
Dear I have local development server. I do complete development and testing on local server. once its ready for the production then I push changes to live production server. Here is the raw log: 2019-11-23T21:31:05.7980790Z ##[section]Starting: Request a runner to run this job |
And one more thing, I am using FTP with it. the title that is used in those test cases "Publish Website Over SFTP" is just the default and while associating action, i didn't modify the title. |
Here is my .yml file for this Action
|
Can you add the following as ARGS: |
Because .git folder not excluded (there's a lot of things inside it) ? |
V3 will now only publish different files. Breaking change: v3 will only publish tracked (committed) files by default. If your file isn't in source control you will have to add it |
Hi,
I don't if it makes sense to ask this,
I tested SamKirkland/FTP-Deploy-Action and found that its very slow. I just tested it with upload a single file to server. It takes more than 2 minutes to complete the action.
Then I tested https://github.com/sebastianpopp/ftp-action , and that worked fast comparatively.
Attached is the screenshot of SamKirkland/FTP-Deploy-Action with the title "Publish Website over SFTP"
and sebastianpopp/ftp-action with the title "Deploy via ftp"
I am still curious and feel that SamKirkland action may the one to go with,
but I can't wait 2 minutes each time.
Before using these actions I used to commit and push my changes to github and then use the another FTP software like FileZilla to upload my files to the server,
Now I want it to be a single step, when I push changes to github, they should be automatically uploaded to server too.
But am I using it the right way? because most of the times there are less than 10 files mostly 2 to 3 files to upload to server.
Sorry if I haven't explained the issue clearly.
The text was updated successfully, but these errors were encountered: