[GH-ISSUE #520] understanding koel:sync #365

New issue

Closed

opened 2026-02-26 02:32:58 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 02:32:58 +03:00

Owner

Originally created by @Fahad-pnw on GitHub (Jan 16, 2017).
Original GitHub issue: https://github.com/koel/koel/issues/520

Hello, could you please help me understand koel:sync
i've got some data stored via a cms to the database on the songs table. Each time i do KOEL:SYNC it puts up data that i stored earlier on to this location.
The fields are titles, descriptions for each tracks and alike.
now again, i store some values say, by...database directly, next as i koel:sync, the command simply reverts it, makes it empty.

Could it be that the ID3 tags aren't being placed into the tracks, and koel:sync applies what it sees under the ID3 tags, can you suggest if i'd turn off the ID3 sync, or if i'd sync the files to have the updated titles that i've stored in the database? i just dont want the whole thing reverted back each time it syncs?

Could you please help through this, i've been digging this for 3 days and have found nothing that would help.

Originally created by @Fahad-pnw on GitHub (Jan 16, 2017). Original GitHub issue: https://github.com/koel/koel/issues/520 Hello, could you please help me understand koel:sync i've got some data stored via a cms to the database on the songs table. Each time i do KOEL:SYNC it puts up data that i stored earlier on to this location. The fields are titles, descriptions for each tracks and alike. now again, i store some values say, by...database directly, next as i koel:sync, the command simply reverts it, makes it empty. Could it be that the ID3 tags aren't being placed into the tracks, and koel:sync applies what it sees under the ID3 tags, can you suggest if i'd turn off the ID3 sync, or if i'd sync the files to have the updated titles that i've stored in the database? i just dont want the whole thing reverted back each time it syncs? Could you please help through this, i've been digging this for 3 days and have found nothing that would help.

kerem closed this issue

2026-02-26 02:32:58 +03:00

kerem commented

2026-02-26 02:32:58 +03:00

Author

Owner

@Fahad-pnw commented on GitHub (Jan 16, 2017):

more info: i moved the data from one server to another and then all the additional data won't sync.

so, i believe the koel:sync / inotify checks for update_file tag? how is this working really, so in case i've to move folders in future, the data doesn't get lost, the additional data that i'm putting along each file, say title....description and so on?

@Fahad-pnw commented on GitHub (Jan 16, 2017): more info: i moved the data from one server to another and then all the additional data won't sync. so, i believe the koel:sync / inotify checks for update_file tag? how is this working really, so in case i've to move folders in future, the data doesn't get lost, the additional data that i'm putting along each file, say title....description and so on?

kerem commented

2026-02-26 02:32:58 +03:00

Author

Owner

@phanan commented on GitHub (Jan 16, 2017):

If the songs are kept intact (not moved or edited), sync process shouldn't reset its data. If it does, please file as a bug.

@phanan commented on GitHub (Jan 16, 2017): If the songs are kept intact (not moved or edited), sync process shouldn't reset its data. If it does, please file as a bug.

kerem referenced this issue

2026-02-26 02:35:53 +03:00

[PR #365] [CLOSED] This fix removed some unused use statement from controller class #1226

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/koel-koel#365

No description provided.

Rows
Columns