[google-appengine] Re: Naked and www custom domains with Google App Engine
Ok, seems that it is available everywhere except Turkey, got to look into this On Saturday, August 29, 2015 at 10:01:54 AM UTC+3, Richard Cheesmar wrote: I have added two custom domains to Google Developers Console for a Google App Project. One, a naked domain with A and AAA records set on the third party DNS manager as specified by Google. Two, a www domain with a Cname record set on the third party DNS manager, as specified by Google. The www is serving, but the naked domain is not! The A records ip addresses timeout on my local machine but I get results when using http://tools.pingdom.com/ping/ Obviously you can use more than one custom domain but is there something I'm missing here? -- 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/3f80a71f-c68e-4fb0-8147-93aa8803f370%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Rate Limit Exceeded when creating new project through devloper's console
I am having the same exact problem. Not a great onboard experience when even creating a new project fails... On Thursday, July 9, 2015 at 6:20:36 AM UTC-7, Phil Side wrote: I'm getting the message Rate Limit Exceeded when I try to create a new project through the developer's console. I have no idea what rate it is referring to, and so no idea how to fix the problem. Any help would be appreciated. -- 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/6846498c-003e-4d2b-8d5c-c6f428bfa959%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Naked and www custom domains with Google App Engine
I have added two custom domains to Google Developers Console for a Google App Project. One, a naked domain with A and AAA records set on the third party DNS manager as specified by Google. Two, a www domain with a Cname record set on the third party DNS manager, as specified by Google. The www is serving, but the naked domain is not! The A records ip addresses timeout on my local machine but I get results when using http://tools.pingdom.com/ping/ Obviously you can use more than one custom domain but is there something I'm missing here? -- 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/9a37831f-ff60-4785-be69-26c2c855fa11%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Google Cloud Storage File Upload Issue
Issue Description : I'm running php application Google App Engine and we would like to upload all files on Google cloud storage. Here is the API class CloudStorageTools when i try to create instance of this class, it shows class not error. -- 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/52bf1eb2-95f4-4447-a870-b72dbee7b68a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] Re: Static SQLite files
When you want to run in App Engine but also need some modules or extension that the App Engine sandbox does not support, consider using managed VMs https://cloud.google.com/appengine/docs/managed-vms/ (MVMs). For example, here https://github.com/GoogleCloudPlatform/appengine-sqlite-guestbook-python's a Python App Engine version of the usual guestbook example app using exactly sqlite for its storage layer. It's important to note that, if your App Engine app is properly structured into *modules*, as Google recommends (if you think you're not using modules, you are anyway: what you think as your app is actually your app's default module and you're just currently choosing not to add others), you can mix and match traditional (sandboxed, thus unable to use certain modules and extensions such as sqlite) and MVM-hosted modules, for maximum flexibility. The only key thing to keep in mind is that managed VMs are in *beta*: thus, perfectly suitable for development and experimenting, but not yet for production deployment at scale. Requesting a new feature for traditional (sandboxed) App Engine, that's already present in MVMs, as Patrice suggested (such as, the ability to use sqlite, or some other module or extensions not currently supported in the sandbox), is clearly possible. However, such a new feature request, if and when accepted, will also have to go through its own period of development, testing, and then beta release, before it's released as generally available (out of beta, thus fully supported and recommended for production deployments). Therefore, even if you do choose to open such a feature request, I would recommend *also*, at the same time, trying out the deployment of an experimental version of your app (ideally, only the one new module requiring sqlite3, with the other modules remaining sandboxed) on MVMs -- so you'll be ready for production deployment when any positive news emerges, one way or another. Yet another workaround to help tide you over is Cloud SQL https://cloud.google.com/sql/docs/introduction -- it's MySQL, not sqlite3, but migration between SQL dialects is usually much easier than moving to NoSQL DBs such as the App Engine datastore; and, Cloud SQL is fully supported (not beta!). So, you could immediately deploy the database access module in production in a sandboxed variant using Cloud SQL, while also developing and experimenting with a MVM-deployed variant for the time when, one way or another, sqlite3 will be available in the way you prefer and fully supported for production use. Alex On Fri, Aug 28, 2015 at 9:06 PM, Tomasz Jamróz mojad...@gmail.com wrote: Hi, I am facing similar problem and found out that the most probable reason is sandbox.py not having '_sqlite3' in _WHITE_LIST_C_MODULES. After adding _sqlite3 to _WHITE_LIST_C_MODULES in my local sandbox.py I managed to both import sqlite3 and execute queries to the database with script running on GAE on my local machine. After deployment, however, the server threw 500 error. Is it possible that you fix this problem? I understand that your policy is to encourage users to use Datastore, but in some cases using sqlite3 is really needed for reasons of compatibility with other apps already existing. Thanks On Saturday, August 29, 2015 at 2:12:42 AM UTC+9, Patrice (Cloud Platform Support) wrote: Hi Johnny, While I can't promise anything, you would have more traction for such a request by posting it on our issue tracker, here https://code.google.com/p/googleappengine/issues/list. Post this with as much information as you can, and we'll follow up there to see what can be done. Cheers, and have a good weekend! On Thursday, August 27, 2015 at 8:58:40 PM UTC-4, Jonny Bergström wrote: I know this is ages later, but I am constantly having the same need; if only I could at least read sqlite files in memory. I've been fiddling with trying to get a pure python sqlite implementation running and what not but never succeeded at anything. Being able to at least read sqlite files would make GAE much more useful to me. On Tuesday, July 19, 2011 at 1:06:16 AM UTC+9, Jim Cipar wrote: That doesn't solve either of my problems. I'm not trying to use SQLite instead of DataStore, I'm trying to use it instead of static CSV files. To paraphrase the SQLite documentation: don't think of SQLite as a replacement for MySQL, think of it as a replacement for fopen(). I want a lightweight structured file format for *static* data. Serving static data out of DataStore is a waste of resources. Secondly, DataStore doesn't solve the complex query problem. It can't do JOIN, GROUP BY, or any kind of nested queries. Lastly, a memory-only SQLite instance is a very useful abstraction for doing data transformations even when you're not worried about persistence at all. Even if we could simply load the SQLite module for memory-only databases that would be a step in the right direction, though storing my
[google-appengine] Re: Problems with SSL on a custom domain
Like I mentioned previously, today I got another user from the UK reporting a similar issue. For some reason the SNI SSL served version of my app isn't reachable or working for them, but going to https://myapp.appspot.com works. I don't see a huge drop in usage in the app so I can't really tell what is causing it, just that those users can't establish a SSL connection to my custom domain url from their devices. Hugo On Wednesday, August 26, 2015 at 9:09:52 PM UTC+2, Patrice (Cloud Platform Support) wrote: Hi again Jon, I continued trying to find what is exactly happening here. So here goes : Running this in San Francisco : openssl s_client -debug -msg -servername dashboard.geospock.com -connect dashboard.geospock.com:443 -showcerts works perfectly and consistently. So I think we can all see that SF won't have issues connecting here. I then connected through an European location, and from there, trying this also succeeds: openssl s_client -servername dashboard.geospock.com -connect 64.233.167.121:443 -showcerts curl -k -I --resolve dashboard.geospock.com:443:64.233.167.121 https://dashboard.geospock.com/ From your error and your message, I get you're using TLS 1.0, while I am running with TLS 1.2. I started looking into the version of openSSL we're both using, and while you're using the 0.98zg, I am on 1.0.1f. I believe since 0.9.8j SNI support was part of OpenSSL, so you using 0.98zg should work fine, but as a test, do you mind trying to run the same with 1.01 latest? I believe they are up to 1.0.1p. If I remember correctly, there was a backport patch implemented in 0.9.8j to let openSSL work with SNI (https://en.wikipedia.org/wiki/Server_Name_Indication ). The basis of the issue we have here is that I'm incapable of reproducing any of the behaviors you're experiencing, so it's hard to investigate further. I'm definitely interested in continuing this, but without a reliable way for me to replicate, it's impossible to send it up the chain to get it looked at and possibly fixed. If you have a specific test case that consistently fail, that I can then reproduce on my side as consistently, I'll be able to get some traction on this. Thanks On Wednesday, August 26, 2015 at 11:16:54 AM UTC-4, Jon Travers wrote: Here is some more detailed debugging information from the failing openssl SSL negotiation. Perhaps this would give you a clue what's actually going on?: $ openssl s_client -debug -msg -servername dashboard.geospock.com -connect dashboard.geospock.com:443 -showcerts CONNECTED(0003) write to 0x7f96b8d006a0 [0x7f96b9802000] (131 bytes = 131 (0x83)) - 16 03 01 00 7e 01 00 00-7a 03 01 55 dd d7 93 c7 ~...z..U 0010 - f0 b2 0d ee ea f4 1c 2b-ee 50 b6 ff 0f e6 8f 59 ...+.P.Y 0020 - 8b 81 9e 05 2f 17 84 e2-20 ed b7 00 00 2e 00 39 /... ..9 0030 - 00 38 00 35 00 16 00 13-00 0a 00 33 00 32 00 2f .8.5...3.2./ 0040 - 00 9a 00 99 00 96 00 05-00 04 00 15 00 12 00 09 0050 - 00 14 00 11 00 08 00 06-00 03 00 ff 01 00 00 23 ...# 0060 - 00 00 00 1b 00 19 00 00-16 64 61 73 68 62 6f 61 .dashboa 0070 - 72 64 2e 67 65 6f 73 70-6f 63 6b 2e 63 6f 6d 00 rd.geospock.com. 0080 - 23# 0083 - SPACES/NULS TLS 1.0 Handshake [length 007e], ClientHello 01 00 00 7a 03 01 55 dd d7 93 c7 f0 b2 0d ee ea f4 1c 2b ee 50 b6 ff 0f e6 8f 59 8b 81 9e 05 2f 17 84 e2 20 ed b7 00 00 2e 00 39 00 38 00 35 00 16 00 13 00 0a 00 33 00 32 00 2f 00 9a 00 99 00 96 00 05 00 04 00 15 00 12 00 09 00 14 00 11 00 08 00 06 00 03 00 ff 01 00 00 23 00 00 00 1b 00 19 00 00 16 64 61 73 68 62 6f 61 72 64 2e 67 65 6f 73 70 6f 63 6b 2e 63 6f 6d 00 23 00 00 read from 0x7f96b8d006a0 [0x7f96b9807600] (7 bytes = 7 (0x7)) - 15 03 01 00 02 02 2f ../ TLS 1.0 Alert [length 0002], fatal illegal_parameter 02 2f 8175:error:14077417:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert illegal parameter:/SourceCache/OpenSSL098/OpenSSL098-52.40.1/src/ssl/s23_clnt.c:593: -- 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/a5153c60-8281-4606-816f-8f345aec2edc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Google Cloud Storage File Upload Issue
Do you have any code snippet that you can shared? Have you read https://cloud.google.com/appengine/docs/php/googlestorage/user_upload? On Saturday, August 29, 2015 at 11:05:18 AM UTC-7, Furpurr The wrote: Issue Description : I'm running php application Google App Engine and we would like to upload all files on Google cloud storage. Here is the API class CloudStorageTools when i try to create instance of this class, it shows class not error. -- 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/646e1055-d17b-475d-a799-034edcab825f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Lightweight Identity for App Engine Java
The User service is handy and simple. That it only handles Google accounts is a problem for me. I've created a lightweight identity library (LID) which is similar to the User service and provides authentication for Google, Facebook and any Email. Google auth is via the User service, Facebook via OAuth and Email via an Email sent to the user which contains a URL they visit to sign in. Sign-in is cookie based. There is a demo at https://cilogi-liddemo.appspot.com. The library is on Github at https://github.com/cilogi/lid. Its not general purpose, requiring Guice and running only on App Engine but it may be useful for someone if the User service is functionally OK but doesn't provide enough coverage. Tim -- 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/1bec00b9-0eff-44d2-a3dd-06f629b2fff0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
