#cloudrun — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #cloudrun, aggregated by home.social.
-
Using HTTP/2 Cleartext for a server in Go 1.24
https://www.clarityboss.com/blog/go-http2-cleartext-h2c-cloud-run
-
Using HTTP/2 Cleartext for a server in Go 1.24
https://www.clarityboss.com/blog/go-http2-cleartext-h2c-cloud-run
-
Using HTTP/2 Cleartext for a server in Go 1.24
https://www.clarityboss.com/blog/go-http2-cleartext-h2c-cloud-run
-
Using HTTP/2 Cleartext for a server in Go 1.24
https://www.clarityboss.com/blog/go-http2-cleartext-h2c-cloud-run
-
Using HTTP/2 Cleartext for a server in Go 1.24
https://www.clarityboss.com/blog/go-http2-cleartext-h2c-cloud-run
-
Cloud Run の Probe 設計：gRPC 未実装・Distroless・ポートなし Job、それぞれの代替策
https://qiita.com/chinen-gmoconnect/items/4e2c8cc6b4271149f2ea?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
Cloud Run の Probe 設計：gRPC 未実装・Distroless・ポートなし Job、それぞれの代替策
https://qiita.com/chinen-gmoconnect/items/4e2c8cc6b4271149f2ea?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
Cloud Run meets legacy tech - and the results were complicated. ☁️
I spent last night dockerizing Geneweb 6.08 to run on GCP for @geneee. While I successfully got the service live, the auto-scaling performance and memory handling didn't quite hit the mark, even with Apache in the mix.
It seems this specific legacy version has reached its ceiling. I am pausing here, the search continues.
What is your go-to tech for legacy scaling? 🚀
-
Cloud Run meets legacy tech - and the results were complicated. ☁️
I spent last night dockerizing Geneweb 6.08 to run on GCP for @geneee. While I successfully got the service live, the auto-scaling performance and memory handling didn't quite hit the mark, even with Apache in the mix.
It seems this specific legacy version has reached its ceiling. I am pausing here, the search continues.
What is your go-to tech for legacy scaling? 🚀
-
Cloud Run meets legacy tech - and the results were complicated. ☁️
I spent last night dockerizing Geneweb 6.08 to run on GCP for @geneee. While I successfully got the service live, the auto-scaling performance and memory handling didn't quite hit the mark, even with Apache in the mix.
It seems this specific legacy version has reached its ceiling. I am pausing here, the search continues.
What is your go-to tech for legacy scaling? 🚀
-
Cloud Run meets legacy tech - and the results were complicated. ☁️
I spent last night dockerizing Geneweb 6.08 to run on GCP for @geneee. While I successfully got the service live, the auto-scaling performance and memory handling didn't quite hit the mark, even with Apache in the mix.
It seems this specific legacy version has reached its ceiling. I am pausing here, the search continues.
What is your go-to tech for legacy scaling? 🚀
-
🔐 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!
-
🔐 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!
-
🔐 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!
-
🔐 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!
-
🔐 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!
-
Boniface.dev ra mắt portfolio AI “Mission Control” tích hợp Google Gemini, triển khai trên Cloud Run. Dùng Nexus AI để hỏi‑đáp dự án, giải thích kiến trúc, RAG và khung agent. Frontend React/Next.js, backend Node + FastAPI, Docker, IAM bảo mật. Thể hiện thiết kế “purpose‑first”, autoscaling và HTTPS. #AI #GenAI #GoogleGemini #CloudRun #Tech #Portfolio #CôngNghệ #TríTuệNhânTạo
-
Boniface.dev ra mắt portfolio AI “Mission Control” tích hợp Google Gemini, triển khai trên Cloud Run. Dùng Nexus AI để hỏi‑đáp dự án, giải thích kiến trúc, RAG và khung agent. Frontend React/Next.js, backend Node + FastAPI, Docker, IAM bảo mật. Thể hiện thiết kế “purpose‑first”, autoscaling và HTTPS. #AI #GenAI #GoogleGemini #CloudRun #Tech #Portfolio #CôngNghệ #TríTuệNhânTạo
-
Boniface.dev ra mắt portfolio AI “Mission Control” tích hợp Google Gemini, triển khai trên Cloud Run. Dùng Nexus AI để hỏi‑đáp dự án, giải thích kiến trúc, RAG và khung agent. Frontend React/Next.js, backend Node + FastAPI, Docker, IAM bảo mật. Thể hiện thiết kế “purpose‑first”, autoscaling và HTTPS. #AI #GenAI #GoogleGemini #CloudRun #Tech #Portfolio #CôngNghệ #TríTuệNhânTạo
-
Boniface.dev ra mắt portfolio AI “Mission Control” tích hợp Google Gemini, triển khai trên Cloud Run. Dùng Nexus AI để hỏi‑đáp dự án, giải thích kiến trúc, RAG và khung agent. Frontend React/Next.js, backend Node + FastAPI, Docker, IAM bảo mật. Thể hiện thiết kế “purpose‑first”, autoscaling và HTTPS. #AI #GenAI #GoogleGemini #CloudRun #Tech #Portfolio #CôngNghệ #TríTuệNhânTạo
-
Boniface.dev ra mắt portfolio AI “Mission Control” tích hợp Google Gemini, triển khai trên Cloud Run. Dùng Nexus AI để hỏi‑đáp dự án, giải thích kiến trúc, RAG và khung agent. Frontend React/Next.js, backend Node + FastAPI, Docker, IAM bảo mật. Thể hiện thiết kế “purpose‑first”, autoscaling và HTTPS. #AI #GenAI #GoogleGemini #CloudRun #Tech #Portfolio #CôngNghệ #TríTuệNhânTạo
-
【Google Cloud 】Private Service Connect を使ってVPC間の内部通信をする
https://qiita.com/aaaabbbbb/items/604140a1050a71c35aa6?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
【Google Cloud 】Private Service Connect を使ってVPC間の内部通信をする
https://qiita.com/aaaabbbbb/items/604140a1050a71c35aa6?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
Cloud Runのアクセス制御を完全理解する（Ingress / IAM / Cloud Armor / IAP）
https://qiita.com/created_on_june_19/items/ed7d16eda2264ba690bb?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
Cloud Runのアクセス制御を完全理解する（Ingress / IAM / Cloud Armor / IAP）
https://qiita.com/created_on_june_19/items/ed7d16eda2264ba690bb?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
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!
-
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!
-
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!
-
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!
-
Kubernetes có thực sự cần thiết?
Đối với hầu hết các workload phổ biến (API, services), các nền tảng của cloud như ECS/Fargate hay Cloud Run thường rẻ hơn, hiệu quả hơn và giảm gánh nặng vận hành.
Hãy chọn Kubernetes khi bạn có nhu cầu rõ ràng: di động đa đám mây (multi-cloud), tùy chỉnh sâu, hoặc xây dựng platform nội bộ. Đừng chạy theo 'trend' mà hãy chọn giải pháp phù hợp nhất.
#Kubernetes #DevOps #Cloud #SysAdmin #K8s #CôngNghệ #LậpTrình
#CloudComputing #ECS #Fargate #CloudRun #Tech #Plat -
Kubernetes có thực sự cần thiết?
Đối với hầu hết các workload phổ biến (API, services), các nền tảng của cloud như ECS/Fargate hay Cloud Run thường rẻ hơn, hiệu quả hơn và giảm gánh nặng vận hành.
Hãy chọn Kubernetes khi bạn có nhu cầu rõ ràng: di động đa đám mây (multi-cloud), tùy chỉnh sâu, hoặc xây dựng platform nội bộ. Đừng chạy theo 'trend' mà hãy chọn giải pháp phù hợp nhất.
#Kubernetes #DevOps #Cloud #SysAdmin #K8s #CôngNghệ #LậpTrình
#CloudComputing #ECS #Fargate #CloudRun #Tech #Plat -
Kubernetes có thực sự cần thiết?
Đối với hầu hết các workload phổ biến (API, services), các nền tảng của cloud như ECS/Fargate hay Cloud Run thường rẻ hơn, hiệu quả hơn và giảm gánh nặng vận hành.
Hãy chọn Kubernetes khi bạn có nhu cầu rõ ràng: di động đa đám mây (multi-cloud), tùy chỉnh sâu, hoặc xây dựng platform nội bộ. Đừng chạy theo 'trend' mà hãy chọn giải pháp phù hợp nhất.
#Kubernetes #DevOps #Cloud #SysAdmin #K8s #CôngNghệ #LậpTrình
#CloudComputing #ECS #Fargate #CloudRun #Tech #Plat -
Kubernetes có thực sự cần thiết?
Đối với hầu hết các workload phổ biến (API, services), các nền tảng của cloud như ECS/Fargate hay Cloud Run thường rẻ hơn, hiệu quả hơn và giảm gánh nặng vận hành.
Hãy chọn Kubernetes khi bạn có nhu cầu rõ ràng: di động đa đám mây (multi-cloud), tùy chỉnh sâu, hoặc xây dựng platform nội bộ. Đừng chạy theo 'trend' mà hãy chọn giải pháp phù hợp nhất.
#Kubernetes #DevOps #Cloud #SysAdmin #K8s #CôngNghệ #LậpTrình
#CloudComputing #ECS #Fargate #CloudRun #Tech #Plat -
Kubernetes có thực sự cần thiết?
Đối với hầu hết các workload phổ biến (API, services), các nền tảng của cloud như ECS/Fargate hay Cloud Run thường rẻ hơn, hiệu quả hơn và giảm gánh nặng vận hành.
Hãy chọn Kubernetes khi bạn có nhu cầu rõ ràng: di động đa đám mây (multi-cloud), tùy chỉnh sâu, hoặc xây dựng platform nội bộ. Đừng chạy theo 'trend' mà hãy chọn giải pháp phù hợp nhất.
#Kubernetes #DevOps #Cloud #SysAdmin #K8s #CôngNghệ #LậpTrình
#CloudComputing #ECS #Fargate #CloudRun #Tech #Plat -
React × Hono × Docker × Cloud Runではじめて自前APIサーバーを構築した話
https://qiita.com/kikotkk/items/5d1e14d0ada3075f384f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
React × Hono × Docker × Cloud Runではじめて自前APIサーバーを構築した話
https://qiita.com/kikotkk/items/5d1e14d0ada3075f384f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
📢 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 :
👉 https://goo.gle/accelerate-ai-paris -
📢 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 :
👉 https://goo.gle/accelerate-ai-paris -
📢 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 :
👉 https://goo.gle/accelerate-ai-paris -
📢 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 :
👉 https://goo.gle/accelerate-ai-paris -
📢 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 :
👉 https://goo.gle/accelerate-ai-paris -
【初心者向け】LINE × ChatGPT × Google Cloud で「会話履歴つきAIチャットボット」を作る方法（Python）
https://qiita.com/popapipapapi/items/d6386680f5987c671e01?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items#qiita #Python #LINEmessagingAPI #GoogleCloud #CloudRun #ChatGPT
-
【初心者向け】LINE × ChatGPT × Google Cloud で「会話履歴つきAIチャットボット」を作る方法（Python）
https://qiita.com/popapipapapi/items/d6386680f5987c671e01?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items#qiita #Python #LINEmessagingAPI #GoogleCloud #CloudRun #ChatGPT
-
バッチジョブの監視、諦めてない？New Relic APMで短命プロセスを捉える方法（Cloud Run編）
https://qiita.com/nr-mito/items/c76d2b80ec4cb30436c6?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
バッチジョブの監視、諦めてない？New Relic APMで短命プロセスを捉える方法（Cloud Run編）
https://qiita.com/nr-mito/items/c76d2b80ec4cb30436c6?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items