LogForge
Synthetic event log generator with a FastAPI control plane, Typer CLI, templates, and outputs. Distributed on GitHub Releases (not PyPI).
sudo tar xzf logforge-1.0.7-linux-x86_64.tar.gz -C /opt
Download the Linux bundle first, then run this from the directory that contains the file. Adjust paths if you unpack somewhere other than /opt (see Installation below for caveats).
Download Files
Production installs use the Linux x86_64 tarball (unpacks to /opt/logforge when extracted under /opt). An optional Python sdist (.tar.gz) is for macOS, Windows, Apple Silicon, or development installs. See the README quick start.
| File | Type | Target | Uploaded | Size |
|---|---|---|---|---|
| logforge-1.0.7-linux-x86_64.tar.gz | Linux bundle | Linux x86_64 servers | 2026-04-05 | 53.6 MB |
| logforge-1.0.7.tar.gz | Python sdist | venv / macOS / Windows / dev | 2026-04-05 | 0.1 MB |
Installation
Recommended Linux x86_64 — production tarball
Matches README: Quick start (production). Full operator layout, systemd notes, and checksums: linux-tarball.md. (Same general idea as unpacking a Splunk Enterprise .tgz—see Splunk’s tar install notes.)
Before you unpack
- Some non-GNU versions of
tarmay not support-C. To install into/opt/logforge, eithercd /optor place the archive in/optbefore runningtar. That approach works for any directory you can write to. - The bundle does not create a Linux account. If you plan to run
logforge service install, the documented service user is typically logmgr—create that user (or your chosen account) first if your policy requires a dedicated user. - Confirm the disk partition has enough free space for the install tree and the log volume you intend to keep under
LOGFORGE_HOME.
Expanding the archive creates a logforge directory in the current working directory by default. To install into /opt/logforge, use -C /opt as below.
- Download logforge-1.0.7-linux-x86_64.tar.gz (link in the table).
- Unpack into
/opt(creates/opt/logforge).
sudo tar xzf logforge-1.0.7-linux-x86_64.tar.gz -C /opt
export PATH=/opt/logforge/app/bin:$PATH
export LOGFORGE_HOME=/opt/logforge
logforge init --force
logforge start
logforge start backgrounds on POSIX like a typical service; use logforge start -f (or --foreground) to stay attached. Stop with logforge stop. Data and config live under LOGFORGE_HOME (default /opt/logforge for this layout).
Optional: Python sdist (venv install)
Use this on macOS, Windows, Linux (including Apple Silicon or non–x86_64), or when you want a normal venv install. Requires Python 3.9 or newer (3.9–3.12 per pyproject.toml).
- Create and activate a venv.
python3 -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
- Install from the downloaded file (same directory as the
.tar.gz), or straight from GitHub:
pip install logforge-1.0.7.tar.gz
# or, without downloading manually:
pip install "https://github.com/Fulcrum-Technology-Solutions/LogForge/releases/download/v1.0.7/logforge-1.0.7.tar.gz"
After install, the logforge CLI is on your venv’s PATH. See linux-single-instance.md for broader single-instance layout (including venv-based installs).
logforge --version
Verify download checksums
If the release includes checksums.txt, compare SHA256 locally after downloading:
# macOS / Linux
shasum -a 256 logforge-1.0.7-linux-x86_64.tar.gz
# Windows (PowerShell / cmd)
certutil -hashfile logforge-1.0.7-linux-x86_64.tar.gz SHA256
# Python sdist
shasum -a 256 logforge-1.0.7.tar.gz
Release info
Requirements
- Python 3.9+ (sdist install); 3.9–3.12 supported
- Linux bundle: x86_64 GNU/Linux
- License: Apache-2.0