config_path requirement should not be that it is in home or a subdirectory of home about moonraker HOT 6 CLOSED

Check out this previous issue: #45

from moonraker.

Indeed this is similar to #45. I would be willing to make an exception if this functionality is necessary to package moonraker, however I would require more specificity than any subdirectory in /etc. For example, I am willing to allow /etc/moonraker as an exception.

from moonraker.

@Arksine feel free to pick a sub directory, - i think /etc/moonraker sounds reasonable.

from moonraker.

Ok, commit 9a309ff allows directories within /etc/moonraker. You can choose /etc/moonraker itself if you want, however I would recommend /etc/moonraker/config for the configuration files, that way you could specify /etc/moonraker/gcode_files for the gcode files if you like. That is up to you though. You simply need to make sure moonraker has permisssion to read/write to this directory.

from moonraker.

@Arksine Thank you for your fast implementation

from moonraker.

Since multiple people have requested a less restrictive directory location I have gone ahead and removed the restriction that folders be located in the HOME directory. Moonraker will check its permissions on the directory, as long as it has them it will allow it. The only exception is the system root, which is always prohibited.

from moonraker.