fmeshsync fix with synology,vm's and lxc

README.md

@@ -1,4 +1,4 @@
-# AssetManager 0.5.5.42
+# AssetManager 0.5.5.52
 
 AssetManager is a self-hosted web application for managing IT equipment and other organizational assets. It provides asset inventory, software inventory, remote job execution, reporting, privacy/retention documentation, and optional integration with MeshCentral.
 
@@ -27,6 +27,9 @@ The project is licensed under the **Apache License 2.0** and may be used, modifi
 
 ## Installation
 
+For a detailed first-start, image deployment, authentication, callback, update, and troubleshooting guide, see [`docs/INSTALLATION.md`](docs/INSTALLATION.md).
+
+
 Create the local environment file:
 
 ```bash
@@ -50,6 +53,20 @@ docker compose up -d --build
 
 By default, AssetManager is exposed on port `8088`.
 
+### First start and authentication
+
+On a fresh image-based installation, `config.json` and `APPINFO.json` are created automatically in `data/config/` if they do not exist. Existing files are never overwritten by the container entrypoint.
+
+The default configuration starts with authentication disabled so the initial configuration can be completed. A prominent warning banner is displayed in the web interface while this mode is active. Before normal use:
+
+1. Edit `data/config/config.json`.
+2. Set `authentication.mode` to `local`.
+3. Restart the application container with `docker compose restart app`.
+4. Sign in with the protected local administrator configured through `LOCAL_ADMIN_USERNAME` and `LOCAL_ADMIN_PASSWORD` in `.env`.
+5. Configure LDAP/Active Directory afterwards if required. The protected local administrator remains available as an emergency account.
+
+Do not expose a fresh installation to untrusted networks while authentication is disabled.
+
 ## Persistent data
 
 Runtime data is stored in bind mounts below `data/`: