steren

14 ms·

121.
by steren 8y ago
I recommend starting by asking your questions on StackOverflow or other public forums. Many googlers (including me) are very active on StackOverflow and monitoring specific tags. For Cloud Run, please use `google-cloud-run`.
122.
by steren 8y ago
Hi, I'm a product manager on Cloud Run. Thanks for your enthusiasm and feedback. We are very excited to share this new product with you. The reason we remain silent at the moment is because Cloud Run will officially be announced at 9am
123.
by steren 8y ago
New features is different from software change. A UI might stay identical while the entire software is rewritten.
124.
Node.js 10 Available for App Engine, in Lockstep with Long Term Support(cloud.google.com)
4 points by steren 8y ago|0 comments
125.
by steren 8y ago
(App Engine PM here) The App Engine APIs will be present in the Go 1.11 runtime when it goes GA and until it is turned down. We do not know exactly which future version of the runtime will stop supporting them. We are working on Google Clou
126.
by steren 8y ago
(App Engine PM here) Nice to hear! Yes indeed, we announced Go 1.11 on App Engine last week at Cloud Next London.
127.
by steren 8y ago
(App Engine PM here) At this time, app.yaml is the only way to set env vars. If you want to separate environments, you could use different .yaml files, I personally use app.staging.yaml and app.prod.yaml
128.
by steren 8y ago
Hi (App Engine PM here) You can use any go package in the Go 1.11 runtime, including the ones relying on GRPC. Did I answer your question?
129.
by steren 8y ago
Hi (App Engine PM here). Yes both libraries connect to the same database (Cloud Datastore). cloud.google.com/go/datastore is preferred as it uses the Cloud Datastore API instead of the App Engine specific API, so your code will be
130.
Go 1.11 on App Engine(cloud.google.com)
4 points by steren 8y ago|1 comments
131.
GCP Cloud Tasks, a task queue service for new App Engine runtimes(cloud.google.com)
4 points by steren 8y ago|0 comments
132.
by steren 8y ago
GCF is now Generally Available. And to sign up for serverless containers: https://g.co/serverlesscontainers (I am a PM on GCP)
133.
Headless Chrome support in Cloud Functions and App Engine(cloud.google.com)
5 points by steren 8y ago|0 comments
134.
Google Cloud Functions is Now Generally Available(cloud.google.com)
7 points by steren 8y ago|0 comments
135.
by steren 8y ago
Google Cloud Platform offers https://www.zyncrender.com/
136.
Serverless announcements from Google Cloud Next 2018(cloudplatform.googleblog.com)
56 points by steren 8y ago|10 comments
137.
by steren 8y ago
Yes, Node.js on GAE Standard comes with all the OS packages needed to run Headless Chrome. Learn more at https://cloud.google.com/appengine/docs/standard/nodejs/usin...
138.
by steren 8y ago
(PM in the team) Both runtimes are using the same autoscaler, we recently updated it: https://cloudplatform.googleblog.com/2018/05/Increase-perfor...
139.
by steren 8y ago
(Pm on the team) App Engine Standard does not support websockets at the moment.
140.
by steren 8y ago
(PM here), if you share a GitHub repository that reproduce the issue, we can investigate and fix issues. Be sure to perform the build step before deploying.
141.
by steren 8y ago
(PM on the team) These are not incompatible, you can use Firebase authentication with App Engine. Get started at https://firebase.google.com/docs/auth/ . The firebase Authentication Admin SDK has a Node.js client l
142.
by steren 8y ago
(PM on the team) Migrating from Node.js flexible to Node.js standard should be pretty straightforward. Chances are you only need to perform a new deployment and remove `env: flex` in your app.yaml.
143.
by steren 8y ago
(PM on the team) Good catch, I'm sending a pull request.
144.
by steren 8y ago
(PM on the team) To be able to deliver Node.js on App Engine Standard, we had to develop an entirely new sandbox environment. You can learn more about it by watching this I/O talk (starting at 15min): https://youtu.be/o
145.
by steren 8y ago
(PM on the team) Thanks! Also, subsequent deployments are faster than the first thanks to some caching in the build process.
146.
by steren 8y ago
(PM on the team) App Engine is designed for stateless HTTP workloads. for an email or DNS server, I recommend using Google Kubernetes Engine or Google Compute Engine.
147.
by steren 8y ago
(PM on the team) This page details the differences and why you would pick one over the other: https://cloud.google.com/appengine/docs/nodejs/
148.
Node.js is now available on App Engine standard environment(cloudplatform.googleblog.com)
310 points by steren 8y ago|112 comments
149.
by steren 9y ago
In the browser != Requires connection.
150.
by steren 9y ago
Are you on Windows? If so, Bazel now bundles the JDK so you should not have to worry about Java.

More ›