From a7695170a6853647a41b9c0ae7a8e185cfecd5bc Mon Sep 17 00:00:00 2001
From: Samuelodan <35481602+Samuelodan@users.noreply.github.com>
Date: Mon, 13 Mar 2023 05:03:58 +0100
Subject: [PATCH] Update instructions for setting letsencrypt global email

Since there's no instruction for how to use the DOKKU_LETSENCRYPT_EMAIL env variable, I'm not sure why it's included here.
So, instead, I'm proposing to include the step for directly setting the global email for `dokku-letsencrypt`.

(It'll be nice to also get some explanation behind creating that env variable)
---
 docs/deployment/application-deployment.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/deployment/application-deployment.md b/docs/deployment/application-deployment.md
index 07ce90825..3e2a5567e 100644
--- a/docs/deployment/application-deployment.md
+++ b/docs/deployment/application-deployment.md
@@ -125,8 +125,8 @@ As an alternative, the Dokku project offers an optional letsencrypt plugin that
 # plugin installation requires root, hence the user change
 sudo dokku plugin:install https://github.com/dokku/dokku-letsencrypt.git
 
-# configure the plugin
-dokku config:set --global DOKKU_LETSENCRYPT_EMAIL=your-email@your.domain.com
+# set global email for letsencrypt
+dokku letsencrypt:set --global email your-email@your.domain.com
 
 # set a custom domain that you own for your application
 dokku domains:set ruby-getting-started ruby-getting-started.your.domain.com