From 6e5094103092a9c4cb5c47eafa33350391680b63 Mon Sep 17 00:00:00 2001 From: NeilClack Date: Fri, 30 Jan 2026 23:33:36 -0600 Subject: [PATCH] Update the action workflow to utilize secrets Instead of managing a .env file on the server, I have begun the migration to Github secrets. This is a tes tto see if I can pass in the Google OAuth client secret. If so, then I can migrate the rest of the environment variables and manage them in one easy place.. I should still keep a record of these somewhere, encrypted, hidden, and safe. --- .github/workflows/deploy.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index f4bda02..cc22418 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -25,4 +25,5 @@ jobs: --network=host \ -v /mnt/volume_nyc3_01/portal/.env:/app/.env:ro \ -v /etc/ssl/certs/Digital_Ocean.crt:/etc/ssl/certs/Digital_Ocean.crt:ro \ + -e GOOGLE_CLIENT_SECRET=${{ secrets.oauth_google_secret }} \ portal:latest