Configuration

Configuration

Languages: English | Français

This page gathers the practical configuration details that used to be scattered between the CLI page, examples, and release notes.

Where ngPost stores configuration

Since v5.4.0, ngPost uses a per-user application configuration directory:

Platform	Default config file
Linux	$XDG_CONFIG_HOME/ngPost/ngPost.conf or ~/.config/ngPost/ngPost.conf
Windows	%LOCALAPPDATA%\ngPost\ngPost.conf
macOS	~/Library/Application Support/ngPost/ngPost.conf

You can still use a specific file for one run:

ngPost -c /path/to/ngPost.conf

Migration from legacy paths

Older versions used different locations:

Platform	Legacy path
Linux/macOS	~/.ngPost
Windows	ngPost.conf next to the executable

On first launch, if a legacy config exists and the new config file does not, ngPost copies the legacy file to the new location and keeps the original file in place. This lets v5.4+ use the new layout without breaking older installs.

Related files in the config directory

The same directory is also used for per-user ngPost data:

• ngPost.conf: main configuration file.
• ngPost_history.sqlite: default structured SQLite post history database.
• vpn/: imported OpenVPN/WireGuard profile files.
• vpn/runtime/: short-lived VPN authentication files while a VPN connection is active.

History database

POST_HISTORY was the old CSV history file. Since v5.4.0, the main history is a SQLite database.

POST_DB = /path/to/ngPost_history.sqlite
HISTORY_STORE_PASSWORDS = true

Use POST_DB to move the database somewhere else. Existing CSV history can be imported from the CLI:

ngPost --history_import_csv /path/to/POST_HISTORY.csv

See History and resume for the full workflow.

Common configuration keys

Key	Purpose
nzbPath	Default folder for generated NZB files.
GROUPS	Newsgroups used for posting.
GROUP_POLICY	How posts are distributed when several groups are configured.
FROM / GEN_FROM	Fixed or generated poster email.
POST_DB	Structured SQLite history database path.
RAR_PATH, PAR2_PATH	External tool paths when bundled tools are not used.
VPN_AUTO_CONNECT	Automatically start/stop the configured VPN profile when needed.

For every CLI switch and automation option, see Command line usage.