gcp (8 posts)

In writing logs in applications that run on Google Cloud Platform, it requires some configurations to be compiled to trace logs in Cloud Logging. This post describes how to implement it, and also some tips for making logs more useful and informative. Tracked as trace logs in Cloud Logging Node

It used to be that using a load balancer is the most common way to provision a custom domain on Cloud Run. However, it's a bit complicated and costly because it requires a load balancer. In order to have lower running cost, using load balancer should not be the best option. For provisioning custom

Google Cloud offers CDN(content delivery/distributed network) that can be backed by Cloud Storage, a.k.a GCS. Terraform supports provisioning CDN in GCP as always. As well as the previous post, in Terraform, variables should be declared in variables.tf but use locals here instead for simplicity

Google Cloud(GCP) has Identity-Aware Proxy that uses ID and contexts to protect applications and VMs from unexpected access. https://cloud.google.com/iap Thanks to IAP, it's a way easy to protect an application running on Cloud Run by requiring Google login within the organization, for example.

The Google provider of Terraform has some mechanisms to manage Service Accounts in GCP as followings. - [google_service_account_iam](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/google_service_account_iam) - google_service_account_iam_policy - google_servi

As I posted before, this blog is running on GCP Cloud Run and also is built with Next.js. https://blog.petitviolet.net/post/2021-12-28/running-a-blog-powered-by-next.js-on-cloud-run Previously, before migrating to Next.js from Gatsby, this blog used to get deployed automatically via GitHub Action

This blog had been built with [Gatsby](https://nextjs.org), but I decided to migrate to [Next.js](https://nextjs.org) just for learning it. This post is going to describe what the arcitecture is and how to deploy this blog to [GCP Cloud Run](https://cloud.google.com/run) which is a serverless platf

Google AppEngine Standard Environment for Java8 に乗せたアプリケーションで非同期処理しつつログ出力すると、 ログがリクエストに正しく紐付かずに別のリクエストのログとして出力されてしまう、という細かすぎて伝わらない問題と戦った話です。 なお言語は Scala で、[Skinny Micro](http://skinny-framework.org/documentation/micro.html)を使用。 まとめ まず結論。 GAE では独自のスレッドではなくThreadManager.createThreadForCurrentR