Is your feature request related to a problem? Please describe.
Ex. I'm always frustrated when...
My students change the configuration,,, I work on a school and we have 7 printers all of them with duet3 on SBC mode running rrf 3.4.6. Many time happens a student changes config.g o r some toher files.
Describe the solution you propose.
I like the config files to be reachable and seen by students beucause we practise using different configs or see what some of themn does or not.
BUT i would like when Im not there or in some "production" machines not meant to be changed on their config, the config is protected from being changed. Some protection system could be good, apart fro the simple password protection that can be easily seen on the config.g once it is unlocked
Describe alternatives you've considered
I tried and I would like this method to work but it doesnt: using ssh I tried to change config.g file permissions. I changed ownership and group to root (not a good practise I know but was just a test). The through the web interface I edited the file and then aved it... and it was possible!. Since the file was owned by root and in the root group with read permission only for everybody else, I though the user dsf was going to be able to read it but not edited (the web server is also running under this user dsf)
Can anyone give a possible clue how to do this?.
Objective is to lock any possible edition of config files but still be able to see their content.
Is your feature request related to a problem? Please describe.
Ex. I'm always frustrated when... My students change the configuration,,, I work on a school and we have 7 printers all of them with duet3 on SBC mode running rrf 3.4.6. Many time happens a student changes config.g o r some toher files.
Describe the solution you propose.
I like the config files to be reachable and seen by students beucause we practise using different configs or see what some of themn does or not. BUT i would like when Im not there or in some "production" machines not meant to be changed on their config, the config is protected from being changed. Some protection system could be good, apart fro the simple password protection that can be easily seen on the config.g once it is unlocked
Describe alternatives you've considered
I tried and I would like this method to work but it doesnt: using ssh I tried to change config.g file permissions. I changed ownership and group to root (not a good practise I know but was just a test). The through the web interface I edited the file and then aved it... and it was possible!. Since the file was owned by root and in the root group with read permission only for everybody else, I though the user dsf was going to be able to read it but not edited (the web server is also running under this user dsf)
Can anyone give a possible clue how to do this?.
Objective is to lock any possible edition of config files but still be able to see their content.
Provide any additional context or information.
Ex. Photos, mockups, etc.