Google
docs.cloud.google.com › ruby › running rails on the cloud run environment
Running Rails on the Cloud Run environment | Ruby | Google Cloud Documentation
Learn how to deploy a sample Rails application to Cloud Run and how to integrate managed databases, object storage, encrypted secrets, and build pipelines with serverless compute. Deploying Rails applications involves integrating multiple services together to form a cohesive project. This tutorial assumes that you are familiar with Rails web development. This tutorial requires Ruby 3.0 or later and Rails 8 or later.
Google
docs.cloud.google.com › cloud run › quickstart: build and deploy a ruby web app to google cloud with cloud run
Quickstart: Build and deploy a Ruby web app to Google Cloud with Cloud Run | Google Cloud Documentation
COPY . ./ RUN bundle install # Run the web service on container startup. CMD ["ruby", "./app.rb"]
Videos
Google
docs.cloud.google.com › ruby › running rails on google cloud
Running Rails on Google Cloud | Ruby | Google Cloud Documentation
It's easy to get started developing Ruby on Rails apps that run on Google Cloud.
Google Skills
skills.google › focuses › 20049
Use Ruby on Rails with Cloud SQL for PostgreSQL on Cloud Run | Google Skills
In this lab, you'll learn how to deploy a new Ruby on Rails application using Google Cloud SQL for PostgreSQL on Cloud Run.
GitHub
github.com › mattes › google_cloud_run
GitHub - mattes/google_cloud_run: Rails on Google Cloud Run
Active Job Adapter via Cloud Tasks · Minor patches for better compatibility · Works with Ruby 3 and Rails 6 · logger.info "Hello World" logger.info do "Expensive logging operation, only run when logged" end logger.info "Labels work, too!", my_label: "works", another_one: "great" All Google Cloud Logging Severities are supported: logger.default (or logger.unknown) - The log entry has no assigned severity level.
Starred by 10 users
Forked by 2 users
Languages Ruby 89.5% | HTML 8.2% | JavaScript 1.2% | CSS 1.1% | Ruby 89.5% | HTML 8.2% | JavaScript 1.2% | CSS 1.1%
Google
docs.cloud.google.com › cloud run › the ruby runtime
The Ruby runtime | Cloud Run | Google Cloud Documentation
In the Google Cloud console, go to the Cloud Run page: ... Click Write a function. In the Runtime list, select a Ruby runtime version.
Medium
medium.com › @palladiusbonton › ruby-on-rails-with-postgresql-on-cloud-run-bdaaf0b26e0b
Level Up Your Rails Game with Cloud Run: A Qwiklabs Deep Dive | by Riccardo Carlesso | Medium
August 15, 2024 - In this video, I walk you through me executing the steps described in Ruby on Rails with PostgreSQL on Cloud Run on cloudskillsboost website, encountering a few bumps along the road, and fixing them. Plus I show you my personal Dev Toolchain
Medium
medium.com › @gjcarew › deploying-to-google-cloud-run-980fdbcd7b34
Deploying a Rails app to GCP Cloud Run | by Gavin Carew | Medium
April 17, 2023 - Hopefully, you’ve worked through containerizing a Rails app before getting here. If not, check out part two. Here’s where we put that practice into action, we’re going to deploy to Google Cloud Platform (GCP). Specifically, we’re going to deploy to Cloud Run.
Google
docs.cloud.google.com › developer tools › ruby › client libraries › cloud run v2 api - class google::cloud::run::v2::resourcerequirements (v0.28.0)
Cloud Run V2 API - Class Google::Cloud::Run::V2::ResourceRequirements (v0.28.0) | Ruby client libraries | Google Cloud Documentation
Reference documentation and code samples for the Cloud Run V2 API class Google::Cloud::Run::V2::ResourceRequirements.
Google
docs.cloud.google.com › ruby › run rails 7 on app engine flexible environment
Run Rails 7 on App Engine flexible environment | Ruby | Google Cloud Documentation
Install the Google Cloud CLI. If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity. To initialize the gcloud CLI, run the following command: ... Install Ruby version 3.0 or later.
Google
docs.cloud.google.com › ruby › client libraries
Ruby client libraries | Google Cloud Documentation
This gem is a versioned client. It provides basic client classes for a specific version of the Cloud Run V2 API. Most users should consider using the main client gem, google-cloud-run-client. See the section below titled Which client should I use?
GitHub
github.com › googleapis › google-cloud-ruby
GitHub - googleapis/google-cloud-ruby: Google Cloud Client Library for Ruby · GitHub
Install this library as a RubyGem, or add it to your Gemfile. Most API calls must be accompanied by authentication information proving that the caller has sufficient permissions to make the call. These API client libraries provide several mechanisms for attaching credentials to API calls. If your application runs on an Google Cloud Platform hosting environment such as Google Compute Engine, Google Container Engine, Google App Engine, Google Cloud Run, or Google Cloud Functions, the environment will provide "ambient" credentials which client libraries will recognize and use automatically.
Starred by 1.4K users
Forked by 567 users
Languages Ruby
GitHub
github.com › ejangi › rails-google-cloud-run
GitHub - ejangi/rails-google-cloud-run: A test deployment of a Rails 6 app to Google Cloud Run using Cloud Build · GitHub
A test deployment of a Rails 6 app to Google Cloud Run using Cloud Build - ejangi/rails-google-cloud-run
Author ejangi
Medium
medium.com › google-cloud › ruby-functions-on-cloud-run-db6ea95ad8ac
Ruby Functions on Cloud Run! - by Grant Timmerman
April 22, 2020 - In this blogpost, we’ll walk through how use the Ruby Functions Framework to containerize and deploy a Ruby method to Cloud Run.
Medium
medium.com › google-cloud › google-cloud-run-on-rails-a-real-life-example-part-1-preparing-the-ground-705c94ab8a7a
Google Cloud Run on Rails: a real life example (Part 1: preparing the ground) | by Laurent Julliard | Google Cloud - Community | Medium
May 23, 2019 - Part 1 of this series introduces Cloud Run, guides you through the creation process of you GCP project and lets you choose your work environment. Part 2 covers the Photo Album application and setting up the installation of Ruby and gems as well as running the Photo Album from your local environment (This part is optional and you may skip it altogether if you are not interested in running the Photo Album locally)
Google
docs.cloud.google.com › ruby › getting started with ruby on compute engine
Getting started with Ruby on Compute Engine | Google Cloud Documentation
Installs Ruby 2.6.5, Bundler, and their system dependencies. Clones the app's source code from the Cloud Source Repositories and installs dependencies. Install and configures Nginx. Installs Supervisor to run the app as a daemon.
GitHub
github.com › swfz › cloud-run-ruby-sample
GitHub - swfz/cloud-run-ruby-sample
gcloud config set run/region asia-northeast1 export PROJECT_ID={プロジェクトID} export TOPIC_NAME=run-with-pubsub export PROJECT_NUMBER={プロジェクトナンバー} export INVOKER_ACCOUNT=cloud-run-pubsub-invoker-test export RUN_NAME=pubsub-tutorial # 事前に作っておく export BUCKET={GCSバケット名} gcloud pubsub topics create $TOPIC_NAME gcloud builds submit --tag gcr.io/$PROJECT_ID/pubsub gcloud run deploy $RUN_NAME --image gcr.io/$PROJECT_ID/pubsub --platform managed --region asia-northeast1 --update-env-vars BUCKET=$BUCKET,PROJECT_ID=$PROJECT_ID --timeout 15m export SE
Author swfz
Top answer 1 of 2
3
While running on Cloud Run (or Compute Engine, Kubernetes Engine, App Engine, Cloud Functions...), you don't need to specify any JSON key files (or the GOOGLE_APPLICATION_CREDENTIALS environment variable). All Google Cloud client libraries automatically get credentials (a token) from the compute platform your app is running on.
In fact this gem’s documentation linked to says:
This library uses Service Account credentials to connect to Google Cloud services. When running on Compute Engine the credentials will be discovered automatically
So you should delete that field in the code, and it should be working on Cloud Run just fine.
You need to specify a key file path (or env. variable) if:
- you need want to use a different identity than the default/configured identity of the platform you're running on
- (e.g. in this case service account you configured for the Cloud Run service)
- while running outside Google Cloud
2 of 2
-1
This gem expects a .json service account key path, or an environment variable specifying the path
I was wondering how this could work in a cloudrun context, as the expected environment variable can't reference a static file path.
The value of the GOOGLE_CLOUD_CREDENTIALS environment variable can be: "Path to JSON file, or JSON contents". So if you can't reference a static file path, provide the entire contents of your JSON key file as the value for the environment variable.
See google-cloud-storage Authentication for full docs.