Update mailjet bundle configuration

Add configuration for debug capabilities offered by mailjet

complete documentation
This commit is contained in:
Nicolas Thal
2018-10-18 17:38:58 +02:00
parent f31445f5de
commit d219ef7323
3 changed files with 29 additions and 0 deletions
@@ -0,0 +1,6 @@
dekalee_mailjet:
api_key: '%env(DEKALEE_MAILJET_API_KEY)%'
secret_key: '%env(DEKALEE_MAILJET_SECRET_KEY)%'
base_template_id: '%env(DEKALEE_MAILJET_BASE_TEMPLATE_ID)%'
email_reporting: '%env(DEKALEE_MAILJET_EMAIL_REPORTING)%'
force_deliver: %env(DEKALEE_MAILJET_FORCE_DELIVER)%
+15
View File
@@ -0,0 +1,15 @@
{
"bundles": {
"Dekalee\\MailjetBundle\\DekaleeMailjetBundle": ["all"]
},
"copy-from-recipe": {
"config/": "%CONFIG_DIR%/"
},
"env": {
"DEKALEE_MAILJET_API_KEY": "your-api_key",
"DEKALEE_MAILJET_SECRET_KEY": "@@your-secret_key",
"DEKALEE_MAILJET_BASE_TEMPLATE_ID": "your_base_template_id",
"DEKALEE_MAILJET_EMAIL_REPORTING": "your_reporting_email",
"DEKALEE_MAILJET_FORCE_DELIVER": "false"
}
}
@@ -0,0 +1,8 @@
<bg=blue;fg=white> </>
<bg=blue;fg=white> DekaleeMailjet, What's next? </>
<bg=blue;fg=white> </>
* The Dekalee/MailjetBundle needs your mailjet configuration.
Modify your DEKALEE_MAILJET_API_KEY, DEKALEE_MAILJET_SECRET_KEY,
DEKALEE_MAILJET_BASE_TEMPLATE_ID, DEKALEE_MAILJET_EMAIL_REPORTING,
and DEKALEE_MAILJET_FORCE_DELIVER config in <fg=green>.env</>