The name of your GitHub action which is shown in the repositories action tab on GitHub. Only start this action, when changes where pushed to the `dist/` directory (this is the default build folder for Vue CLI) This is what my configuration looks like: So, how can you set up this FTP-Deploy-Action? You simply have to create a configuration file called ftp-deploy.yaml under your-repo/.github/workflows/.

Lean back and let the GitHub FTP-Deploy-Action do the rest.

use Git Submodules and uploading the whole project on each build would take an incredible amount of time. And this is, where Git-ftp really pays off: It can upload only those files, that changed since the last upload! This is extremely useful, especially for projects with a lot of files.

⏫ Upload new build files to production serverĮspecially the last two points always bothered me, because most of the time I was pushing some smaller changes that only affected a few files and I still deleted and reuploaded the whole application.

❌ Delete old build files from production server.

🔁 Create new build files optimized for production using vue-cli-service build.

✅ Commit these changes to the repository.

I'm mostly creating Vue.js applications with the Vue CLI - so my normal workflow always looked like this:

It's the FTP-Deploy-Action by Sam Kirkland which utilizes Git-ftp. However, I found an awesome GitHub action to publish files automatically via FTP to my server on build. Or after doing web development for more than 15 years now, I was just too lazy to change something 😅

Maybe I just don't wanted to give up too much control over the files that I push to production. I'm not really sure if it's a thing to be ashamed of today, but I'm still pushing build files of most of my personal open source projects manually via good ol' FTP to my server. Thanks to DEVs GitHub Actions Hackathon, I'm finally tackling this topic. Since their release, GitHub actions are on my long-term todo list for increasing automation of my workflows.

Netbeans ftps