listenbrainz-server VS watchtower

There's also ListenBrainz, run by the MusicBrainz org, which offers similar functionality without API restrictions or other paid features that Last.FM tries to push.

https://listenbrainz.org/

If you wish to use your scrobble data at all programmatically this is a far better tool to use.

If you really <3 clean data you can give listenbrainz.org a go (you can scrobble to that and last.fm concurrently so no need to ‘jump ship’)

Thanks for sharing, yea listenbrainz.org has been doing some great work. Also has an API which can make things interesting.

One way I keep up is using https://listenbrainz.org/ to track my listening habits. Then when you're logged in https://listenbrainz.org/explore/fresh-releases/ will show new releases from artists you listen to, and with KPop you can assume there is video(s) to go with each new release so I just go to youtube then to find them.

Spotify at least was the problem when there was tons of people complaining daily. But if last.fm is the problem now and otherwise you could try https://listenbrainz.org/ as well. You can even import your last.fm history.

But if you have issues with last.fm itself there is always ListenBrainz as well. I recommend both to everyone. I scrobble to last.fm, then import to ListenBrainz, but you can send your listens straight to ListenBrainz as well.

listenbrainz.org solves this problem, but it’s not as feature complete as last.fm, yet.

A friend who's hard into obscura sent me this: https://listenbrainz.org Could be hot, could be not.

p.s. listenbrainz.org doesn’t have this duplication problem 👍

Related: https://github.com/containrrr/watchtower

> if you're using the docker image, upgrades are a breeze. Just bump the tag on the image, redeploy, and you're done.

Or you could just run Watchtower beside it and it will automatically update your docker containers. https://github.com/containrrr/watchtower If you are OK with automated updates.

So i primarily use containers on my local machine walled off from the internet, so it's not a big concern for me. Watchtower [1] is popular among home server users too which automatically updates containers to the latest image.

For production uses I think companies generally build their own containers. They would have a common base linux container and build the other containers based off that with a typical CI/CD pipeline. So if glibc is patched, it's probably patched in the base container and the others are then rebuilt. You don't have to patch each container individually, just the base. Production also minimizes the scope of containers with nothing installed except what's necessary so they have few dependencies.

[1] https://github.com/containrrr/watchtower

You can use Watchtower (https://containrrr.dev/watchtower/) that solves problem of manual pulling on VPS.

I checked https://containrrr.dev/watchtower/ and Arguments, but I don't understand where to attach that using portainer.

Again, there are options to automate some of the burden here by using tools such as Watchtower.

Have you ever deployed a Docker app on a server, but everytime you push a new version of your image to a Docker registry you need to manually restart your app? If you want to automate this restarting, this blog post is for you! I am now going to show you how you can do this with literally 1 simple command using Watchtower!