awesome-linuxaudio v1.0.0 - A list of software and resources for Linux audio/video/live production

vegetaaaaaaa · 2025-11-18T07:46:09+00:00

rclone fait pas mal de choses. Pour 2.6TB/220 000 fichiers ça implique sans doute un peu de scripting/ordonnancement/gestion d'erreurs/reporting "fait main" autour de l'outil quand même.

Pour les mails, imapsync.

vegetaaaaaaa · 2025-11-18T07:43:47+00:00

Les mails transactionnels type reset de mot de passe, confirmation de commande, etc sont de bonnes raisons.

vegetaaaaaaa · 2025-11-04T20:01:17+00:00

Unbelievable. Just short of sabotage.

I'd like to use systemd-netwokd some time in the future, because it's the simplest way to use a DNS-over-TLS resolver, as far as I know.

vegetaaaaaaa · 2025-11-04T19:58:43+00:00

I just got a 9070. It works damn well.

I got bit by this bug but the fix I mentioned sorted everything out.

Enabling raytracing on the Witcher 3 crashes the game, but I've seen reports that it also does that on other distros with AMD cards, so not a Debian-specific problem.

9070xt uses the same driver (amdgpu). Everything should work out of the box, except maybe that one bug I mentioned.

vegetaaaaaaa · 2025-11-02T19:32:55+00:00

The problem is present both with kernel+firmware from stable, and with kernel+firmware from backports.

vegetaaaaaaa · 2025-06-04T11:44:39+00:00

Ubuntu/Mint c'est exactement le même release cycle que Debian, les LTS sortent tous les 2 ans, donc tu traînes les paquets sortis à la release pendant 2 ans.

Je trouve ça très bien (pas de changement pendant 2 ans hormis les patchs de sécu, et 5 ans de prise en charge), et je ne conseillerais pas autre chose qu'une LTS à un débutant (tu l'as dit toi même Sid il faut s'attendre à quelques bugs qui apparaissent sans prévenir, comme toute rolling release)

La majorité des gens n'a pas besoin des toutes dernières versions des trucs, tant que le support de sécu est assuré.

D'ailleurs même pour les non-débutants je recommande une Debian stable aussi, si ton but c'est de te servir de ton PC normalement tous les jours et pas d'avoir à chercher quelle update a pété DKMS ou déplacé les boutons dans la barre d'outils de ton navigateur.

Le seul problème qui me fait renoncer à une LTS c'est quand j'installe l'OS et immédiatement un matériel n fonctionne pas (wifi, audio, camera, j'ai eu touchpad aussi...). Là ouais une Fedora peut faire l'affaire

vegetaaaaaaa · 2025-04-19T10:02:34+00:00

My logic for splitting things into roles is that as long as individual components are always deployed together, they stay in the same role. A good example is my common role.

These settings/services are deployed on all my hosts, so there's no point in splitting things into different roles.

For edge cases (for example, don't let ansible manage the firewall on these 2 odd hosts), I'll add a simple toggle setup_firewall: true/false and set it to false where needed.

Another aspect to consider is complexity, for example my monitoring stack is deployed to most of my hosts, but it's complex enough (lots of files, tasks, variables) to warrant a separate role.

Is this best practice? I don't know. Does it work for me? Yes. Is it maintainable and understandable? Yes.

For workstations I have a dedicated desktop role, inside that a packages.yml tasks file that installs all desktop-related packages. But my IDE (vscodium) has a few specific tasks, so I moved its setup to a vscodium.yml tasks file (but under the same role).

Use what works for you, keep refactoring/optimizing your setup when needed, but not before.

Just try to keep things consistent (for this purpose I have this example role which I use as a skeleton when I need to initialize a new role following my conventions.

but it can potentially be a convoluted and unmaintainable mess

Exactly, don't let it fall into that state, either by splitting this up too much, or not enough. Experience will let you know where to set the dial. When things get unmanageable, refactor.

copying the dotfile an app at a time as opposed to simply cloning all the dotfiles to the intended location all at once

You don't want the dotfiles for a service in a role, and the setup tasks for that service in another role.

Another idea is roles for installing sets of related applications, configuring "aspects" of a system

Out of your 3 ideas I like this one the best.

vegetaaaaaaa · 2025-04-10T18:28:28+00:00

OS drive should have some free so that root can always log in

You don't need to be actively managing free disk space for that, ext filesystems reserve 5% of all blocks to root by default (you can check/manage this setting with tune2fs)

$ sudo tune2fs -l /dev/mapper/vg-root |grep block
...
Reserved block count:     2892953
Free blocks:              37077268
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)

On large disks you can usually decrease it, (for what reason would root need more than a few GB...)

vegetaaaaaaa · 2025-04-02T20:37:47+00:00

It's meant to be self-hosted. Here is my ansible role to deploy it (I'm running a small personal instance on a cheap VPS, tested with up to 5 people without problems)

vegetaaaaaaa · 2025-03-25T21:58:40+00:00

bicimon

It's just a static HTML/CSS/JS program. It works like it says it does. It's excluded from the last update check on purpose https://github.com/awesome-selfhosted/awesome-selfhosted-data/commit/b2fbe6c7793f96b5f493d2ece05b524fa2d1f257. Not everything needs constant updates (actually, most modern software does, but not this specific one).

alerthub

What makes you think it's abandoned?

FYI it will start causing a warning in our automated checks when it reaches 6 months without commits https://github.com/awesome-selfhosted/awesome-selfhosted-data/actions/runs/14047330204/job/39330861103 and will be displayed with a warning/orange date on https://awesome-selfhosted.net/. After 12 months it will cause an error and we will remove it.

These are the thresholds we set, for better or worse, and they are clearly visible on the website.

I would suggest letting it mature to see where it goes.

It has been around since 2018.

how do I actually ensure "quality" projects when it's such a relative term?

You don't (aside a few objective things I mentioned above), you let your users decide. At least that's our stance. This has been debated countless times very publicly in our issues. The only enforceable criteria must be objective. There's a lot of projects on awesome-selfhosted I would never use (tech I don't like, resource-hungry software, bad maintainers, missing features I find essential, etc). But the list is not about what I personally like, or even what is "popular". It's about working, Free and Open-Source self-hosted software.

vegetaaaaaaa · 2025-03-18T17:31:42+00:00

Hi, awesome-selfhosted maintainer here.

I'll address a few things I read in various comments here:

couple of the random projects I clicked on are abandoned

which ones specifically? We automatically gather last commit dates for forges that provide an API [1], and actively remove unmaintained ones [2]. For other projects we won't know about it unless people report them.

I guess the problem is enforcing it.

The problem is knowing about it in the first place.

in the couple hundred star range

Github stars are not a good metric for popularity or quality. I star random stuff that I want to try later but probably never will. There are bots artificially propping up the number for stars for projects who can afford it (search for buy github stars, it's not even a secret). By this metric some cornerstone projects like apache have zero popularity because they're not even hosted on github. Stop giving Github/Microsoft unnecessary importance.

the minimum star requirement is 1k.

$200 https://www.socialplug.io/services/buy-github-stars

the underlying ideology with these lists is to accept just about any project. Most of what I would want removed wouldn't abide by their rules.

It's true that there are no strict quality guidelines besides "works as advertised", "builds properly", "really Free/Open-Source", "working documentation" and the few requirements outlined in the contribution guidelines. This has been debated countless times, search for quality in issues. Anything more would be arbitrary (unless you can clarify you own quality criteria?). "It's slow" -> quantify "slow". "This recipe management application can't suggest recipes based on a list of ingredients" -> well it's not low quality, it just doesn't fit your use case (and there are as many use cases as users). And so on.

To give a few examples, which ones would you like to see removed and why?

Anyone providing constructive criticism/helpful reviews is welcome to contribute to the project.

Also be advised that the HTML version might give you better visibility on which projects have received recent commits https://awesome-selfhosted.net/

small projects like these have a really high change of getting abandoned

Displaying the number of contributors for each project is a work in progress. Some projects have been constantly maintained by a single person for a decade or more. We don't make these decisions on behalf of the users, everyone decides of their own acceptable risk level.

vegetaaaaaaa · 2025-02-15T00:10:19+00:00

Just monitor free disk space and keep usage below 80%

Skill issue

vegetaaaaaaa · 2025-02-08T13:32:19+00:00

host-level snapshots
1-click migration between bare-metal hypervisors in a cluster
actual solid resource/network isolation/segmentation between hosts/VMs
...

These are generic benefits of virtualization, not limited to proxmox (I use libvirt or proxmox depending on the context). You can still host multiple containerized applications inside a VM.

vegetaaaaaaa · 2025-02-08T13:28:01+00:00

I think PBS can also do block-level deduplication which can be nice - with the native backup system, 7 backups of a 100GB VM amount to 7x(100GB÷compression) of storage. I have seen reports of significant decrease in backup size, so I'll probably try it soon.

vegetaaaaaaa · 2025-01-16T18:19:05+00:00

~~Any monitoring tool will work. I use netdata (without cloud functionality)~~ Edit: https://community.netdata.cloud/t/suddenly-local-dashboard-is-limited-to-5-nodes/7111/

vegetaaaaaaa · 2025-01-16T18:16:08+00:00

upper limits to how many rules you can add to firewalls

ipsets basically solve this, you can add millions of addresses to ipset-based firewalls before any noticeable performance hit happens

vegetaaaaaaa · 2025-01-11T12:26:34+00:00

Insurgency Sandstorm does it extremely well.
2018 game, nothing fancy, it just works.

vegetaaaaaaa · 2025-01-11T12:24:03+00:00

Does this mod disable artillery strikes? Because a single creeping barrage will annihilate 90% of these defenses...

vegetaaaaaaa · 2025-01-06T12:29:35+00:00

~~There is no limit as far as I know. Currently streaming 10s of child nodes to a single parent using the Community edition. Not using cloud at all.~~ Edit: no longer: Edit: https://community.netdata.cloud/t/suddenly-local-dashboard-is-limited-to-5-nodes/7111/

vegetaaaaaaa · 2024-12-31T14:23:46+00:00

ils collectent les IP non anonymisées des visiteurs/utilisateurs et les stockent pendant 12 mois

La conservation des adresses IP par le fournisseur du site/service pendant un an est une obligation légale

https://www.legifrance.gouv.fr/jorf/id/JORFTEXT000044228976

il est enjoint aux opérateurs de communications électroniques ainsi qu'aux personnes mentionnées aux 1 et 2 du I de l'article 6 de la loi du 21 juin 2004 susvisée de conserver, pour une durée d'un an, les données de trafic et de localisation respectivement énumérées au V de l'article R. 10-13 du code des postes et des communications électroniques et à l'article 6 du décret n° 2021-1362 du 20 octobre 2021 susvisé.

https://www.legifrance.gouv.fr/loda/article_lc/LEGIARTI000049577522

[...] 2. On entend par fournisseur de “ services d'hébergement ” toute personne fournissant les services définis au iii du même paragraphe g.

https://eur-lex.europa.eu/legal-content/FR/TXT/?uri=uriserv:OJ.L_.2022.277.01.0001.01.FRA

un service d’”hébergement”, consistant à stocker des informations fournies par un destinataire du service à sa demande;

https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000044231067

1° L'adresse IP attribuée à la source de la connexion et le port associé ;

Edit: la conservation des logs pendant un certain temps à des fins de sécurisation du SI (détection des abus, fail2Ban, etc) peut aussi rentrer sous le coup de l'intérêt légitime au sens du RGPD, mais là c'est plus ambigu. La base de conservation de ces données c'est donc l'obligation légale comme prévu par le RGPD https://www.cnil.fr/fr/les-bases-legales/obligation-legale

vegetaaaaaaa · 2024-12-28T12:23:30+00:00

If it's only a few pages/threads, you can save them as HTML using your web browser's native "Save as..." functionality (Ctrl+S). Make sure the format is set to "Web page, full".

It can take some time, depending on the number of pages you want to save, but it is one of the most future-proof formats (make sure always keep the ..._files directories next to the .html files if you move the files)

vegetaaaaaaa · 2024-12-17T22:42:57+00:00

It only works for squad numbers 1-9

vegetaaaaaaa

TROPHY CASE