From the command line

WP-CLI is a convenience, never a requirement — everything is available in the admin.

wp nimblecache status
wp nimblecache purge
wp nimblecache purge https://example.com/about/
wp nimblecache preload --all
wp nimblecache repair

status also prints how many times the whole cache was cleared in the last 24 hours and the last five times, newest first, with the reason, who and how many pages, as the Dashboard's Clearing Log shows them.

purge, for one address or for everything, also asks the cache in front straight away (see Integrations), and says which caches were asked and names one that could not be reached or answered with an error, as a warning, so a deploy script can see it. Without an address it clears that cache whole, as Clear the whole cache does.

repair reinstalls the drop-in and rewrites the settings file, which is what you want after moving a site to a new path. The settings file lives in the cache folder and the drop-in in wp-content, so one can be written while the other is refused. When either cannot be written, repair stops with an error that says where, rather than reporting both as rewritten.

Changing wp-config.php never leaves a copy of it behind: the new version is written beside it and swapped in at once. Versions before 1.1.27 kept a wp-config.php.nimblecache-backup, which is deleted automatically.