[google-appengine] Re: 503 Errors uploading multipart/form-data to blobstore handlers on afternoon of 8/29
http://code.google.com/p/googleappengine/issues/detail?id=8042 On Friday, 31 August 2012 03:06:02 UTC+10, Jeff Carollo wrote: Did anyone else see unexpected 503s for their application yesterday? Only 1/2 of my applications were affected. I made no code changes to my site in the last two weeks, saw a 1-3 hour outage yesterday only in multipart/form-data POSTs to one of my blobstore upload handlers. Quota was not an issue and my dashboard shows no quota denials. I also didn't see the 503s in my logs, but did see other traffic from the same hosts. Changing nothing in my application, the 503s went away on their own after some time. Was there a Blobstore outage yesterday? Is there a page which lists know outages with start/end times? The service status page shows 100% uptime over the last 7 days, which seems to indicate that no one noticed. Is anyone from GAE SRE willing to investigate? Thanks! Jeff -- 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/-/NgqV0RUR3BQJ. 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.
Re: [google-appengine] Channel API not working in production
Hi, I have to agree with Pascal. Channel API has too many issues and though I have worked around most of them to a certain degree when it started to be good enough, I would not repeat this if I would be still planning my application. Some more issues that I can easily add to the list above: - doesn't support batch sending (if you want to broadcast same message) Note that the cost you see in the dashboard for Channel API is not the full cost. You also have to consider that your instances will spend some time sending the messages. Usually the API call to send a message takes 20-40 millis, but on occasions it can take a couple of seconds. And if you are broadcasting your instances may end up spending most of the time doing sendMessage calls.. There is an issue for that, please star it: http://code.google.com/p/googleappengine/issues/detail?id=4506 - 400 SID errors Usually it doesn't happen too often, but sometimes you will get them right after your client connected and then again... There is an issue for that, feel free to star it: http://code.google.com/p/googleappengine/issues/detail?id=4940 - Sometimes channels are just dead You create a channel, there are no errors or anything, but no matter how many messages you send, it just won't receive any. The token is still valid, so your client can try to reconnect, but it won't help, it has to create a new channel with a new token. But how to detect this kind of issue until it is too late and user has left your app for good? The problem is sometimes channel takes 20+ seconds before it receives messages.. - Quota of 60 connects per minute (1 per sec) If I succeed, it won't be enough for my app. I have no idea how responsive is google in increasing the quota.. +1 for presence notifications are extremely unreliable To a degree that I had to duplicate them, my app sends its own callbacks. What is unreliable you may ask? Disconnect notification for example may come *minutes* after. So my client already handled the situation and connected to another channel long ago. If I would have waited for presence notification, I would have lost the user. Or even worse on some days the notification may not come at all. And because you can never be totally sure that you have not missed something or channel doesn't give you a new trick, I had to add shamefull lazy polling to make sure my users are still connected :( PS. I'm trying out Pusher and it looks good. PSS. I still like Appengine, but Channel API is really not ready for production apps. суббота, 1 сентября 2012 г., 7:32:56 UTC+3 пользователь Kristopher Giesing написал: On Friday, August 31, 2012 12:29:20 PM UTC-7, Pascal Patry wrote: Hi, Channels on AppEngine are picky. There are multiple issues that I had to work around for an application that is currently in production: 1. Channels aren't working on backends Argh, seriously? That is a huge problem for me :( 2. No API is available to mobile I worked around this by embedding the jsapi code in my application. It seems to work fine... so far. 3. The implementation is different from the test and production server Yes, that is a pain. I had to add a wrapper class to my application to choose between embedded test and prod implementations dynamically. 4. Connection/Disconnection handlers aren't reliably called Are you talking about this? If so it was fixed: http://code.google.com/p/googleappengine/issues/detail?id=7098 The fix isn't public yet but there's a patch in the thread. - Kris -- 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/-/YPNuW4F8A0kJ. 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] prospective_search broke since yesterday
Dear All, Since 9/1, all my prospective_search related python code is broken. I don't know why. Is there a API change? Anyone has the same experience? Thanks a lot! coronin -- 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/-/8EuwSbVDDJYJ. 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.
Re: [google-appengine] will GAE support private cloud?
see also appscale Dne úterý, 20. dubna 2010 17:37:16 UTC+2 disorderdev napsal(a): just like Amazon, custom can control his own resource, especially database. in fact the most important thing is database in GAE, say I have an app deployed on GAE, then all customers' information will be saved in 'my' database, and I have full control on customers data, a lot of customers will complain that, so I'm wondering wether GAE will support private cloud, for example, for each customer domain, my app will save data to a database that customer has full control, but I have no control, is it possible? -- You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-a...@googlegroups.comjavascript:. To unsubscribe from this group, send email to google-appengi...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- 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/-/p6KP8aHswmMJ. 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: ETags on static files :(
Anybody found a way around this? I noticed you can overwrite the ETag by setting a value for http_headers on app.yaml, but not clear it. On Wednesday, October 27, 2010 7:07:33 PM UTC-4, Waldemar Kornewald wrote: Hi, I noticed that App Engine is setting ETags on static files. Is there a way to turn them off? ETags override the cache-control header and cause the browser to issue additional HTTP requests to check for modified files. This is bad for performance and completely unnecessary if you use an asset manager that adds a version hash to the generated file names. How can I get rid of those ETags and only have a cache-control header? Thanks! Bye, Waldemar Kornewald -- Django on App Engine, MongoDB, ...? Browser-side Python? It's open-source: http://www.allbuttonspressed.com/blog/django -- 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/-/-n6rH1ZoNlkJ. 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] Why is Google so eager to send SMS messages?
I wanted to make another app. The account has billing-enabled apps. Suddenly Google keeps prompting me for SMS verification again. Why? This hasn't happened before when I made new apps, on the very same account. -- You received this message because you are subscribed to the Google Groups Google App Engine group. 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] App Engine G+ hangout: Appstats - Wed. 5th Sept. 4pm PDT
There will be an App Engine G+ hangout on Wed., 5th Sept., at 4pm Pacific time (23:00 UTC). We'll talk about optimizing using Appstats to optimise your App Engine app, and highlight some new Appstats features. Visit this Google Developers live event page to find the hangout when it starts up: https://developers.google.com/live/shows/ahNzfmdvb2dsZS1kZXZlbG9wZXJzcg4LEgVFdmVudBjj58cDDA/ Submit questions via Google Moderator: https://www.google.com/moderator/#15/e=1faeact=1faeac.4c Find out when the hangout starts in your time zone: http://goo.gl/x6gxZ You can find the Cloud Platform Developers live events here: https://developers.google.com/live/cloud and subscribe to calendar events for these hangouts here: http://goo.gl/GGkgx , http://goo.gl/PILq0 . We hope you can join us! -- You received this message because you are subscribed to the Google Groups Google App Engine group. 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] new Google Cloud Platform Developers Google+ page
The Cloud Platform Developer Relations team, which includes App Engine, now has a Google Cloud Platform Developers Google+ page! https://plus.google.com/117105793163182226623/posts https://plus.google.com/117105793163182226623/posts/XzMhE7wxeh1 This is a good way to track news and events, including our Hangout/office hours times, interesting articles and codelabs, etc. It's also a good way to see what's going on with related Google technologies, such as BigQuery and Google Cloud Storage. -Amy -- You received this message because you are subscribed to the Google Groups Google App Engine group. 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.
Re: [google-appengine] Re: Weird Instance Scheduler
The 400ms was measured from the time that the code entered my servlet's get method. I can't be sure anymore since I've rewritten the code since then to use Objectify, but I'm guessing that it did not include the first PMF construction call. If constructing the PMF is what was costing a bunch of time, then I'm guessing that the warmup request was not constructing one, but that it was getting constructed at static init time relative to the actual request. I'll keep an eye on this once I'm ready to deploy again (the rewrite to Objectify came with a bunch of other changes I need to finish before I'm ready for real testing again). For the moment, though, it seems like the problems I was having were due to a misunderstanding of how GAE instance warmups happen, and not due to a problem with the instance scheduler itself. - Kris On Saturday, September 1, 2012 3:57:07 PM UTC-7, Jeff Schnitzer wrote: Yeah, baffling. JDO startup costs come with the construction of the PersistenceManagerFactory, so that should be in your code. That 400ms - is that measured from a filter at the outermost layer? An interesting thing to try is to set up a handler for the warmup request which issues an actual query to the datastore. Any query. Jeff On Fri, Aug 31, 2012 at 9:25 PM, Kristopher Giesing kris.g...@gmail.com javascript: wrote: OK. Something just became clearer to me. The requests appear to be tagged with the instance that handles the request. Based on that data, it looks like my request is in fact being handled by the resident instance, not the new dynamic instance. The puzzle then becomes why the request still takes 8s to satisfy when the instance handling it is already warmed, and the in-application logging code (which I didn't post, but trust me on this) is never higher than about 400ms. I had been assuming that the 8s cost was the cost of the new instance spinning up, but the instance tag seems to contradict that. The answer has to be some kind of static initialization cost. Although my app is not very complex, I wonder if this is due to the class path scanning that JDO does. I have since switched to Objectify, but I am actually not very clear on whether that is sufficient to prevent JDO/JPA class path scanning; it seems like I would need to evict the JDO/JPA core code from my application on deployment, but it's far from clear to me how to do that. ... But even that may not really explain this behavior because you would think static initialization costs would be born by the warmup request. So, actually, I am baffled. Any ideas, anyone? - Kris On Friday, August 31, 2012 9:16:16 PM UTC-7, Kristopher Giesing wrote: This is the request that I actually issued, being handled: 2012-07-31 23:08:28.045 /api/game/57002?pretty=true 200 7893ms 11kb Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/536.25 (KHTML, like Gecko) Version/6.0 Safari/536.25 76.102.149.245 - kris [31/Jul/2012:23:08:28 -0700] GET /api/game/57002?pretty=true HTTP/1.1 200 11652 - Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/536.25 (KHTML, like Gecko) Version/6.0 Safari/536.25 titan-game-qa.appspot.com ms=7893 cpu_ms=3520 api_cpu_ms=0 cpm_usd=0.099322 instance=00c61b117c77507e2cfe78a0806d0ca80b52720e These are the *two* preceding warmup requests: ** Dynamic instance warmup ** 2012-07-31 23:08:27.475 /_ah/warmup 200 5873ms 0kb 0.1.0.3 - - [31/Jul/2012:23:08:27 -0700] GET /_ah/warmup HTTP/1.1 200 60 - - 1.360723738856412175.titan-game-qa.appspot.com ms=5873 cpu_ms=2475 api_cpu_ms=0 cpm_usd=0.068778 loading_request=1 instance=00c61b117cdaae6145945d99c16aeee7cc0f4ad8 ** Resident/idle instance warmup ** 2012-07-31 23:07:42.842 /_ah/warmup 200 5045ms 0kb 0.1.0.3 - - [31/Jul/2012:23:07:42 -0700] GET /_ah/warmup HTTP/1.1 200 60 - - 1.360723738856412175.titan-game-qa.appspot.com ms=5046 cpu_ms=2475 api_cpu_ms=0 cpm_usd=0.068778 loading_request=1 instance=00c61b117c77507e2cfe78a0806d0ca80b52720e This is my point. The problem is not that a new instance was spawned (although I admit that I did not quite understand the desired behavior when I first posted this data). The problem is that the request I issued is not satisfied until AFTER the warmup request has been issued and handled by the new instance. The request should FIRST have been handled by the already resident instance, AND THEN the new instance should have been spawned. If I'm misunderstanding something, please clarify, because at the face of it this seems to be a smoking gun. - Kris -- 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/-/4FGx8YdHUIgJ.
Re: [google-appengine] Channel API not working in production
+1 Channels is probably the most overhyped but underwhelming feature on GAE. It was launched with lots of hype and high expectations. Still after 2 years to is mostly unusable. GAE team is better off killing Channels as a feature to free up resources and focus on delivering websockets. On Sunday, September 2, 2012 1:16:42 AM UTC-7, Aleksei Rovenski wrote: Hi, I have to agree with Pascal. Channel API has too many issues and though I have worked around most of them to a certain degree when it started to be good enough, I would not repeat this if I would be still planning my application. Some more issues that I can easily add to the list above: - doesn't support batch sending (if you want to broadcast same message) Note that the cost you see in the dashboard for Channel API is not the full cost. You also have to consider that your instances will spend some time sending the messages. Usually the API call to send a message takes 20-40 millis, but on occasions it can take a couple of seconds. And if you are broadcasting your instances may end up spending most of the time doing sendMessage calls.. There is an issue for that, please star it: http://code.google.com/p/googleappengine/issues/detail?id=4506 - 400 SID errors Usually it doesn't happen too often, but sometimes you will get them right after your client connected and then again... There is an issue for that, feel free to star it: http://code.google.com/p/googleappengine/issues/detail?id=4940 - Sometimes channels are just dead You create a channel, there are no errors or anything, but no matter how many messages you send, it just won't receive any. The token is still valid, so your client can try to reconnect, but it won't help, it has to create a new channel with a new token. But how to detect this kind of issue until it is too late and user has left your app for good? The problem is sometimes channel takes 20+ seconds before it receives messages.. - Quota of 60 connects per minute (1 per sec) If I succeed, it won't be enough for my app. I have no idea how responsive is google in increasing the quota.. +1 for presence notifications are extremely unreliable To a degree that I had to duplicate them, my app sends its own callbacks. What is unreliable you may ask? Disconnect notification for example may come *minutes* after. So my client already handled the situation and connected to another channel long ago. If I would have waited for presence notification, I would have lost the user. Or even worse on some days the notification may not come at all. And because you can never be totally sure that you have not missed something or channel doesn't give you a new trick, I had to add shamefull lazy polling to make sure my users are still connected :( PS. I'm trying out Pusher and it looks good. PSS. I still like Appengine, but Channel API is really not ready for production apps. суббота, 1 сентября 2012 г., 7:32:56 UTC+3 пользователь Kristopher Giesing написал: On Friday, August 31, 2012 12:29:20 PM UTC-7, Pascal Patry wrote: Hi, Channels on AppEngine are picky. There are multiple issues that I had to work around for an application that is currently in production: 1. Channels aren't working on backends Argh, seriously? That is a huge problem for me :( 2. No API is available to mobile I worked around this by embedding the jsapi code in my application. It seems to work fine... so far. 3. The implementation is different from the test and production server Yes, that is a pain. I had to add a wrapper class to my application to choose between embedded test and prod implementations dynamically. 4. Connection/Disconnection handlers aren't reliably called Are you talking about this? If so it was fixed: http://code.google.com/p/googleappengine/issues/detail?id=7098 The fix isn't public yet but there's a patch in the thread. - Kris -- 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/-/xxXmgwM8N0gJ. 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.
RE: [google-appengine] new Google Cloud Platform Developers Google+ page
No offense I'm sure it is awesome. But don't you think y'all are a little scattered? I mean there is the discussion pages/forum, Stack Over Flow, 4 issues bug trackers, a support form, 6 blogs. That's before I point out that Google Plus rules say you have to be a person, so google is using its own products in ways that conflict with their own usage policies? I'm glad you want to be reachable. But I'd rather have one place where I know I can get an answer than 40, and some of those being pages with nonsensical URLs that are impossible to remember and don't appear in search. From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Amy Unruh Sent: Sunday, September 02, 2012 3:12 PM To: google-appengine@googlegroups.com Subject: [google-appengine] new Google Cloud Platform Developers Google+ page The Cloud Platform Developer Relations team, which includes App Engine, now has a Google Cloud Platform Developers Google+ page! https://plus.google.com/117105793163182226623/posts https://plus.google.com/117105793163182226623/posts/XzMhE7wxeh1 This is a good way to track news and events, including our Hangout/office hours times, interesting articles and codelabs, etc. It's also a good way to see what's going on with related Google technologies, such as BigQuery and Google Cloud Storage. -Amy -- You received this message because you are subscribed to the Google Groups Google App Engine group. 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. -- You received this message because you are subscribed to the Google Groups Google App Engine group. 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.
RE: [google-appengine] Channel API not working in production
I think they know this, which is why there are Endpoints which aren't the same thing but are described for the same use cases, and suck in their own special way. From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of vlad Sent: Sunday, September 02, 2012 3:32 PM To: google-appengine@googlegroups.com Subject: Re: [google-appengine] Channel API not working in production +1 Channels is probably the most overhyped but underwhelming feature on GAE. It was launched with lots of hype and high expectations. Still after 2 years to is mostly unusable. GAE team is better off killing Channels as a feature to free up resources and focus on delivering websockets. On Sunday, September 2, 2012 1:16:42 AM UTC-7, Aleksei Rovenski wrote: Hi, I have to agree with Pascal. Channel API has too many issues and though I have worked around most of them to a certain degree when it started to be good enough, I would not repeat this if I would be still planning my application. Some more issues that I can easily add to the list above: - doesn't support batch sending (if you want to broadcast same message) Note that the cost you see in the dashboard for Channel API is not the full cost. You also have to consider that your instances will spend some time sending the messages. Usually the API call to send a message takes 20-40 millis, but on occasions it can take a couple of seconds. And if you are broadcasting your instances may end up spending most of the time doing sendMessage calls.. There is an issue for that, please star it: http://code.google.com/p/googleappengine/issues/detail?id=4506 - 400 SID errors Usually it doesn't happen too often, but sometimes you will get them right after your client connected and then again... There is an issue for that, feel free to star it: http://code.google.com/p/googleappengine/issues/detail?id=4940 - Sometimes channels are just dead You create a channel, there are no errors or anything, but no matter how many messages you send, it just won't receive any. The token is still valid, so your client can try to reconnect, but it won't help, it has to create a new channel with a new token. But how to detect this kind of issue until it is too late and user has left your app for good? The problem is sometimes channel takes 20+ seconds before it receives messages.. - Quota of 60 connects per minute (1 per sec) If I succeed, it won't be enough for my app. I have no idea how responsive is google in increasing the quota.. +1 for presence notifications are extremely unreliable To a degree that I had to duplicate them, my app sends its own callbacks. What is unreliable you may ask? Disconnect notification for example may come *minutes* after. So my client already handled the situation and connected to another channel long ago. If I would have waited for presence notification, I would have lost the user. Or even worse on some days the notification may not come at all. And because you can never be totally sure that you have not missed something or channel doesn't give you a new trick, I had to add shamefull lazy polling to make sure my users are still connected :( PS. I'm trying out Pusher and it looks good. PSS. I still like Appengine, but Channel API is really not ready for production apps. суббота, 1 сентября 2012 г., 7:32:56 UTC+3 пользователь Kristopher Giesing написал: On Friday, August 31, 2012 12:29:20 PM UTC-7, Pascal Patry wrote: Hi, Channels on AppEngine are picky. There are multiple issues that I had to work around for an application that is currently in production: 1. Channels aren't working on backends Argh, seriously? That is a huge problem for me :( 2. No API is available to mobile I worked around this by embedding the jsapi code in my application. It seems to work fine... so far. 3. The implementation is different from the test and production server Yes, that is a pain. I had to add a wrapper class to my application to choose between embedded test and prod implementations dynamically. 4. Connection/Disconnection handlers aren't reliably called Are you talking about this? If so it was fixed: http://code.google.com/p/googleappengine/issues/detail?id=7098 The fix isn't public yet but there's a patch in the thread. - Kris -- 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/-/xxXmgwM8N0gJ. 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. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com.
Re: [google-appengine] new Google Cloud Platform Developers Google+ page
+1, well said Drake. Nick On 3 September 2012 10:14, Drake drak...@digerat.com wrote: No offense I’m sure it is awesome… But don’t you think y’all are a little scattered? I mean there is the discussion pages/forum, Stack Over Flow, 4 issues bug trackers, a support form, 6 blogs. ** ** That’s before I point out that Google Plus rules say you have to be a person, so google is using its own products in ways that conflict with their own usage policies? ** ** I’m glad you want to be reachable… But I’d rather have one place where I know I can get an answer than 40, and some of those being pages with nonsensical URLs that are impossible to remember and don’t appear in search. ** ** ** ** *From:* google-appengine@googlegroups.com [mailto: google-appengine@googlegroups.com] *On Behalf Of *Amy Unruh *Sent:* Sunday, September 02, 2012 3:12 PM *To:* google-appengine@googlegroups.com *Subject:* [google-appengine] new Google Cloud Platform Developers Google+ page ** ** The Cloud Platform Developer Relations team, which includes App Engine, now has a Google Cloud Platform Developers Google+ page! https://plus.google.com/117105793163182226623/posts https://plus.google.com/117105793163182226623/posts/XzMhE7wxeh1 ** ** This is a good way to track news and events, including our Hangout/office hours times, interesting articles and codelabs, etc. It's also a good way to see what's going on with related Google technologies, such as BigQuery and Google Cloud Storage. ** ** -Amy ** ** -- You received this message because you are subscribed to the Google Groups Google App Engine group. 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. -- You received this message because you are subscribed to the Google Groups Google App Engine group. 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. -- You received this message because you are subscribed to the Google Groups Google App Engine group. 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] Cloud-based Continuous Build Server for Google App Engine Projects
I've been asked to setup a continuous build server for a Google App Engine project. Has anyone already configured a build-server in the cloud that includes the Google App Engine SDK? My ideal solution would be a public Amazon EC2 AMI (or Google Compute Engine image) that I could just clone, launch and configure. Our GAE code is hosted in Github, so my goal is to setup Github to ping the build server every time there is a new commit to the Github repo and have the build server rebuild and test the GAE project. Anyone know of an existing solution? Thanks, Chris -- 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/-/AY0HQ_J8A-UJ. 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.
Re: [google-appengine] Cloud-based Continuous Build Server for Google App Engine Projects
Sure, we have done this with Atlassian Bamboo and GAE/J. We run tests suites over localhost and also a GAE deployed staging environment - it's pretty straight forward. On 3 September 2012 12:46, Chris scboe...@gmail.com wrote: I've been asked to setup a continuous build server for a Google App Engine project. Has anyone already configured a build-server in the cloud that includes the Google App Engine SDK? My ideal solution would be a public Amazon EC2 AMI (or Google Compute Engine image) that I could just clone, launch and configure. Our GAE code is hosted in Github, so my goal is to setup Github to ping the build server every time there is a new commit to the Github repo and have the build server rebuild and test the GAE project. Anyone know of an existing solution? Thanks, Chris -- 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/-/AY0HQ_J8A-UJ. 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. -- You received this message because you are subscribed to the Google Groups Google App Engine group. 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.
Re: [google-appengine] new Google Cloud Platform Developers Google+ page
+1 for Drake. -Aswath On Mon, Sep 3, 2012 at 7:55 AM, Nickolas Daskalou n...@daskalou.com wrote: +1, well said Drake. Nick On 3 September 2012 10:14, Drake drak...@digerat.com wrote: No offense I’m sure it is awesome… But don’t you think y’all are a little scattered? I mean there is the discussion pages/forum, Stack Over Flow, 4 issues bug trackers, a support form, 6 blogs. ** ** That’s before I point out that Google Plus rules say you have to be a person, so google is using its own products in ways that conflict with their own usage policies? ** ** I’m glad you want to be reachable… But I’d rather have one place where I know I can get an answer than 40, and some of those being pages with nonsensical URLs that are impossible to remember and don’t appear in search. ** ** ** ** *From:* google-appengine@googlegroups.com [mailto: google-appengine@googlegroups.com] *On Behalf Of *Amy Unruh *Sent:* Sunday, September 02, 2012 3:12 PM *To:* google-appengine@googlegroups.com *Subject:* [google-appengine] new Google Cloud Platform Developers Google+ page ** ** The Cloud Platform Developer Relations team, which includes App Engine, now has a Google Cloud Platform Developers Google+ page! https://plus.google.com/117105793163182226623/posts https://plus.google.com/117105793163182226623/posts/XzMhE7wxeh1 ** ** This is a good way to track news and events, including our Hangout/office hours times, interesting articles and codelabs, etc. It's also a good way to see what's going on with related Google technologies, such as BigQuery and Google Cloud Storage. ** ** -Amy ** ** -- You received this message because you are subscribed to the Google Groups Google App Engine group. 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. -- You received this message because you are subscribed to the Google Groups Google App Engine group. 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. -- You received this message because you are subscribed to the Google Groups Google App Engine group. 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. -- You received this message because you are subscribed to the Google Groups Google App Engine group. 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] how to use the goole app engine as backend for the iphone application
Hi everyone I have an iPhone application and want to use the Google app engine services( datastore , Google cloud storage and more ) as back end for iPhone application , so how it possible please guide me or suggest me, App Shilendra -- 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/-/3ngby-R0HBYJ. 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.
Re: [google-appengine] new Google Cloud Platform Developers Google+ page
+1
On Monday, September 3, 2012, Amy Unruh wrote:
The Cloud Platform Developer Relations team, which includes App Engine,
now has a Google Cloud Platform Developers Google+ page!
https://plus.google.com/117105793163182226623/posts
https://plus.google.com/117105793163182226623/posts/XzMhE7wxeh1
This is a good way to track news and events, including our Hangout/office
hours times, interesting articles and codelabs, etc.
It's also a good way to see what's going on with related Google
technologies, such as BigQuery and Google Cloud Storage.
-Amy
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to
google-appengine@googlegroups.comjavascript:_e({}, 'cvml',
'google-appengine@googlegroups.com');
.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com javascript:_e({}, 'cvml',
'google-appengine%2bunsubscr...@googlegroups.com');.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
--
S pozdravem,
Peter Ondruška
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
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.
Re: [google-appengine] Channel API not working in production
Aleksei - please tell us how you go with Pusher. -- 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/-/l7b3HdT6BdEJ. 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.
