I’ll be honest…
I have not had to make a config edit on my machine since I edited the pulloff values on initial squaring 9-ish months ago.
At the time, I used your first option.
Today, I would probably connect remotely, download the file, edit, then re-upload.
I have never used the web installer for it. Other than testing I do all the edits from the GUI and save then actually save. Current and pulloff edits, accel, and top speed all from the GUI. Edit and test super fast.
Same
The web installer has always been quirky for me so I don’t trust it outside of basic updates (which I don’t do anymore either).
Usually, I do it in the WebUI and use the save macro.
Then there’s my Z-level thing that calculates and sets the offsets via gcode.
Warning: side tangent below…
I’m wondering if it makes sense to change the Save macro to do a backup of the file. I haven’t tested this, but I think something like this could be done.
$LocalFS/Rename=config.yaml>config_backup.yaml
$CD=config.yaml
Then you could also have a restore macro if you wanted.
$LocalFS/Delete=config.yaml
$LocalFS/Rename=config_backup.yaml>config.yaml
Or some variation where you have a known good config file to restore from.
I also like the $LocalFS/Backup backup command that backs up everything on Flash to a localfs folder on SD.
Ref:
I could almost vote with this one:
Edit on local dev box so git or similar change control can be used. Only upload snapshot to ESP32 via FluidNC Web Installer, the ‘truth’ lives on local PC/Mac.
…As opposed to this one:
Something else
because I’m most often (almost always) editing on laptop and uploading, and I do use VSCode to do that, but I don’t yet do any kind of versioning or git related control.
And I like having a backup copy on my hard drive of my config files.
I wrote a PowerShell script that I run periodically to download all the files on Flash to my computer. I haven’t gotten around to keeping them in Git.