I have temporarily solved this problem, as described here:
https://groups.google.com/forum/?fromgroups=#!topic/web2py/vs39zZpaH7g
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
-
Dear Massimo,
I am only writing again as a reminder because you said last month you would
look into this asap. This is very important I think as one of the key
offerings of web2py, supporting GAE, seems to be broken. At least for me.
Thanks!
--
Resources:
- http://web2py.com
-
Hello Massimo,
One more piece of information that might be useful:
One Google support person at the "Google App Engine" forum here told me my
login attempt was made with password "password", which is NOT the password
I set into the environment variable as seen in my attempted hack above, as
Thanks, Massimo.
FYI, some more info that might be helpful in your investigation:
Google docs tell me that my app is granted access to the SQL instance by
default, as it is in the same project with the Cloud SQL license, so
there's nothing to do there. Also, I set a password for the root user
I have not tried it but I have an interest in it. I will try asap and will
make sure it works.
On Tuesday, 25 April 2017 00:54:08 UTC-5, Karoly Kantor wrote:
>
> Dear Sirs,
>
> I can connect my Google App Engine web2py app to a first generation GAE
> SQL instance, but not to a second generation
5 matches
Mail list logo
