31–40 of 101 posts
Earlier quoted context omitted.
is gRPC supported now or is that more of an upstream HTTP 1.1 constraint?
Inbound GRPC will be limited to HTTP1.1; that's a limitation of the platform rather than the language runtime. We're working on HTTP2 support, but I can't promise any timelines.
Earlier quoted context omitted.
Inbound GRPC will be limited to HTTP1.1; that's a limitation of the platform rather than the language runtime. We're working on HTTP2 support, but I can't promise any timelines.
By inbound GRPC you mean when running an app engine instance as a client right? So running a GRPC server is completely out of question still I would presume?
I’m assuming urlfetcher is deprecated now too? I’ll go read the migration guide now ...
Awesome work! Love Go and GAE! Very happy so far.
Earlier quoted context omitted.
when will appengine support setting environment variables with gcloud command or inside the gcloud console instead of in the app.yaml, i.e. so that each environment can have their own variables without copying app.yaml's?!
(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
This actually seemed to be live a week or two ago, I managed to run Miniflux [1] on App Engine with no changes though to get it working properly it would need it's scheduling changing. [1] - https://github.com/miniflux/miniflux
(App Engine PM here) Nice to hear! Yes indeed, we announced Go 1.11 on App Engine last week at Cloud Next London.
Hmm, I was just running into some context annoyances but this seems to remedy some nuances regarding that. Cool! Good timing! I’m assuming urlfetcher is deprecated now too? I’ll go read the migration guide now ... Awesome work! Love Go and GAE! Very happy so far.
Glad you're enjoying both Go and GAE!
I'm the tech lead and primary software engineer on the Go runtime. If you have any questions, please don't hesitate to ask! I'm super thrilled to announce that Go 1.11 is now available on App Engine! We now support... * vendoring * regular best-practice package structures * go modules * the regular Google Cloud client libraries: https://github.com/GoogleCloudPlatform/google-cloud-go This is a "second-generation" runt…
Earlier quoted context omitted.
It's always been my impression that Go on GAE is the most lightweight compared to Java/Python, as it not "memory hungry" like Java nor "slow" like Python. Am I correct?
It is quite lightweight, yes! Though...I wouldn't necessarily call Python slow! Python keeps getting faster, and we now support Python 3.7 on our second gen runtimes: https://cloud.google.com/blog/products/gcp/introducing-app-e...
Python might be perfectly acceptable of course.
Earlier quoted context omitted.
(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
Not worried about secrets in repo?
You definitely don't want to check secrets into the repo for the same reason you don't set them as environment variables: It's not secure. The solution is to use Cloud Key Management Service. More info here: https://cloud.google.com/kms/ We use that to either store secrets directly, or to decrypt encrypted entities in a DB (e.g. Datastore).
You can see how we use it here (our project is open source): https://github.com/google/nomulus/tree/master/java/google/re...
I’m curious because now it’s seems like there are 3 solutions. Although I really like the simplicity of this solution and the modernizing from the constraints of true classic mode.