LEMP / LAMP adoption

Inventory first, take ownership second

Sysaro should not silently rewrite production configuration. Discovery is separate from adoption: the platform identifies infrastructure first and only then decides what can safely become managed.

For an existing LEMP/LAMP server, Sysaro starts with passive discovery and creates a fingerprinted candidate. Adoption happens only after review; stale hashes, validation failures or failed reloads stop the takeover and preserve rollback.

Adoption pipeline

Unknown production configuration does not become managed merely because Sysaro discovered it.

Passive scan

No production state changes.

Classification

Fingerprint + SHA-256

Review

Backup

Managed apply

Validation

Rollback available

What is discovered

nginx, Apache, PHP-FPM, MySQL/MariaDB, PostgreSQL, Redis/Valkey, MongoDB.

What protects takeover

Stale-hash protection, backup, native config tests, atomic writes and rollback.