I tried it out. I like the idea of the fully customizable UI. I can't seem to get it to import anything as a library and it constantly crashes after roughly 5-10 minutes, though. Am I missing something or doing something wrong, or is that the expected behavior at this point in development?
That is not expected behavior, no. How did you install it? Through a package? Or did you build from source?
There is currently problems with the way fooyin and fooyin-bin in the AUR are packaged which has been leading to crashes when trying to add tracks. I'm attempting to get that resolved.
Using an Ubuntu (22.04) based distro, I tried installing with the jammy .deb a couple times, which produced the constantly crashing result. I just built from source, which appears to have resolved the constant crashes, but I still can't add a library.
I found that all I needed to do to add a library was close the app and reopen after the first time opening the version built from source. Built myself a layout similar to the Obsidian preset. Really nice customizable player! I have two recommendations: have some way for the Library Filter widget to show individual tracks so you can add them to a playlist, and have some way to actually view and edit the Playback Queue. Other than that, this is a great player!
Hmm, I'm not seeing either of those issues. I have a 1.5TB library imported and have listened for many hours straight without a crash. Version 0.4.2 was just released today. Maybe give that a shot. https://github.com/ludouzi/fooyin/releases/tag/v0.4.2
I solved the issues yesterday by building from source, which solved the crashing issue (guessing a packaging issue with the .deb version is one problem) and then after one restart of the app I was able to add my library. Works fine now.
The Foo is obviously from Foobar. Google translate says "fuyin" is "copy" in Chinese, which I guess could make sense since it's a copy of foobar2000. It also says "fooyin" is "I'm sorry" in Somali, which is probably a coincidence because that makes no sense.
EDIT: One of the screenshots in the README is in Chinese so yeah that's probably it.
If Nintendo would put half the effort into game development as they put into picking legal fights, maybe they could make profit off their video games enough they wouldn't have to do lawsuit trolling.
Could've used something like this for my Nokia which became unusable because of a small crack in the screen and a broken USB port. Those fuckers glued the screen on instead of having some convenient screws in the back. So in order to switch out the 5 € port I had to try to remove the 120 € screen which didn't survive because of a tiny crack.
I have no idea as all video editors are too complicated for me and I didnt ever find the time to learn them... even though I should. And then I will use KDENlive
I'm curious how using ansible to deploy docker containers is easier than just using docker compose?
Ansible makes sense to setup the OS the way it needs to be (file systems, folder structure etc), but why make every container through ansible instead of just making a docker compose and maybe having ansible deploy that?
Even easier is probably to just run something like portainer and run the compose file through there
just making a docker compose and maybe having ansible deploy that?
that's what I do, why ansible? Because it makes it easier to deploy the same service in different servers with slightly different configurations, for example when migrating from one server to another. Also it helps with having something I can easily backup (e.g. git repo) that can redo my server(s) if needed.
That being said I'm still setting everything up with ansible.
I’m curious what issues you had with TrueNAS? I’ve been using it for about a year now and the only issue I have had has been with one of my pools deleting itself after a reboot, but that was user error because I put the wrong SED password in the settings.
The apps service just borked itself and I couldn't get it to properly start anymore. Also deploying apps always took a ridiculously and annoyingly long time (like about 15 minutes to deploy NPM).
If I read this correctly, Immich is setup entirely through Ansible, no docker compose. That's fine, however if Immich changes something drastically in their setup topology, it'll be more work for you to implement those changes. For services that use docker compose, you could use Ansible to deploy a compose file in a dir, say /opt/immich-docker along with its requisite .env and other files. Then setup running it via systemd. Then when you need to update it, it's almost copy-paste from the upstream compose file into your Ansible repo.
I wouldn't do that because I'd be inevitably picking up breaking changes without my knowledge that I'd have to fix after the fact. Unless you're pulling from a tag I guess. Still storing along the playbook feels more robust. It's less likely to get any surprises. Also I'm working under the assumption that you want to write idempotent code so you don't get breakage when your rerun it, which allows to run it on a schedule, to ensure your config doesn't drift too much.
In a similar situation. I was using Open Media Vault but it has some networking bug that I just can't nail down or work around. I have to manually fix the networking every time it breaks. Otherwise I barely used OMV features and did most things through Docker. I'll be switching to Diet Pi and probably Ansible unless I feel like learning Puppet.
It should be pretty easy to adapt it for Debian. The only thing you need to change as far as I can see is the usage of the dnf module to the apt module.
If you want to make your playbooks/roles more universal, there's a generic package module which will figure out what package manager to use based on the detected OS.
Or, if that doesn't fit your needs, you can add conditions to tasks (or blocks of tasks), like
when: ansible_os_family == "Debian"
and use that for tasks specific to a given Linux distro/family.
I know but I also learned that it's generally better to use the specific module for the package manager (just can't remember why from the top of my head) and I never intended this playbook to be generally usable.
github.com
Hot