IDK if I’d recommend this to others, but I don’t trust unsupervised metadata lookup (I’m anal like that), so I lookup metadata with musicbrainz picard and then feed the files to beets only to keep my library organized.
My beets doesn’t do any lookup (no lookup plugins are enabled, none_rec_action: asis, fetchart configured to only look at the local filesystem).
If it’s for recruiters, put it on github. That’s the one they are most probably familiar with and you want to minimize barriers to access.
The simplest (= most basic) solution would be to assign several IPs to the machine (you can add multiple on the same network interface) and have each service listen on a specific address.
You’ll need networking basics for anything you do (there are lots of courses on youtube).
After that, you can just follow wherever you curiosity carries you :)
Err… you write markdown and hit “preview” before posting?
Also, the edit box (PC, browser) has a question mark button that will take you to https://join-lemmy.org/docs/users/02-media.html
Picard adds IDs too (well, I think it only adds musicbrainz ids, per default anyway, but those are the only ones I care about).
The lookup is automatic as well (you can review or intervene if it fails to identify the release).
It also has a plugin for replay gain (I redo that step in my script anyways) and can be configured to delete any previous tags if you re-process music that you had previously tagged with some other software (IIRC it doesn’t clean them up per default).
If you’ve not used it, I recommend giving it a try before deciding how to go on.