Sure, so on my custom install, I used the latest available Armbian:
___ ____ _ _ _
/ _ \ _ __ __ _ _ __ __ _ ___| _ \(_) | || |
| | | | '__/ _` | '_ \ / _` |/ _ \ |_) | | | || |_
| |_| | | | (_| | | | | (_| | __/ __/| | |__ _|
\___/|_| \__,_|_| |_|\__, |\___|_| |_| |_|
|___/
Welcome to Armbian 22.05.1 Bullseye with Linux 5.15.35-rockchip64
It ships with outdated nodeJS, interestingly. It had EOL in April, but since I have no nodeJS services running on the custom install anyway, it should be fine. In any case, as soon as you install something that runs on node, all install guides tell you to update nodeJS, so it will be fine.
~:% node --version
v12.22.5
But if I boot the
latest Futurebit OS - released over half a year ago (12/17/21) - I get this login screen. It's 5 releases behind on the Linux kernel and behind by one major Debian version.
_____ _ ____ _ _ _ _ _
| ___| _| |_ _ _ _ __ ___| __ )(_) |_ / \ _ __ ___ | | | ___
| |_ | | | | __| | | | '__/ _ \ _ \| | __| / _ \ | '_ \ / _ \| | |/ _ \
| _|| |_| | |_| |_| | | | __/ |_) | | |_ / ___ \| |_) | (_) | | | (_) |
|_| \__,_|\__|\__,_|_| \___|____/|_|\__| /_/ \_\ .__/ \___/|_|_|\___/
|_|
Welcome to Armbian 21.05.1 Focal with Linux 5.10.35-rockchip64
~# node --version
v14.16.1
[/quote]
Interestingly, it comes with nodeJS v14, but then I don't understand why
on GitHub, I was told that
Try to use Node version 9
By now it's the only way
Compilation on the latest nodeJS version didn't work; hence I went on GitHub to ask.
I will try again with nodeJS 14, which is by the way the oldest LTS version of node ('Maintenance LTS' phase) and will be updated for just another 10 months.
It would be much preferred to have ApolloUI be able to run on 16.x or 18.x, though.