Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by j16sdiz | Hacker News Reader

Parent Full thread

j16sdiz·

https://github.com/koel/koel/issues/1099

Looks like the "sqlite-e2e" is for integration-test only.

View on HN

But sqlite is the only choice from those options that makes any sense for a personal music server.

(I use it in this role, with my own home-brewed media and documents library.)

It definitely should be the default IMO.

I have quite a few personal services running at home that use mysql.

Would be lovely if sqlite worked, but why is it the only one that makes any sense?

Installing/maintaining mysql or the others is a pain in the ass relative to sqlite (essentially no cost at all). For a personal media library, all write operations are trivially serializable. Sqlite DBs are the easiest to copy to new machines when you upgrade hardware.

> Installing/maintaining mysql or the others is a pain in the ass

Koel provides a docker-compose file for them, should make it trivial to spin it up.

Needing to delve into docker stuff is itself a bigger hassle than using sqlite. Which isn't saying much admittedly, but sqlite is basically hassle free in the most extreme way.

Oh yeah, but it's still far far away from "not making any sense"

Interesting, I wouldn't consider another DB driver for integration tests if that isn't usable in production. Probably a good reason for it but can anyone clarify why that's done?

Well, sqlite is the most simple alternative that's great for local testing.

And yet the "getting started" page says: "Any database supported by Laravel – MySQL, MariaDB, PostgreSQL, or SQLite"

The "wizard" also proposes a regular "SQLite" option. But it fails as well.

I wouldn't mind if it was a humble project, but the website is full of marketing BS, including "Koel is a music streaming solution that actually works™"

Reply on news.ycombinator.com