How to maintain a project built in Gulp?

Question

Sass

So, I recently decided to start using gulp to build projects, set everything up as it should. By the way, it was the use of SASS and JADE
preprocessors that prompted me to take this step . It has become very convenient to use them, and launch the watcher with one command. But then I have a question, what next? So I finished the layout, tied it to cms, let's say modx or bitrix. Ok, scss files, I can save next to the same css . And if necessary, download them from the server, and make changes, and update the result on the server. But in the end, I only use gulp during primary development...



And after all I think there are any decisions allowing to carry out and support?
Can someone help me with this issue so that I can fully understand it?
PS By the way, maybe I can help someone, you never know. At first I had problems with SCSS and imports, when saving files that were imported into the main file, the watcher cursed that he could not find the file that I saved, and I had to re-save the main one for the changes to take effect.
I found an alternative component for building scss, gulp-ruby-sass instead of gulp-sass after installation everything works with a bang.

Answer 1

I found an alternative component for building scss, gulp-ruby-sass instead of gulp-sass after installation everything works with a bang.

Now everything works several times slower. I advise you to figure out the paths and return gulp-sass.
On the topic of the question - you can upload the configs to the server, if it's more convenient for you and download if necessary.
Sense to lift remotely - I do not see.