Automatically deploy local files to server on change? (Currently just using filezilla)
Can anyone suggest me a tool to automatically push my local changes to like an ftp file? I'm using Tailwind with WordPress and my client is telling me to work on the files that are uploaded in the server via FTP, and we are only using FileZilla, but I need to build my tailwind locally as well.
Any suggestions/tools to automate this, or make the workflow better?
13 Replies
winscp is great for that on windows. I can not say for other OS
You can configure your editor in FileZilla, when you open a file for edit from FileZilla, it will upload the updated file on each local save. Just need to tell FileZilla you’re done editing so it will stop monitoring.
the issue with both those solutions is that it won't automatically push the built files
the real question is, why do you need to update the remote server so frequently @Nibelung Valesti ? Usually, you'd develop your changes locally on a local copy, then commit your changes to git and deploy to the prod server once you're done.
in fact, github (and other git repo providers like gitlab and atlassian) have tooling that lets you run deploys when certain conditions are met (usually a merge to a specific branch such as
main)@Jochem winscp will definitely push built files (or any files you point it to. All files that change are immediately copied)
the real question is, why do you need to update the remote server so frequentlyI needed this very often, and others need too. Your process is different and that is fine.
winscp only does that to files you open to edit from inside winscp in my experience, guess that must've changed
the concern I have is that editing a live site is a terrible habit to get into
you should never live-edit the prod site, especially not with an automated process
that is when you edit remote files with winscp
you can open folder side by side and turn on sync. it will watch files for changes and copy as they change
you should never live-edit the prod site, especially not with an automated processfair, point, but it depends 🙂 ... I do this often to test new version in a separate folder so it is on prod, can be tested, but not really published to all users ... this is much more productive for troubleshooting difficult issues than waitng for CD/CI for ages.
ideally, and I realize this isn't always possible, you should have a separate staging server for that. But what is possible, is to just test your stuff on your local dev machine. The environment should be similar enough that you can test 99% of backend issues locally, and definitely 100% of frontend issues
yes, ideally 🙂 ... @Nibelung Valesti was asking for a tool that can sync, although such advice on structuring projects is valuable, does not answer the question asked here 🙂
I have saved countles hours, by intentionally skipping the ideal setup for specific issues that need to be solved fast and were too difficult to reproduce on staging
My experience with both tools is that they only sync actively opened files, I was unaware of the option to sync entire folders. Also, a lot of the time beginners will ask how to do a certain thing, when the process they're using is unnecessarily complicated. Or they will ask how to solve a tiny subsection of a more complex problem that is better solved using a different solution. Asking for an expansion of their workflow to better solve the issue they're facing is a totally valid strategy
I agree, your input here is good, we should not spam much more, to not drown out the original question 🙂
Has OP offered any response to the suggestions thus far? I’m checking but all I can find is discussion between others. Has this been considered ’solved’?
this is the last message OP sent on the server, so no idea
Let’s hope they come back to catch up on this, and contribute some clarity or mention that this helped them to any degree.