Auto upload .css file generated by LESS compiler

[Nicolas33259498hiyj]

Hi,

I have "auto upload" activated on save but when I save a .less file and it's compiled, it won't upload the .css file and I have to do it manualy. Is it possible to fix that?

Thanks,

Nicolas

[L e n a]

By enabling upload on save on DW, the only thing you'll be doing, at least in your case, is uploading the .less source to the server...

Unfortunately, before DW went into minimal maintenance, the development teams didn't have time to finalize this feature.

Well, nothing's lost, but you'll have to develop this solution by yourself, based on Node.js. So once Node is running on your local machine :

1.  Monitor changes in your local files, by using tool as gulp, grunt, nodemon, watch...
2.  Ask to compile your .less files... using packages as less, node-sass, gulp-less...
3.  Transfer files to server (not obly CSS, but also JS, HTML/PHP, .htaccess, .jpg, webp...all what you need) ... based on packages as gulp-rsync, grunt-rsync... depending on your initial tool.
4. Then once it's done, reload all connected devices... browser-sync can be piloted by the Gulp plugin gulp-browser-sync, or with grunt-browser-sync if you wen grunt.

However, if you run that way, I'd advise you to disable compilation .less managed by DW, as well as upload on save... you'll avoid any artifacts that could become counterproductive.

[Nancy OShea]

I wonder how many Dreamweaver users have brought Node.js into their workflow. 

• <5%
• 10%
• 25%
• >25%

[L e n a]

I wonder how many Dreamweaver users have brought Node.js into their workflow. 

By Nancy OShea

Hmm... I'd say 100%... in fact DW has been integrating Node.js for several versions already...

No, more seriously, it doesn't matter who, or how many of us, use Node.js in their workflow, for one thing, before I knew about chocolate cakes, I always thought dry cakes were the only cakes there were... and for another... it's never too late to start. Don't you think ?

[Nancy OShea]

It's not what I think that matters. 

You can lead horses to water.  If they drink it or not remains to be seen.

Recent forum activity suggests to me that DW users want to keep doing things the way they always have.  What they can't do themselves, the software should intuitively do it for them.  You & I know that being a web developer requires a lot more from us than just pressing buttons.

[Nancy OShea]

Dreamweaver is in minimal maintainence status.  No new features will be added except essential security updates.

I manually select Scripts, Styles and Media folders from my Files Panel (F8) and hit the UP arrow to ensure they are transfered to my server.

[L e n a]

Actually, I understand @Nicolas33259498hiyj 's productivity concerns. It's often frustrating to have to do, say, a Ctrl Shift U, just to upload a file, and then an F5 to refresh the browser just to check real-time refinement adaptations live on the production site.

So having to add a select a generated file in the file panel, just because the auto upload doesn't take it into account, quickly becomes restrictive.
That's why I've suggested opening up to a grunt/gulp solution, depending on the availability of packages that could be added to the final needs (image conversion, uglify script, concat javascript, and so on...).