-
Notifications
You must be signed in to change notification settings - Fork 0
Environment Setup
Dotify v2.0.0+ includes a built-in environment management system that handles configuration directories, placeholder files, and dependency verification.
Run the setup wizard after installing Dotify:
dotify env setup
This creates the Dotify config directory (~/.dotify/ on Linux/macOS, %USERPROFILE%\.dotify\ on Windows) and sets up the expected folder structure.
dotify env setup --create-placeholders
Generates empty placeholder files so you know exactly what to fill in:
~/.dotify/
├── config.json ← your configuration
├── cookies.txt ← your Spotify session cookies
└── keys/
└── device.wvd ← your Widevine device key
After setup and after placing your credentials, run the doctor to verify everything is correctly configured:
dotify env doctor
The doctor checks:
- ✅ FFmpeg is installed and in
PATH - ✅ Aria2c is installed (optional but recommended)
- ✅
cookies.txtexists and is readable - ✅
device.wvdexists and is valid - ✅ mp4decrypt and MP4Box (if video downloads are intended)
Fix any issues it reports before your first download.
| File | Linux / macOS | Windows |
|---|---|---|
| Config | ~/.dotify/config.json | %USERPROFILE%.dotify\config.json |
| Cookies | ~/.dotify/cookies.txt | %USERPROFILE%.dotify\cookies.txt |
| Widevine key | ~/.dotify/keys/device.wvd | %USERPROFILE%.dotify\keys\device.wvd |
You can override all of these with command-line flags or entries in config.json. See Configuration.
Dotify v2.0.0 changed the default locations for cookies and the Widevine key. If upgrading from v1.x:
# Re-run setup to create the new directory structure
dotify env setup
Move your existing credentials to the new locations
mv cookies.txt ~/.dotify/cookies.txt
mv device.wvd ~/.dotify/keys/device.wvd
Verify everything is in order
dotify env doctor
- Authentication — How to obtain your cookies and Widevine key
-
Configuration — Full
config.jsonreference