docs: update notes on Plover

This commit is contained in:
Gabriel Arazas 2023-07-02 20:21:49 +08:00
parent c89c29ac10
commit 6bd59ccfd4
No known key found for this signature in database
GPG Key ID: ADE0C41DAB221FCC

View File

@ -33,7 +33,7 @@ To deploy it, just start up a Terraform project as usual (assuming it is run fro
terraform -chdir=./hosts/plover init terraform -chdir=./hosts/plover init
---- ----
There are ways to deploy with the given credentials but the common way to do it with this setup is modifying `.envrc` located at the project root. There are ways to deploy with the given credentials but the common way to do it with this setup is creating a production dotenv (`.production.envrc`) located at the project root.
Just provide the sensitive credentials as an environment variable `TF_VAR_$KEY=$VALUE`. Just provide the sensitive credentials as an environment variable `TF_VAR_$KEY=$VALUE`.
@ -86,9 +86,6 @@ Please activate them and with the right ports.
* Get the appropriate credentials for the following services: * Get the appropriate credentials for the following services:
** An API key from the domain registrar (i.e., Porkbun).
This is used for the certificate generation in case the ACME client went with the DNS-1 challenge.
** An API key/credentials for the email service (i.e., SendGrid). ** An API key/credentials for the email service (i.e., SendGrid).
This is used for setting up configuration for transactional emails used by some of the services such as Gitea and Vaultwarden. This is used for setting up configuration for transactional emails used by some of the services such as Gitea and Vaultwarden.