Hacker News Reader

Comment by Arrowmaster | Hacker News Reader

># src: Mirano Verhoef ># Go into root >su - > ># Install all required dependencies apt update ; apt upgrade ; apt install podman -y ; cd ~ ; mkdir 4.2.23 ; cd 4.2.23 ; wget https://fw-download.ubnt.com/data/unifi-os-server/8b93-linux... ; chmod +x 8b93-linux-x64-4.2.23-158fa00b-6b2c-4cd8-94ea-e92bc4a81369.23-x64 ; ./8b93-linux-x64-4.2.23-158fa00b-6b2c-4cd8-94ea-e92bc4a81369.23-x64 install

This is some of the jankiest install installations I've seen in a long time. Not even using && to stop on an error, just plowing ahead for more errors to stack up.

View on HN

My issue with this comment is my issue with the original article -- what's the actual source for this information?

As far as I can tell, this article has no actual link back to any Unifi press release, git repo, or other project page about this, the closest the author does is link the downloads from Ubiquiti's site (as in, literally, links to the files, and nothing else).

This is janky, yes, and I'm not gonna shill for Ubiquiti, but for lack of a legitimate source, I don't think this is a fair representation of the actual install steps.

The actual source is this: https://community.ui.com/releases/UniFi-OS-Server-4-2-23/21d... but only accessible if you opt-in to the Unifi Early Access program. We are talking beta software / first release here, so any criticism needs to be looked at through that lens.

Also there is the official announcement now: https://blog.ui.com/article/introducing-unifi-os-server

My criticism was mainly of the original article for failing to link to a primary source beyond hotlinking some dmgs.

I appreciate you linking these, though, as well as the extra context.

And you're absolutely right about the original article not containing many links.

Their code must be perfect and thus no need to worry about pesky errors.

I think this is like adding overflow detection to a math equation in a textbook.

Things like this get the information out there in human-readable form to be understandable, and error checking would be for the reader.

Or said another way, more like gist.github.com vs github.com/some÷project.git

The fix is a simple as replacing semicolons with double ampersands.

Reply on news.ycombinator.com