Combining services (game-db-updater and playnite-web-app)

[andrew-codes]

There is no technical reason to separate the game-db-updater service from playnite-web-app. Separating has its benefits, but also its problems.

Pros

• Users can run the game-db-updater without running playnite-web. This can be helpful to capture your gaming library database but not run playnite-web-app as a front-end.

Cons

• More services to coordinate when deploying.
• More images to publish and maintain

Additionally, with the soon to be introduction of an API built into playnite-web-app, the web app will be more than just front-end. It will also provide API access to the game library. This most likely will mitigate the need to run the game-db-updater separately anyway.