me0nline/LOGAR
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 10 Wiki Activity

docs(wiki): add default login credentials and installer data directory / license options to installation guide

me0nline
2026-09-26 20:44:00 +02:00
parent a5291b6f3b
commit f919ced08c
1 changed files with 44 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Deployment-and-Installation.md
+44 -8
@@ -6,6 +6,26 @@ LOGAR is distributed as self-contained standalone binaries (`Server.bin` / `Serv
## 1. Central Server Hub Deployment
### WebUI Dashboard & Default Login Credentials
Once LOGAR Server is installed or executed, the WebUI Management Console is immediately accessible:
- **WebUI URL**: `http://<server-ip>:8443/webui` (or `http://localhost:8443/webui`)
- **Default Username**: `admin`
- **Default Password**: `admin_logar_2026!`
| Setting | Default Value | Environment Variable Override | Description |
| :--- | :--- | :--- | :--- |
| **Username** | `admin` | `LOGAR_ADMIN_USER` | Initial administrative user account |
| **Password** | `admin_logar_2026!` | `LOGAR_ADMIN_PASS` | Default master administrative password |
| **Session Secret**| Auto-generated | `LOGAR_SESSION_SECRET` | HMAC cookie signature key |
> [!TIP]
> **Changing the Default Password**:
> Administrators can change the password at any time from the WebUI settings modal, or through the REST API via `POST /api/admin/change-password`.
---
### Standalone Executable (Zero Dependencies)
Download `Server.bin` (Linux) or `Server.exe` (Windows) from the release assets:
@@ -18,23 +38,38 @@ chmod +x Server.bin
.\Server.exe
```
On first launch, the server automatically generates its Subordinate CA keypair, server TLS certificate, and default configuration file. The WebUI is immediately accessible at `http://<server-ip>:8443/webui`.
On first launch, the server automatically generates its Subordinate CA keypair, server TLS certificate, and default configuration file.
---
### Automated Linux Server Service (Systemd)
To install the server as a persistent background service managed by `systemd`:
```bash
# Interactive installation (prompts for config directory and optional .lic file)
sudo ./compilation/install_linux_server.sh
# Unattended / Automated installation with license activation:
sudo ./compilation/install_linux_server.sh --data-dir /etc/logar --lic /path/to/server.lic
```
This script:
1. Deploys the standalone executable to `/opt/logar-server`.
2. Generates the initial PKI keys and configuration.
3. Installs and starts `logar-server.service` with `LimitNOFILE=65536`.
2. Configures data directory (default: `/etc/logar` or user-specified).
3. Imports the `.lic` license file (if provided).
4. Installs and starts `logar-server.service` with `LimitNOFILE=65536`.
---
### Windows Server Service Installation
1. Download or compile `LOGAR-Server-Setup.exe`.
2. Execute the installer. It will install the server binary to `{autopf}\LOGAR` and register the `LOGAR_Server` Windows service via NSSM.
1. Download `LOGAR-Server-Setup.exe` from [Releases](https://gitea.eibl.tech/me0nline/LOGAR/releases).
2. Execute the installer wizard:
- **Binaries Folder**: Default `C:\Program Files\LOGAR-Server`.
- **Data & Configuration Folder**: Choose default (`C:\ProgramData\LOGAR-Server`) or browse to select any custom storage path (e.g. `D:\LOGAR-Data`).
- **License File (.lic)**: Optionally select a signed `.lic` license package to activate your seat quota and CA during installation.
3. The installer registers and starts the `LOGAR_Server` Windows service via NSSM with full user/service permissions.
---
### Development Mode (Running from Python Source)
*(Optional for contributors & local development)*
@@ -78,12 +113,13 @@ journalctl -u logar-client.service -f
### Inno Setup Automated Installer
1. Download `LOGAR-Client-Setup.exe` from the latest release.
2. Run the installer or deploy silently via Group Policy / SCCM:
2. Run the installer (or deploy silently via Group Policy / SCCM):
```cmd
LOGAR-Client-Setup.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART
```
3. Place `client_config.json` (exported from Server WebUI) into `C:\Program Files\LOGAR\client_config.json`.
4. The service automatically enrolls on first start and streams Windows Event Logs continuously.
During interactive setup, you can select the binaries folder and the data directory (default: `C:\ProgramData\LOGAR`).
3. Place `client_config.json` (exported from Server WebUI) into `C:\ProgramData\LOGAR\client_config.json` (or your chosen data directory).
4. The `LOGAR_Client` service automatically enrolls on first start and streams Windows Event Logs continuously.
### Windows Service Management
- **Service Name**: `LOGAR_Client`