Following the quick start guide...
podkit sync --dry-run
returns:
No collections configured to sync.
Add collections to your config file:
/Users/myfolder/.config/podkit/config.toml
Example:
[music.main]
path = "/path/to/music"
Or set via environment variable:
PODKIT_MUSIC_PATH=/path/to/music
with a correctly set path in the config. The weird issue is if you have a malformed path (e.g. path = /Users/myname/Music instead of path="/Users/myfolder/Music") it will throw an invalid TOML document error.
Similar issue with
podkit device clear --dry-run
returning:
No default device set. Specify a name or set a default with: podkit device default -d <name>
In order to proceed with the quickstart guide I needed to use the -d flag in podkit device clear and environment variables for podkit sync
Another weird issue is that PODKIT_MUSIC_PATH=/Users/myfolder/Music podkit sync works despite the fact that I did not set the device flag manually.
Following the quick start guide...
podkit sync --dry-runreturns:
with a correctly set path in the config. The weird issue is if you have a malformed path (e.g.
path = /Users/myname/Musicinstead ofpath="/Users/myfolder/Music") it will throw an invalid TOML document error.Similar issue with
podkit device clear --dry-runreturning:
No default device set. Specify a name or set a default with: podkit device default -d <name>In order to proceed with the quickstart guide I needed to use the -d flag in
podkit device clearand environment variables forpodkit syncAnother weird issue is that
PODKIT_MUSIC_PATH=/Users/myfolder/Music podkit syncworks despite the fact that I did not set the device flag manually.