[google-appengine] Re: How use Celery on appengine flexible with a django app

2018-07-10 Thread 'Katayoon (Cloud Platform Support)' via Google App Engine
Hi Julio, Yes, you need to create a custom runtime to include additional components like Celery by creating your base image and using a Dockerfile that configures the

[google-appengine] Re: Unable to download file from google cloud storage with it's original name.

2018-07-10 Thread diogoalmeida via Google App Engine
Most probably the issue is that your code may be using the open method, which sets the mode default to read-only. Less likely, you are trying to save the file to

[google-appengine] Re: Unable to download file from google cloud storage with it's original name.

2018-07-10 Thread diogoalmeida via Google App Engine
Most probably the issue is that your code may be using the open method, which sets the mode default to read-only. Less likely, you are trying to save the file to

Re: [google-appengine] Re: Node.js standard and urlfetch

2018-07-10 Thread Aleksander Efremov
But yes, you're correct. Only for me is more important a streaming between the client and the my app. вт, 10 июл. 2018 г., 23:40 Aleksander Efremov : > > https://cloud.google.com/appengine/docs/standard/nodejs/how-requests-are-handled > > Streaming Responses > > App Engine does not support

Re: [google-appengine] Re: Node.js standard and urlfetch

2018-07-10 Thread Aleksander Efremov
https://cloud.google.com/appengine/docs/standard/nodejs/how-requests-are-handled Streaming Responses App Engine does not support streaming responses where data is sent in incremental chunks to the client while a request is being processed. All data from your code is collected as described above

[google-appengine] How use Celery on appengine flexible with a django app

2018-07-10 Thread Julio Brito
Hi can anybody help me how use Celery on App Engine flexible. my problem exact is how start Celery maybe i need to use Custom and genarate the Dockerfile? is a django app. Thanks. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To

Re: [google-appengine] Re: Node.js standard and urlfetch

2018-07-10 Thread Jason Collins
Streaming doesn't work for inbound requests (i.e., requests from a client to your App Engine app), but should work fine for outbound requests originating from your App Engine app to another server. On Mon, 9 Jul 2018 at 22:11 Aleksander Efremov wrote: > Yes, I use `http`/`https` native

[google-appengine] Re: Google App Engine Upload File to API Directory

2018-07-10 Thread 'George (Cloud Platform Support)' via Google App Engine
In case of an app deployed in the Cloud, the local filesystem that your application is deployed to is not writeable. This behavior ensures the security and scalability of your application. Why reading the file from GS represents a problem? Are there speed or otherwise performance

[google-appengine] Re: Unable to download file from google cloud storage with it's original name.

2018-07-10 Thread Nagaraju Devisetti
I am getting Read-only file system bug with cloud storage. Traceback (most recent call last): File "C:\Program Files\Google\google_appengine\lib\webapp2-2.5.2\webapp2.py", line 1535, in __call__ rv = self.handle_exception(request, response, e) File "C:\Program

[google-appengine] Re: browsing UK sites using google cloud server

2018-07-10 Thread 'Kenworth (Google Cloud Platform)' via Google App Engine
All the IP addresses Google provides to GCP users are registered in the Google HQ in Mountain View, California. Thus, all geolocations lookup of the IP addresses will resolve to the United States even though the actual server is located somewhere else (in your case UK). This explains why you

Re: [google-appengine] Node.js On Standard App Engine - Requires Enabling Billing?

2018-07-10 Thread PhistucK
Thank you for the update! I switched to using Heroku for now (thankfully, my application had almost no dependencies on App Engine or almost anything else, that it was a less than half an hour job to switch providers. The only thing I really had to do was to "re-implement"