Command Line Reference
Use tackler --config path/to/tackler.toml
to run configured reports and exports.
The name of the configuration file could be anything, but tackler.toml is used as reference for clarity through this documentation.
Some of the configuration settings can be overridden by command line arguments. See below for available options.
See tackler.toml, accounts.toml, commodities.toml and tags.toml for full configuration options. |
Commands
new <name>
Create a new journal and configuration setup as name
.
You can run it as:
tackler --config name/conf/tackler.toml
init
Initialize journal at the current working directory.
You can run it as:
tackler --config ./conf/tackler.toml
Accounting Auditing
See Accounting Auditing for full documentation.
Output
Input
Options related to accounting Tackler Journal input.
--input.file <filename>
Path to single transaction journal file. Relative path is relative to the current working directory.
FS Storage
See Filesystem Storage Guide for full documentation.
--input.fs.path <path>
Filesystem path to journal directory
This is the root of journal, see also --input.fs.dir
GIT SCM Storage
See Git SCM Storage Guide for full documentation.
--input.git.repository <path>
Path to git repository
Path to .git
directory or bare git-repository.
This could be a path to .git
directory inside working copy
Reporting
Options related reporting
--accounts <regex>…
Account selectors for reports and exports
List of patterns (regex) for account names.
These are full match regular expressions, and they try to match full account name. Use wildcard patterns .*
, (:.*)?
, etc. when needed.
Use empty string ""
to list all accounts
--reports <type>…
List of Reports to generate
The list is space separated
Possible values: register
, balance
, balance-group
Commodity Price
--price.lookup-type <lookup-type>
Type of price lookup method
Possible values: none
, txn-time
, last-price
, given-time
--price.before <time>
Timestamp to use for price lookup. This either partial or full <ISO-8066-timestamp>
. The same rules applies as with txn timestamps: if time or zone is missing, then configured default is used.
Filters
--api-filter-def <filter>
Txn Filter definition in JSON.
See Transaction Filters for documentation of available filters. There are also transaction filter examples under Tackler Examples.
The filter definition could be ascii armored with base64 encoding. The ascii armor must have prefix 'base64:'
base64:eyJ0eG5GaWx0ZXIiOnsiTnVsbGFyeVRSVUUiOnt9fX0K