.env.example

# Usage:
# Copy this file as `.env` and fill in the variables below as instructed.

# If you are developing more than one plugin, you can store the bin path and 
# profile path in the system environment variables, which can be omitted here.

# The path of the Zotero binary file.
# The path delimiter should be escaped as `\\` for win32. 
# The path is `*/Zotero.app/Contents/MacOS/zotero` for MacOS.
ZOTERO_PLUGIN_ZOTERO_BIN_PATH=/path/to/zotero

# The path of the profile used for development.
# Start the profile manager by `/path/to/zotero.exe -p` to create a profile for development.
# @see https://www.zotero.org/support/kb/profile_directory
# @see https://www.zotero.org/support/kb/multiple_profiles
ZOTERO_PLUGIN_PROFILE_PATH=/path/to/profile

# The directory where the database is located.
# If this field is kept empty, Zotero will start with the default data.
# @see https://www.zotero.org/support/zotero_data
ZOTERO_PLUGIN_DATA_DIR=

# Custom commands to kill Zotero processes.
# Commands for different platforms are already built into zotero-plugin, 
# if the built-in commands are not suitable for your needs, please modify this variable.
# ZOTERO_PLUGIN_KILL_COMMAND=

# Remote Linux UI/debug helper options used by scripts/zotero-remote-debug.sh.
# These are optional. Defaults are shown here.
ZOTERO_REMOTE_DISPLAY=:99
ZOTERO_REMOTE_RESOLUTION=1920x1080x24
ZOTERO_REMOTE_VNC_PORT=5901
ZOTERO_REMOTE_VNC=1
ZOTERO_REMOTE_NOVNC=1
ZOTERO_REMOTE_NOVNC_PORT=6080

# If ZOTERO_PLUGIN_ZOTERO_BIN_PATH is replaced by the helper's wrapper at runtime,
# set this to the real Zotero binary. Usually the helper resolves it automatically.
# ZOTERO_REAL_BIN_PATH=/path/to/zotero

# GitHub Token
# For release-it auto create release and upload assets
# GITHUB_TOKEN =