From 94ad81274d3847c4d870f95c69689d09153573f2 Mon Sep 17 00:00:00 2001 From: taitus Date: Fri, 27 Sep 2024 12:42:02 +0200 Subject: [PATCH] Add consistency to Omniauth keys in secrets.yml.example The keys to configure Omniauth for WordPress were only added to the production environment, so we unified all the keys across the staging and preproduction environments. --- config/secrets.yml.example | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/config/secrets.yml.example b/config/secrets.yml.example index b395b0266..b785db667 100644 --- a/config/secrets.yml.example +++ b/config/secrets.yml.example @@ -78,6 +78,15 @@ staging: # # Currently you can overwrite SMTP, SMS, manager, microsoft API, # HTTP basic, twitter, facebook, google, wordpress and security settings. + twitter_key: "" + twitter_secret: "" + facebook_key: "" + facebook_secret: "" + google_oauth2_key: "" + google_oauth2_secret: "" + wordpress_oauth2_key: "" + wordpress_oauth2_secret: "" + wordpress_oauth2_site: "" <<: *maps <<: *apis @@ -129,6 +138,9 @@ preproduction: facebook_secret: "" google_oauth2_key: "" google_oauth2_secret: "" + wordpress_oauth2_key: "" + wordpress_oauth2_secret: "" + wordpress_oauth2_site: "" <<: *maps <<: *apis