Re: [google-appengine] Re: app.yaml resources suggestions for static hosting

2017-07-26 Thread A. Kong
With the google cloud storage option to serve static files, what is the best way to manage it with the local development environment? Background: I am thinking of switching from standard to flex environment. I am using python runtime, so the switch can let me to switch from python 2.7 to

Re: [google-appengine] Re: app.yaml resources suggestions for static hosting

2017-07-26 Thread A. Kong
With the google cloud storage option to serve static files, what is the best way to manage it with the local development environment? Background: I am thinking of switch from standard to flex environment using python. I use webpack to emit a final bundled javascript. In a standard environment

Re: [google-appengine] Re: app.yaml resources suggestions for static hosting

2017-05-15 Thread 'Alex Martelli' via Google App Engine
Another possibility for a static-only site, recommended for example in the short, useful video Moving existing applications to Google Cloud Platform , is to use Google Cloud Storage

[google-appengine] Re: app.yaml resources suggestions for static hosting

2017-05-15 Thread Blaine Garrett
If you are only doing static code (i.e. express is just serving files), you may consider just using a standard env (python or go for simplicity). From my understanding Flex env will add a fair amount of overhead. I started a github project years ago for this purpose:

[google-appengine] Re: app.yaml resources suggestions for static hosting

2017-05-12 Thread Attila-Mihaly Balazs
AFAIK two big limitations of the FLEX environment are the slow startup of new instances (10s of seconds vs. under 1 second for AppEngine Standard) and the fact that the default images are all configured to serve requests sequentially. You almost surely be better off moving the static files to

[google-appengine] Re: app.yaml resources suggestions for static hosting

2017-05-11 Thread E EE
30 requests per second for static resources is small enough to be insignificant. You should be able to serve it happily with a micro instance, so something seems very wrong here. It is possible that app engine has a lot of latency, so out of those 100ms, only 1ms or less is spent in your web