1
0
mirror of https://github.com/jcwimer/wrestlingApp synced 2026-03-24 17:04:43 +00:00

Added email address variable

This commit is contained in:
2019-12-31 07:52:31 -05:00
parent e2ec1d4a8a
commit e37281771d
5 changed files with 18 additions and 3 deletions

View File

@@ -28,5 +28,7 @@ Each push to master updates the docker `prod` tag and also pushes a tag with the
Right now, mariadb's root password comes from the secrets.yaml and wrestlingdev uses the root password to run. Ideally, you'd create another secret for mariadb's root password and you'd create a user specifically for wrestlingdev.
From a mysql shell> `CREATE USER ${username} IDENTIFIED BY '${password}'; GRANT ALL PRIVILEGES ON ${database}.* TO ${username}; FLUSH PRIVILEGES;` $database would be wrestlingdev. I'll do this automatically later.
Right now, we're also only using gmail for email.
## Recommended cloud machines
In production, this runs on GKE. I have two node pools. The first is 2 x `n2-high-cpu-2` ($12.63/month preemptible). That pool can run 1 "copy" of the application. That means 2 x app pods, 1 x worker, 1 x memcached, and 1 x mariadb. The second node pool is an autoscale from 0-10 and is of the machine type `n1-standard-1` ($7.30/ month preemptible). This pool is scritly for scaling the app pods and the worker pods.

View File

@@ -68,6 +68,16 @@ spec:
secretKeyRef:
name: wrestlingdev-secrets
key: railssecretkey
- name: WRESTLINGDEV_EMAIL_PWD
valueFrom:
secretKeyRef:
name: wrestlingdev-secrets
key: gmailpassword
- name: WRESTLINGDEV_EMAIL
valueFrom:
secretKeyRef:
name: wrestlingdev-secrets
key: gmailemail
resources:
limits:
cpu: "0.5"

View File

@@ -8,4 +8,6 @@ stringData:
dbusername: root
dbpassword: PUT_SECRET_HERE
devisesecretkey: PUT_SECRET_HERE get from running rails secret
railssecretkey: PUT_SECRET_HERE get from running rails secret
railssecretkey: PUT_SECRET_HERE get from running rails secret
emailpassword: PUT_EMAIL_PASSWORD_HERE
gmailemail: PUT EMAIL ADDRESS HERE