[web2py] Re: Python3 GAE 502 Error

2020-03-31 Thread Jacinto Parga
Is there any main.py example to deploy web2py in GAE with python 3.7 as it 
is in py4web?


El domingo, 21 de abril de 2019, 18:32:33 (UTC+2), Jacinto Parga escribió:
>
> Or may be what i need is just to know what is the entrypoint in the 
> app.yalm for my web2py application
>
>
> runtime: python37
> entrypoint: gunicorn -b :$PORT main:app
>
>
>
>
> El domingo, 21 de abril de 2019, 18:19:59 (UTC+2), Jacinto Parga escribió:
>>
>> The first issue (fatal:ambiguous argument'HEAD') solved just with git 
>> init. 
>>
>> The second one 'Bad Gateway' in google app engine with python3.7 not yet. 
>>
>> May be this solution valid for web2py) 
>> https://stackoverflow.com/questions/54565417/error-bad-gateway-502-when-opening-google-app-engine-python-domain
>>  
>>
>>
>>
>> El jueves, 18 de abril de 2019, 14:21:41 (UTC+2), Jacinto Parga escribió:
>>>
>>> Hi, 
>>>
>>> I'm trying to deploy my first python3 app in Google App Engine. I've 
>>> edited  app.yaml according to 
>>> https://cloud.google.com/appengine/docs/standard/python3/config/appref 
>>> . I have created .gcloudignore replacing skip files and I have deployed it 
>>> gcloud app deploy app.yaml --version  --promote
>>>
>>> But what I get is
>>>
>>> Beginning deployment of service [default]...
>>> fatal:ambiguous argument'HEAD': unknown revision or path outside the 
>>> working tree.
>>> Use '--' to separate the routes of the revisions, in this way:
>>> 'git  [...] -- [...]'
>>>
>>> I vhave checked that all the files are uploaded wrght to Google App 
>>> Engine, but when I access to the app:
>>>
>>> [image: bad-gateway-502.png]
>>> I dont know if it is an app.yaml mistale or there is somethin wrong in 
>>> web2py with python3 apps in GAE.
>>>
>>> Thanks
>>>
>>

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/web2py/fd05f3f2-a158-43e6-8660-308c273984c5%40googlegroups.com.


[web2py] Re: Python3 GAE 502 Error

2019-04-21 Thread Jacinto Parga
Or may be what i need is just to know what is the entrypoint in the 
app.yalm for my web2py application


runtime: python37
entrypoint: gunicorn -b :$PORT main:app




El domingo, 21 de abril de 2019, 18:19:59 (UTC+2), Jacinto Parga escribió:
>
> The first issue (fatal:ambiguous argument'HEAD') solved just with git 
> init. 
>
> The second one 'Bad Gateway' in google app engine with python3.7 not yet. 
>
> May be this solution valid for web2py) 
> https://stackoverflow.com/questions/54565417/error-bad-gateway-502-when-opening-google-app-engine-python-domain
>  
>
>
>
> El jueves, 18 de abril de 2019, 14:21:41 (UTC+2), Jacinto Parga escribió:
>>
>> Hi, 
>>
>> I'm trying to deploy my first python3 app in Google App Engine. I've 
>> edited  app.yaml according to 
>> https://cloud.google.com/appengine/docs/standard/python3/config/appref . 
>> I have created .gcloudignore replacing skip files and I have deployed it 
>> gcloud app deploy app.yaml --version  --promote
>>
>> But what I get is
>>
>> Beginning deployment of service [default]...
>> fatal:ambiguous argument'HEAD': unknown revision or path outside the 
>> working tree.
>> Use '--' to separate the routes of the revisions, in this way:
>> 'git  [...] -- [...]'
>>
>> I vhave checked that all the files are uploaded wrght to Google App 
>> Engine, but when I access to the app:
>>
>> [image: bad-gateway-502.png]
>> I dont know if it is an app.yaml mistale or there is somethin wrong in 
>> web2py with python3 apps in GAE.
>>
>> Thanks
>>
>

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[web2py] Re: Python3 GAE 502 Error

2019-04-21 Thread Jacinto Parga
The first issue (fatal:ambiguous argument'HEAD') solved just with git init. 

The second one 'Bad Gateway' in google app engine with python3.7 not yet. 

May be this solution valid for 
web2py) 
https://stackoverflow.com/questions/54565417/error-bad-gateway-502-when-opening-google-app-engine-python-domain
 



El jueves, 18 de abril de 2019, 14:21:41 (UTC+2), Jacinto Parga escribió:
>
> Hi, 
>
> I'm trying to deploy my first python3 app in Google App Engine. I've 
> edited  app.yaml according to 
> https://cloud.google.com/appengine/docs/standard/python3/config/appref . 
> I have created .gcloudignore replacing skip files and I have deployed it 
> gcloud app deploy app.yaml --version  --promote
>
> But what I get is
>
> Beginning deployment of service [default]...
> fatal:ambiguous argument'HEAD': unknown revision or path outside the 
> working tree.
> Use '--' to separate the routes of the revisions, in this way:
> 'git  [...] -- [...]'
>
> I vhave checked that all the files are uploaded wrght to Google App 
> Engine, but when I access to the app:
>
> [image: bad-gateway-502.png]
> I dont know if it is an app.yaml mistale or there is somethin wrong in 
> web2py with python3 apps in GAE.
>
> Thanks
>

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.