From d77ad24d784e0c816b9b559ca4d559f0f7a0fe0e Mon Sep 17 00:00:00 2001 From: foormea Date: Sun, 3 May 2020 10:52:39 +0000 Subject: [PATCH] README.md edited online with Bitbucket --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 3e7240c..249b73f 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@ A `flask` route that does the following: ## Setup - WordPress must be set up to send the hook `publish_post` with fields `post_content`, `post_name`, and `post_url` to the URL defined by your network setup. Go to [https:///wp-admin](https:///wp-admin) `> Settings > Webhooks`. -- This is packaged as a Docker container meant to be used together with the [Letsencrypt nginx proxy companion](https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion). This could easily be adjusted to run on a [GCP Cloud Function](https://cloud.google.com/functions/). WordPress doesn't require `https` so this could also easily run as a standalone service at home without much setup. +- This is packaged as a Docker container meant to be used together with the [Letsencrypt nginx proxy companion](https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion) or [linuxserver.io letsencrypt image](https://docs.linuxserver.io/images/docker-letsencrypt). This could easily be adjusted to run on a [GCP Cloud Function](https://cloud.google.com/functions/) or similar. WordPress doesn't require `https` so this could also easily run as a standalone service at home without much setup. - Look through source files for extra info. ## What works, what doesn't