ftp-deploy | Deploy websites over FTP with one command line | FTP library

I am trying to simply run webpack serve -c myconfig.js, but I keep getting these errors:

I am using Github as my source control, and using Github Actions as my CI/CD solution. I have a dedicated Windows Server somewhere, which accepts the published version of my repo.

I have a Github Action, which does Built, Test, Publish and Deploy (using FTP). I am not convinced with the "Deploy" idea. for example lets say my website has a huge codebase, and then FTPing everytime when we make a commit (Push) is NOT really a productive idea (i am publishing the published directory...not the Source Code to my server). Sometimes FTPing simply does not work, due to IIS Locking the files. what is the most reliable way to publish/deploy files to a remote server using Github Actions (or any other provider).

below is my sample Yaml file...

I have a custom Jekyll site which is working fine on local.

I would like to deploy my builded site to my hosting environment. Via FTP with github actions is working fine with this: https://github.com/SamKirkland/FTP-Deploy-Action

This is the FTP workflow:

As the title says, deploying to FTP server isn't working for me from a Github Action. I've tried using a couple of actions to accomplish this (FTP-Deploy and ftp-action), but FTP-Deploy just kept running with sporadic

curl: (7) Failed to connect to ftpservername.com port 21: Connection timed out

messages and ftp-action kept running without any output. Note: The server is available, I connected and transferred some files using Filezilla without any issues.

After that I tried using lftp, this is the command I used on a local Ubuntu machine

lftp -c "open -u username,password ftpservername.com; mirror -R locfolder remote/remotefolder"

and the file transfer worked, but when used in a Github Action it produced this output:

---- Connecting to ftpservername.com (123.456.789.123) port 21

mkdir `remote/remotefolder' [Connecting...]

**** Socket error (Connection timed out) - reconnecting

---- Closing control socket

---- Connecting to ftpservername.com (123.456.789.123) port 21

I tried setting both ftp:ssl-allow and ssl:verify-certificate to false, but this did not produce any results. Also, I do not have access to the server, so I can't check the server logs.

This is the workflow file:

I want to use Github actions to transfer files to a remote server via SFTP (only option for this server) when I push up to Github.

I am using this Action https://github.com/marketplace/actions/ftp-deploy

I have created a file in my repo in .github/workflows/main.yml and I have added:

How can I exclude folders or files from being uploaded to the server?

I would like to ignore the "src" folder and package.json.

I have written a small Vue app and have been looking for a nice way to automate its deployment, i.e. call lint -> test -> build -> upload to some web space (stage and /or production) (sftp). Basically a simple CI/CD pipeline.

I looked a task runners such as grunt (seems to be a bit outdated and the docs didn't help me much) and gulp (see also this answer) and also thought of defining a npm script. CI tools such as Jenkins seem to be a bit oversized with some work to setup.

The npm script would probably be the simples solution, especially as I could simply chain lint / test / build:

I have recently started working with CI using Bitbucket Pipelines. I have managed to connect using my SFTP server, creating API public & private keys and adding them to my server using SSH.

Now, when I run the build it will upload all my files to the correct folder. But I am having a problem that running a package.json command from the script "yarn build" is doing absolutely nothing.. nothing is in the root folder.

What am I missing or doing wrong? Locally everything works just fine same goes for uploading files.

My bitbucket-pipeline.yaml:

I am making edits to my JS files but my gulp task is not updating them live or writing new code. It did used to work but all of a sudden it has stopped.

I tried upgrading the gulp to version 4 but that just created more issues and didn't fix the fact the JS wasn't working.

Added jshint to see if that threw any errors but seems fine too.