file_manager: allow server to start with invalid paths
Don't raise an exeption if the config or log paths are invalid, add warnings instead. This allows the user to see what is wrong and resolve this issue. Signed-off-by: Eric Callahan <arksine.code@gmail.com>
This commit is contained in:
@@ -101,19 +101,12 @@ class FileManager:
|
||||
# Register Klippy Configuration Path
|
||||
config_path = config.get('config_path', None)
|
||||
if config_path is not None:
|
||||
ret = self.register_directory('config', config_path,
|
||||
full_access=True)
|
||||
if not ret:
|
||||
raise config.error(
|
||||
"Option 'config_path' is not a valid directory")
|
||||
self.register_directory('config', config_path, full_access=True)
|
||||
|
||||
# Register logs path
|
||||
log_path = config.get('log_path', None)
|
||||
if log_path is not None:
|
||||
ret = self.register_directory('logs', log_path)
|
||||
if not ret:
|
||||
raise config.error(
|
||||
"Option 'log_path' is not a valid directory")
|
||||
self.register_directory('logs', log_path)
|
||||
|
||||
# If gcode path is in the database, register it
|
||||
if gc_path:
|
||||
|
Reference in New Issue
Block a user