DNS have been published, server is configured to listen to those ports, Docker container too.

Previously already published

The server works fine. Next step is to integrate Certbot or any other client with it and create relevant CNAMEs.

Server is deployed on Equatower.

It seems it's also possible to store the deploy key on the master, as long as it's fine to copy it to the server:

D2151 works well, but there are two issues:

Perhaps a master key would be more pertinent, if so, that's a candidate for Vault.

We've a deploy key in salt master, let's use it.

Roles core and saltmaster have been successfully fixed and applied.

After a few dozens of seconds, I've got:

Fun, after systemctl enable --now snapd.socket I got the following message:

OpenBSD version is netcat-openbsd package.

On those two Linux, we can use snap, per https://snapcraft.io/install/starship/debian and https://snapcraft.io/install/starship/centos.

In T1539#20449, @dereckson wrote:

Actually, there is now a port: https://www.freshports.org/shells/starship/

Need to install through ports, as we need to uncheck X11 and check AALIB in options:

Actually, it's cool with autopilot mode.

Furthermore, aalib and xaos don't have a port maintainer.

Unmaintained software (there are caretakers, but the owner doesn't maintain it, so patches are unmerged) and not really useful (old logo, information we can print through a script).

FWIW, port files are available at https://github.com/dereckson/freebsd-ports/tree/master/sysutils/linux_logo

Debug stacktrace

Compiling
Compiles successfully, but segmentation fault when doing something else than -V or -h.

Can't help for an API key:

The package has been deprecated, with the following rationale: