[google-appengine] Re: Best solution / practice for temp files with App Engine PHP?

No way to create it - you'll need a new app instead. On Friday, 19 June 2015 08:13:46 UTC+10, Alex Kerr wrote: > > That's helpful thanks. Only problem is I deleted the default bucket using > the cloud console, is it possible to recreate it? (I tried and it's asking > me to verify the bucket name

[google-appengine] Re: Best solution / practice for temp files with App Engine PHP?

That's helpful thanks. Only problem is I deleted the default bucket using the cloud console, is it possible to recreate it? (I tried and it's asking me to verify the bucket name). Or do any buckets under a project count for the 5 GB free? On Thursday, June 18, 2015 at 10:27:43 PM UTC+1, Stuart

[google-appengine] Re: Best solution / practice for temp files with App Engine PHP?

Cloud storage read-after-write is strongly consistent so the file would be available immediately after it is written: https://cloud.google.com/storage/docs/concepts-techniques#consistency I'm not certain about the costs for "temporary" files - If the files are 100kb and the cost per GB per mont

[google-appengine] Re: Best solution / practice for temp files with App Engine PHP?

Thanks Stuart, good to have that reassurance. My code does do that, but in the event a file can't be created in vfs:// it saves it out to Cloud Storage. I can't find details anywhere on how soon after a file is written to Cloud Storage it becomes available for reading again, and also what costs

[google-appengine] Re: Best solution / practice for temp files with App Engine PHP?

Yes, the pricing details were my first port of call :) But they say nothing about costs accrued for data stored for very short periods of time... On Wednesday, June 17, 2015 at 9:13:31 PM UTC+1, Mars Lan wrote: > > You can find the pricing details for GCS at > https://cloud.google.com/storage/pr

[google-appengine] Re: Best solution / practice for temp files with App Engine PHP?

If you're doing images a few hundred K in size I seriously doubt you'll hit memory limits using vfs:// - I'd start there. On Thursday, 18 June 2015 03:17:58 UTC+10, Alex Kerr wrote: > > Thanks. No problems with tempnam, but I'm capacity planning for what is > likely to be a heavily loaded site w

[google-appengine] Re: Best solution / practice for temp files with App Engine PHP?

You can find the pricing details for GCS at https://cloud.google.com/storage/pricing On Wednesday, June 17, 2015 at 10:17:58 AM UTC-7, Alex Kerr wrote: > > Thanks. No problems with tempnam, but I'm capacity planning for what is > likely to be a heavily loaded site with many users hitting simulta

[google-appengine] Re: Best solution / practice for temp files with App Engine PHP?

Thanks. No problems with tempnam, but I'm capacity planning for what is likely to be a heavily loaded site with many users hitting simultaneously. I want to avoid (or plan for) a situation where there is no spare memory in a particular instance for another temp file to be created because it's s

[google-appengine] Re: Best solution / practice for temp files with App Engine PHP?

Have you tried using tempnam ? If so, what problems did you see? That seems to be the obvious solution. On Sunday, 14 June 2015 05:11:03 UTC+10, Alex Kerr wrote: > > Hi, > > What's generally accepted wisdom/tech solution for temp files on GAE using