You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then, I built with Cloud Build gcloud builds submit . --tag gcr.io/<PROJECT>/logpaste:latest
And deployed to Cloud Run: gcloud beta run deploy logpaste --image gcr.io/<PROJECT>/logpaste:latest --set-env-vars DB_REPLICA_URL=gcs://<BUCKET>/db --execution-environment gen2 --no-cpu-throttling
I can try to send a PR: we can enable litestream if DB_REPLICA_URL is set, but I'm not sure about the best way handle the translation of envvars to litestream.yml
The text was updated successfully, but these errors were encountered:
Thanks for reporting this and sharing the Google Cloud Run steps, @steren!
I tried your instructions, and it's pretty cool running it on Cloud Run. I was able to deploy successfully after #134 without removing the LITESTREAM lines from litestream.yml. Do you run into issues with those lines?
I successfully deployed logpaste to Google Cloud on Google Cloud Run and Google Cloud Storage
I had the change the code in the following way:
litestream.yml
since litestream is able to pick up credentials from the environment directlyThen, I built with Cloud Build
gcloud builds submit . --tag gcr.io/<PROJECT>/logpaste:latest
And deployed to Cloud Run:
gcloud beta run deploy logpaste --image gcr.io/<PROJECT>/logpaste:latest --set-env-vars DB_REPLICA_URL=gcs://<BUCKET>/db --execution-environment gen2 --no-cpu-throttling
I can try to send a PR: we can enable litestream if
DB_REPLICA_URL
is set, but I'm not sure about the best way handle the translation of envvars tolitestream.yml
The text was updated successfully, but these errors were encountered: