#CloudRun

Guillaume Laforgeglaforge@uwyn.net
2026-02-09

🔐 How are #GoogleAIStudio deployed apps on #CloudRun protecting the API key so it's not visible in the browser? (although it appeared as if Gemini was called from the client-side...)

➡️ A transparent proxy w/ Service Workers & WebSocket interception prevent key exposure!

glaforge.dev/posts/2026/02/09/

:rss: Qiita - 人気の記事qiita@rss-mstdn.studiofreesia.com
2026-01-06
:rss: Qiita - 人気の記事qiita@rss-mstdn.studiofreesia.com
2025-12-23
Return of Aadmaaaadmaa2@mathstodon.xyz
2025-12-09

This week I had a bug where my API container was deploying without incident and crashing a second later when /health was checked. The issue was that the crypto provider was not initialized, which caused a panic as soon as /health was checked - it was an ordinary bug.

Because the container started, but then crashed on health check, and it was deployed to #Google #CloudRun, CloudRun kept restarting the container while I was asleep. And crashing it, hitting /health. Then Google's AI must have seen the word "crypto" in the logs because they turned my project off and I woke up to completely broken infrastructure, and an email that said I was CRYPTOMINING in violation of their FREE use agreement.

Now: (a) they charge me for every millisecond of compute time - this is not free use! and (b) crypto means CRYPTOGRAPHY to normal developers. Not freaking crypto currency mining, which I ain't doing.

So now my service is down and I'm waiting for an appeals process - it's been two days.

This was for a personal project but I can't continue to recommend GCP for organizational folks going forward. it is insane to shut down cloud resources on such a thin fact. This is a single 1-CPU CloudRun service that happens to be cycling due to a bug. Stop the API as failing to start properly, and send an email like a NORMAL PERSON. They could absolutely destroy a business this way.

And I think they also need to count false-positive shut downs as part of their uptime calcs. Because ... it is absolutely down time.

Ugh!

#enshittification #gcp #gcs #google #ai

2025-11-05

Open redirect endpoint in Datasette prior to 0.65.2 and 1.0a21 - Open redirect endpoint in Datasette prior to 0.65.2 and 1.0a21
This GitHub security... - simonwillison.net/2025/Nov/5/o #annotated-release-notes #datasette #security #cloudrun

2025-10-09

Key question: Do you want your developers spending energy on Docker internals, or should a platform team handle this? Or just go with a FaaS framework?

Full tutorial: shinglyu.com/web/2025/10/08/se

:rss: Qiita - 人気の記事qiita@rss-mstdn.studiofreesia.com
2025-10-07
Guillaume Laforgeglaforge@uwyn.net
2025-10-01

📢 Le 4 novembre à Paris, Google organise l'atelier #AccelerateAI avec #CloudRun et #ADK.
Une journée sur le développement et le déploiement d'applications #IA sur Cloud Run.
Par ici pour les inscriptions :
👉 goo.gle/accelerate-ai-paris

:rss: Qiita - 人気の記事qiita@rss-mstdn.studiofreesia.com
2025-09-28

【初心者向け】LINE × ChatGPT × Google Cloud で「会話履歴つきAIチャットボット」を作る方法(Python)
qiita.com/popapipapapi/items/d

#qiita #Python #LINEmessagingAPI #GoogleCloud #CloudRun #ChatGPT

:rss: Qiita - 人気の記事qiita@rss-mstdn.studiofreesia.com
2025-09-11

バッチジョブの監視、諦めてない?New Relic APMで短命プロセスを捉える方法(Cloud Run編)
qiita.com/nr-mito/items/c76d2b

#qiita #Python #NewRelic #Docker #observability #CloudRun

:rss: Qiita - 人気の記事qiita@rss-mstdn.studiofreesia.com
2025-09-09

【GCP初学者向け】Cloud Runでステートフルなセッション管理を実現する完全ガイド
qiita.com/Natsuhi-aruku/items/

#qiita #Redis #GoogleCloud #CloudRun

:rss: Qiita - 人気の記事qiita@rss-mstdn.studiofreesia.com
2025-08-26
Guillaume Laforgeglaforge@uwyn.net
2025-08-01

A proof-of-concept #ADK #AI #Agent code visualizer

glaforge.dev/posts/2025/08/01/

✨ Vibe-coded with Google #AiStudio and #GeminiCLI.
Powered by #Gemini 2.5 Pro.
Using #ReactFlow for the nice node-based UI.
Deployed on #CloudRun ☁️

⚠️ It works for both single-file #Java and #Python ADK multiagents. It doesn't work for projects spanning multiple files or directories.

Guillaume Laforgeglaforge@uwyn.net
2025-07-22

The Sci-Fi naming problem: Are #LLMs less creative than we think?

The most well known LLMs seem to always give the same names to the protagonists of #scifi stories.

Why do they do that? Are they not creative?

Who are Dr Thorne and Anya?

In my AI agent generating sci-fi stories (developed with #langchain4j, deployed on #CloudRun) I was always encountering the same names again and again:

short-ai-story.web.app

Guillaume Laforgeglaforge@uwyn.net
2025-06-09

🧵Building an #MCP server with @quarkusio and deploying on Google #CloudRun

glaforge.dev/posts/2025/06/09/

The @quarkusio support for #MCP is really straightforward: you just need to use the @Tool and @ToolArg annotations to describe methods as MCP tools!

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst