From 5525a9021ed197d3f6edb488d37cd371c18a73c8 Mon Sep 17 00:00:00 2001 From: Justin Mayer Date: Wed, 19 Jun 2019 15:45:32 +0200 Subject: [PATCH] Use OUTPUT_PATH setting in Invoke tasks.py template The default setting for OUTPUT_PATH is already 'output', so it would be more DRY to use the existing default value instead of a hardcoded 'output' string. --- pelican/tools/templates/tasks.py.jinja2 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pelican/tools/templates/tasks.py.jinja2 b/pelican/tools/templates/tasks.py.jinja2 index ef48e968..80bd2ae3 100644 --- a/pelican/tools/templates/tasks.py.jinja2 +++ b/pelican/tools/templates/tasks.py.jinja2 @@ -16,8 +16,8 @@ LOCAL_SETTINGS = get_settings_from_file('pelicanconf.py') SETTINGS.update(LOCAL_SETTINGS) CONFIG = { - # Local path configuration (can be absolute or relative to tasks.py) - 'deploy_path': 'output', + # Output path. Can be absolute or relative to tasks.py. Default: 'output' + 'deploy_path': SETTINGS['OUTPUT_PATH'], {% if ssh %} # Remote server configuration 'production': '{{ssh_user}}@{{ssh_host}}:{{ssh_port}}',