Add deployment instructions for Google Cloud Run

README.md

@@ -141,6 +141,7 @@ LogPaste is easy to deploy to cloud services. Here are some places it works well
 
 * [fly.io](docs/deployment/fly.io.md) (recommended)
 * [Heroku](docs/deployment/heroku.md)
+* [Google Cloud Run](docs/deployment/cloud-run.md)
 * [Amazon LightSail](docs/deployment/lightsail.md)
 
 ## Further reading

docs/deployment/cloud-run.md

@@ -0,0 +1,108 @@
+# Deploy LogPaste to Google Cloud Run
+
+TODO: Finish this, still a work in progress.
+
+## Requirements
+
+* gcloud SDK
+
+## Set variables
+
+```bash
+GCP_PROJECT="your-gcp-project"    # Replace with your GCP project ID
+GCS_BUCKET="your-logpaste-bucket" # Replace with your bucket name
+GCP_REGION="us-east1"             # Replace with your desired GCP region
+```
+
+### Authenticate
+
+You need to authenticate gcloud and configure docker to push to Google Container Registry.
+
+```bash
+gcloud auth login && \
+  gcloud auth configure-docker
+```
+
+### Specify GCP Project
+
+```bash
+gcloud config set project "${GCP_PROJECT}"
+```
+
+### Enable services
+
+Your GCP project will need the [Cloud Run API](https://cloud.google.com/run/docs/reference/rest) enabled, so ensure your project enables this API:
+
+```bash
+gcloud services enable run.googleapis.com
+```
+
+### Create a Google Cloud Storage bucket
+
+If you haven't already created the GCS bucket to provide LogPaste's persistent storage, create it with the command below:
+
+```bash
+gsutil mb "gs://${GCS_BUCKET}"
+```
+
+## Push to Google Container Registry
+
+Cloud Run can't run Docker images from external image repositories, so next you'll copy the official LogPaste image to Google Container Registry:
+
+```bash
+LOGPASTE_VERSION="mtlynch/logpaste:latest"  # LogPaste version on DockerHub
+LOGPASTE_GCR_TAG="logpaste"                 # Change to whatever name you prefer
+LOGPASTE_GCR_URL="gcr.io/${GCP_PROJECT}/${LOGPASTE_GCR_TAG}"
+```
+
+```bash
+docker pull "${LOGPASTE_VERSION}" && \
+  docker tag "${LOGPASTE_VERSION}" "${LOGPASTE_GCR_URL}" && \
+  docker push "${LOGPASTE_GCR_URL}"
+```
+
+## Deploy
+
+Finally, it's time to deploy your image to Cloud Run.
+
+```bash
+GCR_SERVICE_NAME="logpaste"
+gcloud beta run deploy \
+  "${GCR_SERVICE_NAME}" \
+  --image "${LOGPASTE_GCR_URL}" \
+  --set-env-vars "DB_REPLICA_URL=gcs://${GCS_BUCKET}/db" \
+  --allow-unauthenticated \
+  --region "${GCP_REGION}" \
+  --execution-environment gen2 \
+  --no-cpu-throttling
+```
+
+If the deploy is successful, you'll see a message like the following:
+
+```text
+Service [logpaste] revision [logpaste-00002-cos] has been deployed and is serving 100 percent of traffic.
+Service URL: https://logpaste-abc123-ue.a.run.app
+```
+
+Your LogPaste instance will serve at the URL listed next to "Service URL."
+
+On Cloud Run, you'll notice that LogPaste shuts down a few seconds after each request. This is normal. It's persisting all of its data in Google Cloud Storage, and it will start up again upon the next HTTP request it receives with all the same data.
+
+Thanks to [Steren Giannini](https://github.com/steren) from the Google Cloud Run team for his help with these instructions.
+
+## Set custom domain (optional)
+
+You'll need to [verify ownership](https://cloud.google.com/run/docs/mapping-custom-domains#command-line) first.
+
+```bash
+CUSTOM_DOMAIN="logpaste.example.com"
+```
+
+```bash
+gcloud beta run domain-mappings create \
+  --service "${GCR_SERVICE_NAME}" \
+  --domain "${CUSTOM_DOMAIN}" \
+  --region "${GCP_REGION}"
+```
+
+The command will show you a DNS record to add to your DNS. When you add the record, you'll be able to access the Cloud Run instance from your custom domain.