Running for some (4) years Airtime 2.5.2 (latest free version), now moving to LibreTime because of various runtime (unsupported PHP too old etc.). My description also includes the (painfully) migration of the existing database, so new users might read that part as a story.
Installation
Nothing fancy, install OS (Ubuntu 18.04), git and curl are probably already there or at the distance of an sudo apt -y git curl, install icecast and apache2 (or whatever the web server you might need if you plan to pump the stream in a web page), then read the Libre docs, clone the repo and install -fiap.
Do NOT use Ubuntu later than 18.04 (so no 20) because it will not work.
Back to installer: did not work 100% mainly because of the post install setup (the web part), which have the habit of not saving the changed password for admin and others, so a nano visit to /etc/airtime/airtime.conf and on liquidsoap might be needed. Also /etc/airtime/icecast_pass might need tweaking as well.
So I had to stop everything (service apache2 stop, libretime runtime as well), change the passwords to match icecast, move airtime.conf to a backup location and rerun the web part, which worked perfectly.
[optional] Move of existing airtime database
Files moved from another server to this new one, 70 GB, rsync, grab a coffee (ok, more than one) and copy everything in the exact same default location (/srv/airtime/stor/). All good. Database move: complete pain. My setup is postgres, which does not support select from one database and insert in another, and the dblink postgres specific thing sucks ass. Also, postgres is quite slow, database fields slightly differs, so I had to export in a CSV the airtime tables (ccfiles, cchistory, ccshow etc.) Some of the tables had around 700.000 rows and I had to do manual SQL in order to map the old existing foreign keys over the new ones - took one day but all good.
The run
My setup is one main (webserver + icecast) machine - which acts also as a relay for the second machine - and libretime sits on a second machine. Although the interface is relatively different than what airtime 2.5.2 has, I was able to setup the params, stream, schedule shows etc. in no time. The dragging of tracks into the right panel does not respect the UI (meaning I am dragging between songs 100 and 101 but I end up with the new track somewhere below some rows) but I can live with that. The same limitation of a show that cannot have more than 24 hours is present, but other than that, everything it is running for a week now on a 4 GB RAM machine with CPU sitting most of the time in one digit. Import is very quick, smart blocks is a killer, and it works.
Conclusion
Although is not a stable release and is probably driven by a handful of guys having another jobs and doing changes in the spare time, it is a good fork which runs. Be comfortable with ssh and terminal because you might need to do this, especially when integrating with web servers, certbot, redirecting streams to HTTPS, making Icecast SSL-aware etc. But that's how Linux infrastructure is running, so no complains here.
Based on our record, KeePass seems to be a lot more popular than LibreTime. While we know about 206 links to KeePass, we've tracked only 1 mention of LibreTime. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Https://libretime.org/ seems like a helper tool for setting up icecast and other radio type services? I've only just learned about it just now so you'll want to evaluate it for yourself. Source: over 2 years ago
And the best part is there are solutions already that do this: https://keepass.info/ Does it work on Android or iOS? - Source: Hacker News / 7 months ago
The key difference here being that this is two way hashing so passwords can be decrypted. In reality, there are a lot of attack vectors like MITM, event logging or sometimes straight up storing data in plaintext. Through these hackers can generally get passwords of all users of these services. So, why don't people use local password managers? Just a txt file encrypted with "master password" should be pretty... - Source: Hacker News / 7 months ago
When you're at a point where you're relying on a display name to make security-critical decisions, you've already lost. Character substitutions like ķeepass or ƙeepass or keypass are at least possible to spot if you know the name of the product, but not the full URL. But there are many ways to create lookalike domains that don't change the product name: https://keepass.org https://keepass.net https://keepass.info... - Source: Hacker News / 8 months ago
> People love to hate on passwords but the reality is that for many circumstances (threat models) they are the best compromise. You can make them more than strong enough (take 32+ bytes out of /dev/random and encode however you like, nobody will ever brute force that in this universe) and various passwords managers solve the problem of re-use (never reuse a password). > And it comes with the benefit that you... - Source: Hacker News / 8 months ago
If you have used this combo at many sites (which is of course not recommended) then download one of the available free Password Managers like Keepass, Bitwarden, Lastpass or any others you can find with a Google Search. Source: 9 months ago
AzuraCast - AzuraCast is a free and open-source self-hosted "web radio station in a box".
1Password - 1Password can create strong, unique passwords for you, remember them, and restore them, all directly in your web browser.
Centova Cast - Centova Cast is the world's most advanced Internet radio stream hosting control panel.
bitwarden - Bitwarden is a free and open source password management solution for individuals, teams, and business organizations.
RadioBOSS - RadioBOSS provides professional radio programming engineering and automation at a fraction of what...
Lastpass - LastPass is an online password manager and form filler that makes web browsing easier and more secure.