Config Installation

When installed, the following values are set by default in the config file

[SETTINGS]
WATCH=/downloads/temp
TARGET=/downloads/processed
IGNORED_TERMS=Annual
IGNORED_EXTENSIONS=.crdownload,.torrent,.tmp,.mega,.rar,.bak
IGNORED_FILES=cover.jpg,cvinfo,.DS_Store
READ_SUBDIRECTORIES=True
CONVERT_SUBDIRECTORIES=True
AUTOCONVERT=True
MOVE_DIRECTORY=True

During installation (see Quickstart),the /config is mapped to a separate docker volume to ensure that config settings are persisted on updates.

volumes:
  - 'config-volume:/config'

/config is not optional

Your database lives here too, not just config.ini. If /config isn't mapped, the database sits in the container's writable layer and is destroyed the next time the container is recreated — including on every image update. CLU flags this as a Storage: overlay alert on the Database tab.

Map it to a named Docker volume or a local path. Not a network share — see Database Recovery.

First Install: On the first install with new config settings, visit the config page, ensure everything is configured as desired.

Save your Config settings
Click the Restart App button

Explanation of Values

Parameter	Function
`WATCH`	Path/Folder to watch if folder monitoring enabled
`TARGET`	Path/Folder to where watched files are moved after processing
`INGNORED_TERMS`	Option for Missing Issue Check to not look for issues.
`IGNORED_EXTENSIONS`	File types that will be ignored by Missing Issue Check
`IGNORED_FILES`	Files here will not show when browsing file structure in the app.
`READ_SUBDIRECTORIES`	Read sub-directories when folder monitoring enabled
`CONVERT_SUBDIRECTORIES`	Enable traversing sub-directories when converting CBR to CBZ
`AUTOCONVERT`	Auto-convert files to CBZ as they are downloaded with folder monitoring enabled
`XML_YEAR`	Move sub-directories when moving files in folder monitoring
`GCD_METADATA_LANGUAGES`	When using GCD Metadata, CLU will search for metadata on these languages

Startup

If your container seems to hang on start

It probably isn't hanging. Before v6.5, a first run or a large-library start could sit completely silent for up to two minutes, which is indistinguishable from a container that never started — so people killed it and tried again.

As of v6.5 the container reports what it's doing while it starts. Watch the log:

docker logs -f clu

Ownership passes over /cache and /config are the slow part on a large install, and they are now timed and reported individually, so you can see which one you're waiting on.

The startup database backup also no longer blocks startup — it runs in the background.