https://github.com/zerovox/music-sync

utilities for syncing music to s3, scraping itunes metadata, writing to navidrome db, etc
https://github.com/zerovox/music-sync

Last synced: about 2 months ago
JSON representation

utilities for syncing music to s3, scraping itunes metadata, writing to navidrome db, etc

• Host: GitHub
• URL: https://github.com/zerovox/music-sync
• Owner: zerovox
• Created: 2022-01-17T03:23:26.000Z (about 3 years ago)
• Default Branch: main
• Last Pushed: 2022-03-05T18:28:00.000Z (almost 3 years ago)
• Last Synced: 2024-08-13T07:17:53.917Z (5 months ago)
• Language: TypeScript
• Size: 146 KB
• Stars: 3
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• jimsghstars - zerovox/music-sync - utilities for syncing music to s3, scraping itunes metadata, writing to navidrome db, etc (TypeScript)

README

        
# music-sync

Previously, I used itunes with itunes match to sync music between my desktop, laptop, etc. Seemingly there was no way to pair this with an android phone, and I wanted more control over my setup (youtube music is a joke).

My new setup is a navidrome instance hosted on the cheapest linode instance, with a linode objects bucket mounted using rclone for music library storage, and subsonic android clients such as ultrasonic for offline/android auto usage.

In this repo, there are various utilities that helped me transition:

- `./sync.ts` uploads files from a local music dir to a given folder in a bucket. It stores md5 hashes of the sync'd files (and the etags reported on upload) to track which files are out of date. It does not sync deletes. I re-run this whenever I have new music to sync to my navidrome instance.

- `./metadata-to-navidrome.ts` grabs the ratings, play counts and last played info from my local itunes library xml file, finds the corresponding item_ids in a navidrome sqlite DB, and creates annotations. This let me transition my many years of play count and rating history to navidrome as a one time migration.

It uses aws-sdk for s3 writes, and expects a `.aws-credentials` file in the working dir:

```

[default]

aws_access_key_id="..."

aws_secret_access_key="..."

```