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.
This commit is contained in:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user