[gimp-web/testing] pelicanconf: RELATIVE_URLS also FALSE on testing.
- From: Jehan <jehanp src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gimp-web/testing] pelicanconf: RELATIVE_URLS also FALSE on testing.
- Date: Sat, 1 Feb 2020 14:57:51 +0000 (UTC)
commit f6504f9d475d468772d5b81dcce0cd623f62873e
Author: Jehan <jehan girinstud io>
Date: Sat Feb 1 15:55:45 2020 +0100
pelicanconf: RELATIVE_URLS also FALSE on testing.
Testing and production should be as close as possible. It makes sense to
set relative urls on a local dev environment, but not when published to
testing website (as well as for the production website).
Let's change this, as confirmed with Patdavid input.
pelicanconf_common.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
diff --git a/pelicanconf_common.py b/pelicanconf_common.py
index e8f235b6..d0381788 100644
--- a/pelicanconf_common.py
+++ b/pelicanconf_common.py
@@ -64,7 +64,7 @@ def customize_environment(environment):
# When developing, you probably want document relative URLs - so set this to True
# When publishing, set to False
- RELATIVE_URLS = False if environment == 'production' else True
+ RELATIVE_URLS = True if environment == 'local' else False
if environment != 'production':
# Not sure why, but production pelicanconf didn't have .htaccess
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]