No, Audacity is licensed as GPLv2+.

Audacity was bought in 2021 by Muse Group, and a few weeks later, they announced that they would introduce Google Analytics and Yandex-based “telemetry”. After strong criticism by the community, Muse Group backtracked, emphasized their commitment to the GPL license, dropped their plans to include Google/Yandex tracking, and instead opted for a self-hosted solution for bug reports and update checks. Both can be disabled, and some distributions disable them by default.

Still, a few forks emerged, Tenacity is the only one that is still actively being maintained. The last commit is from today, but their repository is at 16k commits, compared to 21k commit for Audacity, so it seems the two projects have diverged.

I did the same last week (and am still in the process of setting up more services for my new server). I have a few VMs (running Fedora CoreOS, with podman preinstalled), and I use ansible to push my quadlets, podman secrets, and static configuration files. Persistent data volumes get mounted using virtiofs from the host system, and the VMs are not supposed to contain any state themselves. The VMs are also provisioned using using ansible.

Do you use ansible to automatically restart changed containers after pushing your changes? So far, I just trigger a systemctl daemon-reload, but trigger restarts manually (which I guess is fine for development).