Skip to content

Platforms & Default Paths ​

Supported Platforms ​

RolePlatformArchitectures
ServerLinuxx64 / ARM64
ServerWindowsx64
ServermacOSARM64
ServerFreeBSD 13+x64 / ARM64
ServerDockerMatches the host architecture (x64 / ARM64)
AgentLinux / Windows / macOS / FreeBSDSame as above (macOS: Apple Silicon only)

The install script detects the service manager (systemd / OpenRC / launchd / FreeBSD rc / Windows scheduled task) and registers a boot-time service; Docker deployments rely on restart unless-stopped — see Docker Deployment.

Default Paths ​

PlatformProgramConfig & data
Linux/opt/nodeflare/etc/nodeflare
Windows%ProgramFiles%\NodeFlare%ProgramData%\NodeFlare\Server
macOS/usr/local/libexec/nodeflare/Library/Application Support/NodeFlare/Server
FreeBSD/usr/local/libexec/nodeflare/var/db/nodeflare/server
DockerBundled in the image/etc/nodeflare in the container, mounted from the same host path in these examples

Agent (Linux): program at /opt/nodeflare/agent, config and state at /etc/nodeflare/agent. The SQLite file lives in the config directory.

In the Docker examples the config file is /etc/nodeflare/config.toml on both host and container. The directory and config file must be readable and writable by container user 10001:10001 — see Docker Deployment.

Log Locations ​

  • Linux (systemd): journalctl -u nodeflare -f; agent: journalctl -u nodeflare-agent -f
  • Linux (OpenRC): rc-service nodeflare status
  • macOS: /var/log/nodeflare.log
  • Windows: Get-ScheduledTaskInfo -TaskName nodeflare
  • Docker: docker logs -f nodeflare

Released under the MIT License.