Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not assume S3 #133

Closed
steren opened this issue Dec 4, 2021 · 2 comments
Closed

Do not assume S3 #133

steren opened this issue Dec 4, 2021 · 2 comments

Comments

@steren
Copy link

steren commented Dec 4, 2021

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:

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

@mtlynch
Copy link
Owner

mtlynch commented Dec 5, 2021

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'm adding instructions for Cloud Run here: #135

@steren
Copy link
Author

steren commented Dec 5, 2021

Great to hear the changes to litestream.yml aren't needed, I guess they aren't picked up if the values are empty.

I left a few comments on the guide. Thanks for writing!

@steren steren closed this as completed Dec 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants