Skip to content

Commit 0fc6c2c

Browse files
committed
chore: README updated
1 parent f09b190 commit 0fc6c2c

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ MusicBee to Navidrome Sync allows you to:
3333
4. Click on **Preview**, MusicBee will scan your entire collection, so it can take some time depending on its size. Once it's done, click on **Export** and name your file `MusicBee_Export.csv`
3434
5. **Shutdown Navidrome properly**. This is mandatory to avoid backing up its database while there's still operations going on with it.
3535
6. Once Navidrome is shut down, backup its database file, `navidrome.db`. Its location is usually in navidrome `/data` folder. You can back up it either by copying it or with sqlite3 CLI if installed (`sqlite3 <path to original file> ".timeout 30000" ".backup <path to backup file>"` for instance). If you back it up by copying, just copy `navidrome.db-shm` or `navidrome.db-wal` too if present, just for precaution.
36-
7. Download [this repository latest release](https://github.com/rombat/musicbee-navidrome-sync/releases) .exe
36+
7. Download [this repository latest release](https://github.com/rombat/musicbee-navidrome-sync/releases/latest) .exe
3737
8. Copy `navidrome.db` and `MusicBee_Export.csv` in the same folder as this .exe (or you can provide pathes with CLI, see **Commands** below)
3838
9. Run the command you want to run (, see **Commands** below), your database file will be updated
3939
10. Once it's done, go back to navidrome `/data` folder where you found `navidrome.db` and overwrite it with the updated one. Remove any remaining `navidrome.db-shm` or `navidrome.db-wal` or you will probably get some errors on navidrome startup.
@@ -47,28 +47,28 @@ For instance, `musicbee-navidrome-sync.exe fullSync -h`
4747

4848
### fullSync
4949

50-
Sync playcounts, track ratings, loved tracks and last played date from MusicBee DB to Navidrome DB. Run on tracks first, then update albums and artists accordingly.
50+
Syncs playcounts, track ratings, loved tracks and last played date from MusicBee DB to Navidrome DB. Runs on tracks first, then updates albums and artists accordingly.
5151

5252
#### Available options :
5353

54-
* `-f, --first` : run sync for the first time: **add** MusicBee playcount to Navidrome playcount. If not used, playcount will be updated only if it greater than Navidrome's one (see [Notes](#-notes)).
54+
* `-f, --first` : runs sync for the first time: **add** MusicBee playcount to Navidrome playcount. If not used, playcount will be updated only if greater than Navidrome's one (see [Notes](#-notes)).
5555
* `--csv <path>` : MusicBee CSV source file path. By default if not passed, will look for a file named `MusicBee_Export.csv` in the same folder as `musicbee-navidrome-sync.exe`
5656

5757
### albumsSync
5858

59-
Update all albums playcounts and ratings based on existing Navidrome DB.
59+
Updates all albums playcounts and ratings based on existing Navidrome DB.
6060

6161
### artistsSync
6262

63-
Update all artists playcounts and ratings based on existing Navidrome DB
63+
Updates all artists playcounts and ratings based on existing Navidrome DB
6464

6565
### Common options
6666

6767
All commands have these options available:
6868
* `--db <path>` : Navidrome SQLITE .db source file path. By default if not passed, will look for a file named `navidrome.db` in the same folder as `musicbee-navidrome-sync.exe`
69-
* `-u, --user <user_name>` : choose Navidrome username (by default if not used, the first found user will be used)
69+
* `-u, --user <user_name>` : selects Navidrome username (by default if not used, the first found user will be used)
7070
* `--verbose` : verbose debugging
71-
* `-h, --help` : display help for command
71+
* `-h, --help` : displays help for command
7272

7373

7474
## 📋 Notes

0 commit comments

Comments
 (0)