NODIVEXA.
Let’s talk

LAB CASE STUDY / LINUX

Server prepared.
Access and recovery checked.

Seven setup recipes executed on a new Ubuntu VM, followed by permission diagnosis, recovery and post-reboot checks.

← All case studies
Lab demo · synthetic dataNODIVEXA local environment
7 recipesExecuted on a new VM
Non-rootService and restricted access
After rebootAccess and services restored

What we tested

Ensure automation produces services that can be inspected and recovered, while retaining operator access and a recovery console.

What we did

  1. Prepare a separate Ubuntu VM, verified SSH host identity and firewall; check a fresh login.
  2. Execute recipes for non-root HTTP, Nginx, reverse proxy, PostgreSQL, Docker, a monitoring stack and a monitoring target.
  3. Change one synthetic file permission for diagnosis and recovery, then reboot the VM and verify access and services.

Test results

All seven recipes executed successfully. The non-root service, Nginx and proxy returned the expected markers. Permission failure was recovered without broadening access. After reboot, the boot identity changed, SSH worked and the service, Prometheus and Grafana returned.

Demo limitations

Local Ubuntu Server 24.04.5 VM with NAT and loopback host access. Not evidence for every OS, application or client server. Debian and other systems require separate verification; no production SLA is claimed.

LET’S BUILD SOMETHING RELIABLE

Your next step.
A conversation.

Tell us what you are running, what is getting in the way, and what you need next. Start directly on WhatsApp or Telegram.

Chat on WhatsAppTelegram