gyptazy

@gyptazy@gyptazy.ch

Believer in the power of open-source & community-driven innovation.

Former AS20621 NetOp that loves FreeBSD & illumos. Currently mostly in DevOps & developing (Python, Rust). Contributes to & . Evaluating and production usage of hardware/software.

Projects:
* BoxyBSD.com - A free VM hosting service to provide some value back to the community.
* manpageblog.org - A static blog generator in manpage design.
* QualvoSec - A security patch management tool.
Bloghttps://gyptazy.ch
GitHubhttps://github.com/gyptazy
Xhttps://twitter.com/gyptazy
0 ★ 0 ↺
in reply to »

gyptazy »
@gyptazy@gyptazy.ch

So basically it could now handle the VM stuff (admin & enduser), email account creation including custom domains, alias handling etc, creating default webspace (including LE TLS, fcgi, MariaDB and PGSQL management).

I really like this approach because of the data minimalism. It just needs a pubkey and the related user for authentication. No email, no password,… nothing. Doing this in a webinterface could also be possible but with much more efforts by creating client certificates from BoxyBSD CA.

But I’m still not quite sure if this will make it to prod

History