diff --git a/docs/contributing/MODEL_MANAGER.md b/docs/contributing/MODEL_MANAGER.md index 98e8702c8f..c12046293c 100644 --- a/docs/contributing/MODEL_MANAGER.md +++ b/docs/contributing/MODEL_MANAGER.md @@ -840,22 +840,6 @@ and directories at regular intervals when the size of the cache exceeds the value specified in Invoke's `convert_cache` configuration variable. -#### List[str]=installer.scan_directory(scan_dir: Path, install: bool) - -This method will recursively scan the directory indicated in -`scan_dir` for new models and either install them in the models -directory or register them in place, depending on the setting of -`install` (default False). - -The return value is the list of keys of the new installed/registered -models. - -#### installer.sync_to_config() - -This method synchronizes models in the models directory and autoimport -directory to those in the `ModelConfigRecordService` database. New -models are registered and orphan models are unregistered. - #### installer.start(invoker) The `start` method is called by the API intialization routines when diff --git a/docs/features/CONFIGURATION.md b/docs/features/CONFIGURATION.md index 60fa826964..41f7a3ced3 100644 --- a/docs/features/CONFIGURATION.md +++ b/docs/features/CONFIGURATION.md @@ -137,15 +137,7 @@ Most common algorithms are supported, like `md5`, `sha256`, and `sha512`. These #### Path Settings -These options set the paths of various directories and files used by -InvokeAI. Relative paths are interpreted relative to the root directory, so -if root is `/home/fred/invokeai` and the path is -`autoimport/main`, then the corresponding directory will be located at -`/home/fred/invokeai/autoimport/main`. - -Note that the autoimport directory will be searched recursively, -allowing you to organize the models into folders and subfolders in any -way you wish. +These options set the paths of various directories and files used by InvokeAI. Any user-defined paths should be absolute paths. #### Logging diff --git a/docs/features/LORAS.md b/docs/features/LORAS.md index 3c6b2d3d3f..5dcfc8bf21 100644 --- a/docs/features/LORAS.md +++ b/docs/features/LORAS.md @@ -20,10 +20,7 @@ are applied to generate imagery. LoRAs may be supplied with a simply apply their effect without being triggered. LoRAs are typically stored in .safetensors files, which are the most -secure way to store and transmit these types of weights. You may -install any number of `.safetensors` LoRA files simply by copying them -into the `autoimport/lora` directory of the corresponding InvokeAI models -directory (usually `invokeai` in your home directory). +secure way to store and transmit these types of weights. To use these when generating, open the LoRA menu item in the options panel, select the LoRAs you want to apply and ensure that they have diff --git a/docs/installation/050_INSTALLING_MODELS.md b/docs/installation/050_INSTALLING_MODELS.md index 2997bbced0..5c00a6888e 100644 --- a/docs/installation/050_INSTALLING_MODELS.md +++ b/docs/installation/050_INSTALLING_MODELS.md @@ -45,11 +45,3 @@ In this situation, you may need to provide some additional information to identi Say you have a repo ID `monster-labs/control_v1p_sd15_qrcode_monster`, and the model you want is inside the `v2` subfolder. Add `:v2` to the repo ID and use that when installing the model: `monster-labs/control_v1p_sd15_qrcode_monster:v2` - -## Autoimport - -In the InvokeAI root directory you will find an `autoimport` directory. On startup, any models in this directory will be installed and copied into the Invoke-managed models directory. - -The location of the autoimport directories are controlled by settings in `invokeai.yaml`. See [Configuration](../features/CONFIGURATION.md). - -[set up in the config file]: ../features/CONFIGURATION.md#model-marketplace-api-keys