[google-appengine] Re: did App Engine change instance scheduler algorithm in the past month?

2018-05-01 Thread Kyle Finley
Tapir & Jordan,

For what it's worth, I've notice the same issue. I spoke with billing in 
the beginning of April, but at the time they weren't aware of the issue, 
and since it was only a few dollars I didn't pursue it further. If your 
interesting in investigating, here is some information that may be useful.

- The issue seems to have started on March 6th
- For me, it affected 3 low traffic apps (services).
- The apps had previously managed with one instance, and had never or very 
rarely gone over the 28hrs free quota
- No recent setting or code changes. Months or years since last updated
- All apps where using the Go runtime

May be related:
- There was another billing issue that affect 2 of the 3 around the same 
time. The issue involved instance hours being tracked incorrectly 
(attributed to the wrong day). Billing proactively notified me, via email, 
and issued a refund for *that* issue. According to billing *that* issue was 
isolated to one day, but I saw uncharacteristically high quota usage for 
multiple days that month.
- There is a UI bug in the quota table view where quota is reported as $0 
daily while still incurring charges for the day (report to billing).

I suspect the issue is still ongoing. I made changes to 2 of the 3 to 
eliminate instance usage, but the third still seems to be requiring 
increased instance. Since the scheduler behavior is somewhat opaque it's 
difficult to determine if this is a scheduler issue or caused by increased 
traffic, however.

Sorry if this isn't the correct place to post this, I just wanted to give 
you an additional datapoint in case it's helpful. 



On Tuesday, May 1, 2018 at 11:04:04 AM UTC-5, Jordan (Cloud Platform 
Support) wrote:
>
> You should investigate how many instances each of your applications used 
> in March and compare that with the amount in April. If you changed your 
> applications' scaling settings it would have directly affected instance 
> count, and in turn the amount of instance hours you use. 
>
> It is also recommended to make sure you are stopping previous versions of 
> your applications in the Cloud Console 
> , as older versions 
> can still be serving with instances.
>
> - Note that Google Groups is reserved for general product discussions and 
> not for technical support. It is recommended to open a free Billing 
> Support case 
>  for any 
> billing related inquiries. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f6a213cd-52d2-4af8-bd0c-3488405fca26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[google-appengine] Re: !!!URGENT!!! Billing Error in App Engine Instance Hours, charges skyrocketing

2017-03-15 Thread Kyle Finley
Lawrence & Marco,

For what's it's worth I'm seeing the same issue. 

Marco, If you would like billing account number, please feel free to 
contact me.

Lawrence, thank you for posting this. Would you mind updating this thread 
once the issue has been resolved? I'll need to follow the same procedure.

Thanks,
Kyle

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/dd1ed5e3-8d6b-4372-a33b-c9d1afdefd35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[google-appengine] Re: Managed VMs logs, load-balancing & context

2015-12-22 Thread Kyle Finley
John,

I just tested accessing my VM by IP. Unfortunately the request timed out:

curl: (7) Failed to connect to 23.XX.XX.XX port 80: Operation timed out


Incase you haven't seen it yet. There's a thread in the App Engine Go group 
where the issue with background context logging is discussed. There's a few 
alternatives suggested.

https://groups.google.com/forum/#!searchin/google-appengine-go/background/google-appengine-go/V90qiZKJ5Tk/CWiXsxkNDgAJ

I hope you find a solution I'll be looking into websockets in the near 
future.

Kyle

On Tuesday, December 22, 2015 at 9:15:28 AM UTC-6, John Smith wrote:
>
> Hey Kyle,
>
> yes I am using appengine.Main() to start serving requests.
> did you try to access your VMs directly? (by IP, or by 
> network-load-balancer)
>
> (note: when using google's default my-game.appspot.com 
> appengine.NewContext works but WebSockets dont)
>
> Thanks
>
>
> On Tuesday, December 22, 2015 at 4:16:56 PM UTC+2, Kyle Finley wrote:
>>
>> John,
>>
>> Are you calling appengine.Main() in your main() function?
>>
>> I'm not sure if it works with the network-load-balancer, but when I 
>> switched from classic to MVM I was receiving the same error. Adding the 
>> appengine.Main() call fixed the unknown http.Request error.
>>
>> Kyle
>>
>> e.g.
>>
>> package main
>>
>> import (
>> "google.golang.org/appengine"
>> )
>>
>> func main() {
>> appengine.Main()
>> }
>>
>> On Tuesday, December 22, 2015 at 7:42:16 AM UTC-6, John Smith wrote:
>>>
>>> Hey Nick,
>>>
>>> Thank you for your response, I would like to further clarify the flow of 
>>> things:
>>>
>>>- I have to use WebSockets
>>>- WebSockets are not supported on the Classic App Engine (when I 
>>>attempt to open a websocket connection to my-game.appspot.com it is 
>>>being filtered out and not even making it to my app code)
>>>- WebSockets seem to work on MVM via a network-load-balancer 
>>><https://cloud.google.com/compute/docs/load-balancing/network/> (and 
>>>not via the default my-game.appspot.com domain)
>>>- using MVM and a network-load-balancer I cannot create a request 
>>>context [to create a new context I use the supplied 
>>> appengine.NewContext(r) 
>>>function and get the mentioned error]
>>>- I need a context to use the datastore.GetMulti() or log.Debugf() 
>>>APIs
>>>- I am able to create a background context (supported by MVM) and 
>>>use these APIs but when I use this context (with the 
>>> appengine/log.Debugf() 
>>>API) the logs get cluttered (aggregated under /_ah/background)
>>>
>>>
>>>1. are the above points clarify how my app receives requests?
>>>2. no, when a request is dispatched via network-load-balancer (and 
>>>not my-game.appspot.com) my application gets no X-Appengine-* 
>>>headers at all
>>>3. yes all of my logs are piling up under one /_ah/background entry. 
>>>as mentioned above I am using the golang standard appengine/log library 
>>> as 
>>>I did with my previous Classic App engine.
>>>
>>>
>>> ideally the appengine.NewContext(r) function would work and logging via 
>>> the appengine/log.Debugf() would split the lines per request.
>>> do you find this explanation sufficient?
>>>
>>> Thanks.
>>>
>>>
>>>
>>> On Tuesday, December 22, 2015 at 12:21:02 AM UTC+2, Nick (Cloud Platform 
>>> Support) wrote:
>>>>
>>>> As someone somewhat familiar with the Go runtime but not with your 
>>>> exact use case, I'd like to help, but I'm wondering if you could provide 
>>>> some more concrete specification of the following from your post, in terms 
>>>> of code or logs: 
>>>>
>>>> While porting my app from the Classic App Engine I was facing an issue 
>>>>> with the request context (which now "skips" the default HTTP load 
>>>>> balancer 
>>>>> and goes straight to my MVM(gce) node).
>>>>>
>>>>  
>>>>
>>>>> I was getting an error ("appengine: NewContext passed an unknown 
>>>>> http.Request").
>>>>>
>>>>  
>>>>
>>>>> To overcome my need for datastore/logging/other App Engine facilities 
>>>>> I used context.Backgroun

[google-appengine] Re: Managed VMs logs, load-balancing & context

2015-12-22 Thread Kyle Finley
John,

Are you calling appengine.Main() in your main() function?

I'm not sure if it works with the network-load-balancer, but when I 
switched from classic to MVM I was receiving the same error. Adding the 
appengine.Main() call fixed the unknown http.Request error.

Kyle

e.g.

package main

import (
"google.golang.org/appengine"
)

func main() {
appengine.Main()
}

On Tuesday, December 22, 2015 at 7:42:16 AM UTC-6, John Smith wrote:
>
> Hey Nick,
>
> Thank you for your response, I would like to further clarify the flow of 
> things:
>
>- I have to use WebSockets
>- WebSockets are not supported on the Classic App Engine (when I 
>attempt to open a websocket connection to my-game.appspot.com it is 
>being filtered out and not even making it to my app code)
>- WebSockets seem to work on MVM via a network-load-balancer 
> (and 
>not via the default my-game.appspot.com domain)
>- using MVM and a network-load-balancer I cannot create a request 
>context [to create a new context I use the supplied 
> appengine.NewContext(r) 
>function and get the mentioned error]
>- I need a context to use the datastore.GetMulti() or log.Debugf() APIs
>- I am able to create a background context (supported by MVM) and use 
>these APIs but when I use this context (with the appengine/log.Debugf() 
>API) the logs get cluttered (aggregated under /_ah/background)
>
>
>1. are the above points clarify how my app receives requests?
>2. no, when a request is dispatched via network-load-balancer (and not 
>my-game.appspot.com) my application gets no X-Appengine-* headers at 
>all
>3. yes all of my logs are piling up under one /_ah/background entry. 
>as mentioned above I am using the golang standard appengine/log library as 
>I did with my previous Classic App engine.
>
>
> ideally the appengine.NewContext(r) function would work and logging via 
> the appengine/log.Debugf() would split the lines per request.
> do you find this explanation sufficient?
>
> Thanks.
>
>
>
> On Tuesday, December 22, 2015 at 12:21:02 AM UTC+2, Nick (Cloud Platform 
> Support) wrote:
>>
>> As someone somewhat familiar with the Go runtime but not with your exact 
>> use case, I'd like to help, but I'm wondering if you could provide some 
>> more concrete specification of the following from your post, in terms of 
>> code or logs: 
>>
>> While porting my app from the Classic App Engine I was facing an issue 
>>> with the request context (which now "skips" the default HTTP load balancer 
>>> and goes straight to my MVM(gce) node).
>>>
>>  
>>
>>> I was getting an error ("appengine: NewContext passed an unknown 
>>> http.Request").
>>>
>>  
>>
>>> To overcome my need for datastore/logging/other App Engine facilities I 
>>> used context.BackgroundContext() everywhere and it seemed to work well for 
>>> the datastore/urlfetch/etc..
>>
>>
>> This might help me to reproduce your situation and attempt different 
>> solutions. 
>>
>> As to your numbered questions, here are my first responses:
>>
>> 1. Are you talking about "Network Loadbalancing 
>> " or the 
>> GCE "Http Load balancer 
>> ", 
>> and could you clarify again what kind of errors you observed when 
>> attempting this? What is meant by context "skipping"?
>>
>> 2. Do you notice that you're receiving X-Appengine-* headers? If so, you 
>> can certainly use them. If you attempt to add them to requests, do you 
>> notice if they're stripped? If they are, it won't work, if they aren't, it 
>> will. Although this is a quite empirical way to proceed, and if something 
>> isn't explicitly documented, you should file a Public Issue Tracker 
>> feature request  
>> to have the behaviour defined. 
>>
>> 3. Your log lines are all piling up under one /_ah/background entry, as 
>> far as I can tell. You could use the Logging API 
>>  to write 
>> logs, and see if that shows up properly. Another option is logging to a 
>> BigQuery or SQL table. The final, most trivial answer, is to figure out how 
>> to get request logging to work without this BackgroundContext which seems 
>> to flatten all its logs into one expando in the Developers Console UI (if 
>> I'm understanding you correctly, again, it seems like this is what you're 
>> reporting).
>>
>> 4.  A better approach could only be found through further investigation, 
>> if it exists. I'm optimistic that a better approach is out there, it would 
>> just take more thought.
>>
>> On Sunday, December 20, 2015 at 11:17:12 AM UTC-5, John Smith wrote:
>>>
>>> *TL;DR: *Need to use WebSockets on AE. Only works on MVM. NewContext 
>>> fails, BackgroundContext works. Logs are polluted & d

[google-appengine] Re: Do App Engine Managed VMs Support the AppEngine Cron System?

2015-12-16 Thread Kyle Finley
Christopher,

I'm glad you found a solutions. I believe that you can also specify your 
cron.yaml when deploying. At least it works with Go. E.g.

gcloud preview app deploy app.yaml cron.yaml

And I haven't tested it, but I suspect you can add the cron directive to 
your app.yaml file directly, without the need for a separate file:

// app.yaml
runtime: node
// ...
cron:
- description: task one
  url: /task/one
  schedule: every 1 minutes




On Wednesday, December 16, 2015 at 7:02:28 PM UTC-6, Christopher Eaton 
wrote:
>
> Answered- Thanks folks - I want to leave this here in case someone else 
> goes digging for an answer:
>
> Deploying is not enough to get the cron jobs going, you have to use the 
> appcfg.py (found in the google_appengine directory after installing the 
> SDK) to update the cron.
>
> Here's the exact command that pushed my cron.yaml to AppEngine:
> ./appcfg.py update_cron /path/to/app-root/ --no_cookies 
> --noauth_local_webserver -A 
>
> *Where "xxx" is my cloud project id
>
> Hope that helps anyone in the future!
>
>
> On Wednesday, December 16, 2015 at 4:44:40 PM UTC-8, Christopher Eaton 
> wrote:
>>
>> I have a nodejs based Managed VM. It works great, deploys fine, etc. 
>> However, I can find basically zero documentation about getting AppEngine's 
>> cron to work with it. Many forum/stack overflow posts allude to it being 
>> supported, but no one knows how. 
>>
>> I tried dropping a cron.yaml file into my app's directory (same location 
>> as the app.yaml file) but it doesn't seem to register when deployed.
>>
>> Anyone know anything about this, is it supported or not?
>>
>> *Note I'm not talking about cron within the docker image, I'm 
>> specifically asking about the AppEngine cron functionality that is grouped 
>> with Task Queues in the console.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f65dc889-ce70-4dda-b3d6-403cf1c42154%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[google-appengine] Re: Qualys SSL Test keeps rating Google App Engine sites with B

2015-09-19 Thread Kyle Finley
PK,

It looks like this issue will be resolved soon.

Disabling SSLv3 and RC4 

  http://googleonlinesecurity.blogspot.com/2015/09/disabling-sslv3-and-rc4.html

> [..] Because of these issues we expect to disable both SSLv3 and RC4 
support at Google’s frontend servers and, over time, across our products in 
general, including Chrome, Android, our webcrawlers and our SMTP servers.

Kyle

On Friday, September 18, 2015 at 10:49:33 PM UTC-5, PK wrote:
>
> This has been reported in this public tracker about a year and a half ago 
> (see issue 10783 
> ). 
> Google has acknowledged the issue there but has never offered an official 
> response. It makes conversations with customers about security difficult. 
> Can somebody respond here and/or the bug tracker what the plans are to make 
> us look good in this test and hopefully more secure?
>
> (Before somebody jumps to offer Cloudflare, I know that Cloudflare or some 
> other front end might be an option but I do not want to have traffic in the 
> clear between that front end and Google, so I want a fix from Google.)
>
> Thanks
>
>
>
>
> PK
> p...@gae123.com 
>
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/10b1a641-4fc7-4765-9617-bee715218e4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[google-appengine] Re: Email not working after migrating from master/slave to high replication

2015-05-20 Thread Kyle Finley
I believe the limit is reset when you migrate. If you are sending more then 
100 email daily you may need to request a quota increase:
https://docs.google.com/forms/d/1OpXTrBHpnTZfv53bzr55Ra1NK_eTBzWQ-yO6ydIHC48/viewform?formkey=dENESzEwNzJiZEdpQkRzTl9RNElVWUE6MQ#gid=0

There's' a check box for those that have migrate from master/slave to HDR

On Tuesday, May 19, 2015 at 12:09:57 AM UTC-5, openentry wrote:
>
> Even after successfully migrating the AppEngine from master/slave to high 
> replication, the email function does not work which is working before 
> migrating.
> Anyone has any idea how to fix this problem.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0d283f6b-d638-456f-a687-eb6a9c49cb60%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[google-appengine] Re: How to sell and support a web app on GAE

2015-02-23 Thread Kyle Finley
I've been thinking about this also.

For option (1) maybe upgrades could be automated. I wonder if the Google 
Cloud Deployment Manager 
 could be 
useful here. At the very least, it seems like it should be possible to have 
user authenticate via oAuth and upload utilizing the deploy command from a 
VM.

Out of curiosity how are you planning on licensing your app? I was 
considering something like this:

CostBusiness TypeRevenueHosting TypeSupportFreeNon-commercial0-XXXSelf - 
Your Option (1)NoneXXXCommercialXXX - XManage - Your Option (2)PaidXXX
CommercialXXX - XSelf - Your Option (1)Paid

I think AppEngine is an interesting platform for this type of 
setup/licensing. It essentially allows the customer to get high quality 
software and hosting at zero initial cost to them and the developer. I 
believe this to be ideal for small-medium businesses who don't want to pay 
a system admin.

I'm also interested in hear others ideas and thoughts on this. 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/844d6530-5a81-459d-b3a3-93441cc57d48%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[google-appengine] Re: Push to deploy discontinued?

2014-12-22 Thread Kyle Finley
I believe they sent emails to those that have used the service. Here's the 
contents:

Hello,

The ability to quickly, easily and safely deploy your code is an important 
part of a great cloud developer experience. You have used the Release 
Pipelines feature on GCP to push-to-deploy and have given us very 
insightful feedback. We heard clearly that you want more flexibility and 
control. So we have decided to move the product in this direction.

Instead of a pipeline with a small number of options, we want to offer you 
the full flexibility of Jenkins. We heard that setting up Jenkins is hard, 
so we are giving you tools to make that simpler. There are instructions 
 explaining how to set 
up Jenkins and configure continuous deployment for your GCP apps, using 
provided plugins 
.

With the availability of this solution, we are going to remove the Release 
Pipelines UI in the Developer Console by January 22. If you are currently 
using the build/test options, please remember to disable your pipeline so 
you are no longer charged for it.

Note that repo sync with GitHub and Bitbucket is still supported and the 
Jenkins plugin to trigger a deployment from the push event is included 
above.

If you used the 'source only' option in Release Pipelines, going forward 
you can use gcloud app update  to 
deploy source to App Engine.

If you have any questions, please email [removed]*.

Google Cloud Release Pipelines team

*I removed the email address in the event that it was reserved for current 
users.

On Monday, December 22, 2014 2:57:20 PM UTC-6, Kristopher Giesing wrote:
>
> I'm confused as well, was there an official announcement that I missed?
>
> - Kris
>
> On Saturday, December 20, 2014 11:14:29 AM UTC-8, Chad Vincent wrote:
>>
>> Wait, what is this?
>>
>> I just spent 3 of the last 5 weeks trying to convert our Eclipse build to 
>> Maven so we could use push-to-deploy (and dependency management)...
>>
>> On Friday, December 19, 2014 9:22:57 PM UTC-6, Rae Wang wrote:
>>>
>>> Hi Lucas,
>>>
>>> I'm sorry this upsets you. I hear your need to have an easier source 
>>> deploy experience and will connect you offline with the eng team working on 
>>> the deployment. 
>>>
>>> Thanks,
>>> Rae
>>>
>>> On Friday, December 19, 2014 3:44:30 PM UTC-8, Lucas Geiger wrote:

 Guys, this is absurd. You finally got the push-to-deploy product right 
 , and now you are discontinuing it. At least pushing source should remain 
 as a feature. 
 The whole appeal of push to deploy was NOT setting up Jenkins. I think 
 you are misjudging the number of people who object to using Jenkins. 
  (By the way it was very disrespectful of you to cloak this 
 discontinuation as a feature upgrade. A tasteless and disingenuous tactic, 
 to be precise.)
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.


[google-appengine] Re: git repo with PhoneGap

2014-04-18 Thread Kyle Finley
Does passing in your username and password work? Something like:[0]

https://username:passw...@source.developers.google.com/p/my-repo/

Note: It's not very secure.

Another option is using a .netrc file [1], but that may not work with 
PhoneGap, if it's an external service.


[0]: 
https://stackoverflow.com/questions/10054318/how-to-give-username-and-password-when-do-git-clone-gitremote-git
 
[1]: 
https://confluence.atlassian.com/display/STASH/Permanently+authenticating+with+Git+repositories


On Friday, April 18, 2014 5:05:07 PM UTC-5, GAEfan wrote:
>
> Would be nice to be able to have a url to the GCS git repo that bypasses 
> authentication.
>
> Or, coordination between PhoneGap and the GCS repo.  PhoneGap coordinates 
> now with GitHub, where you can enter your credentials once, and link the 
> two accounts.
>
> Thanks.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.


Re: [google-appengine] Cloud Datastore Dashboard not working

2014-04-04 Thread Kyle Finley
Are you using Chrome? I've had issues with Chrome, but the admin displayed 
correctly with Firefox 28. Also, I've found that some browser extensions 
(Ad block, Disconnect, etc.) may interfere with the loading of some assets.


On Friday, April 4, 2014 2:02:19 PM UTC-5, husayt wrote:
>
> Hi Vinny,
>
> here is the screenshot:
>
>
> https://www.dropbox.com/s/rw7c7pkc32hrhq4/Screenshot%202014-04-04%2019.52.23.png
>
> Noting special. something to do with the error in obtainning 
> metadata
>  mentioned above.
>
> On Wednesday, 2 April 2014 00:53:57 UTC+1, Vinny P wrote:
>>
>> Can you screenshot the error page and post an image here?
>>  
>>  
>> -
>> -Vinny P
>> Technology & Media Advisor
>> Chicago, IL
>>
>> App Engine Code Samples: http://www.learntogoogleit.com
>>   
>>  
>>
>>
>> On Mon, Mar 31, 2014 at 3:50 AM, husayt  wrote:
>>
>>>
>>> Hi, 
>>> Cloud Datastore Dashboard in Developers Console is not working for us in 
>>> one of projects:
>>>
>>> https://console.developers.google.com/project//datastore/stats
>>>
>>> it says "Failed to load".
>>>
>>> Probably fails because of the error in this quesry:
>>> Request URL:
>>> https://console.developers.google.com/m/datastore/metadata?pid=...
>>>
>>> Is this known issue, and where is the best to report it?
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Google App Engine" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to google-appengi...@googlegroups.com.
>>> To post to this group, send email to google-a...@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/google-appengine.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.


Re: [google-appengine] Cacheing (mostly) static data in Cloud Storage

2014-03-20 Thread Kyle Finley
Pertti,

Cloudflare  offers a free caching service that 
should fit your needs. App Engine also offers edge 
caching, 
but I believe you must have billing enabled to utilize it. Either solution 
would save you from incurring datastore lookups. Cloudflare has the added 
benefit of saving you on bandwidth as well.

As for billing, you can set the maximum spend to as low as $0.01 / day, 
this would give you the benefits of having billing enabled without the risk 
of encoring a large bill.

Kyle

>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.


[google-appengine] Re: Announcing a credit for App Engine applications with new custom domains

2013-06-17 Thread Kyle Finley
Andrew,

Is this in addition to the 1 free Google Apps user?

https://groups.google.com/d/msg/google-appengine/pVZfdeky-ow/TO1SmipM2Y0J

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.




[google-appengine] Re: Deploy current HTML site to Google Apps

2013-01-07 Thread Kyle Finley
To add to Blaine's comment -- you *can* map the root url i.e. '/' to an 
index.html file by add something like:

# app.yaml
# ...
handlers:
- url: /
  static_dir: dreamweaver_dir

- url: /
  static_files: dreamweaver_dir/index.html
  upload: dreamweaver_dir/index.html

Kyle

On Monday, January 7, 2013 2:35:38 PM UTC-6, Blaine Garrett wrote:
>
> See 
> https://developers.google.com/appengine/docs/python/gettingstarted/staticfiles
>
> You *might* be able to set the static directive for your root URL or 
> catchall, although I have not tried this and would anticipate some issues. 
> If that works, then you should be able to just have Dreamweaver publish to 
> a folder in your app, set the directive to point the root url to that 
> folder, and then deploy the app as normal.
>
>
>
>
>
>
> On Sunday, January 6, 2013 4:58:43 PM UTC-6, rod.doo...@trucker-ware.comwrote:
>>
>> Have been working with the cloud sherpa’s for a while now but can’t seem 
>> to get a straight answer from anyone. We are trying to do a Proof of 
>> concept on the App Engine but before we get to deep we just want to deploy 
>> a very basic HTML site that was developed with Dream Weaver. Is this 
>> possible? If so does anyone have a link or instruction for a Windows user.
>>
>>  I am so frustrated with this that we are considering cancelling the POC 
>> and just doing traditional development and hosting.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/8rMncCq1TjIJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



[google-appengine] Re: Google Apps No Longer Free

2012-12-07 Thread Kyle Finley
techamerica,

Have you looked into Windows Live Custom Domains https://domains.live.com/ 
? I think what you could do is:

1. Add your clients domain as Greg described.
2. Setup your clients email using Windows Live
3. Create regular google accounts (not gmail accounts) using the Windows 
Live email addresses e.g. u...@example.com
4. Add the users as developers to the account so that you can send emails 
using their address.

I haven't tested this, but I think it should work. It adds a few more hoops 
to jump through, but I guess that's the cost of free.

Kyle

On Friday, December 7, 2012 11:31:13 AM UTC-6, techamerica wrote:
>
> Well Merry Christmas to you too Greg and Google. 
>
> Have you guys even stopped to consider the effects eliminating the small 
> standard app will have on small business?  I for one do not know if I can 
> survive. I make my living on helping very small business's get efficient on 
> the web. And part of that was introducing those small clients to Google 
> Apps Standard and Google Adwords. I was literally in the process of setting 
> up 2 brand new clients when this hit. I just cashed their checks on 
> Tuesday. Now I am going to have to give them their money back. Right before 
> Christmas. And when I say small clients I am talking about 4 or 5 people. 
>
> If you even would have given us some notice, we might have managed it. How 
> many of us small, one and two and three man shops have supported Google 
> over the years?
>
> Thanks a lot. Merry Christmas.
>
> On Thursday, December 6, 2012 6:42:42 PM UTC-8, Greg wrote:
>>
>> Just saw that Google Apps is no longer free for 
>> businesses
>> . 
>>
>> I have no problem paying for a Google Apps account where I actually use 
>> Google apps, but at the moment you have to have a Google Apps account to 
>> link a domain to an Appengine app. Some of our apps have two or three 
>> domains showing the same app, and because you need to have an account for 
>> each email address that Appengine sends email from, we have three or four 
>> accounts per domain. So this is potentially going to add $600 per year to 
>> our costs - all for virtual accounts that don't actually use Google Apps at 
>> all.
>>
>> Can someone from Google comment please? Either Google Apps accounts need 
>> to remain free if they are associated with Appengine apps, or there needs 
>> to be another way to link domains (and authorise email addresses) for 
>> Appengine.
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/ydAKJwWqR_gJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



[google-appengine] Re: Question on how to modularize handlers

2012-11-09 Thread Kyle Finley
Shan, if you are using the python27 runtime it should be:

# app.yaml

runtime: python27

- url: /test
  script: handlers/test.application

https://developers.google.com/appengine/docs/python/config/appconfig#Script_Handlers

-- Kyle

On Friday, November 9, 2012 9:18:35 AM UTC-6, Shan Sikdar wrote:
>
> Hi basic question,
>
> Basically I'm having trouble modularizing handlers in GAE.
>
> Specifically in my application I have a download button that calls a Test 
> handler so far I have:
>   
>  $('#download').button().click(function(){
> $('