Re: [google-appengine] Re: Future of dev_appserver.py - deprecated?

2019-06-17 Thread 'Nicolas (Google Cloud Platform Support)' via Google App Engine


Hi, 

 

I totally agree with you, we have to make App Engine the easiest and most 
intuitive experience the developer that's why in the second generation 

 
we made it easier to run locally by being able to run locally 

 
with the tools that you normally use.

 

Alse you can test your application 

 
by deploying with the --no-promote flag which would deploy the application 
without allocating any traffic to the deployed version.

 

gcloud app deploy --no-promote 



On Sunday, June 16, 2019 at 12:36:29 PM UTC-4, dir Ls wrote:
>
> The purpose of app engine standard is so developers can focus no the app 
> and not worry about the rest. To me, dev_appserver.py is a pre-req to 
> encourage app developers to get on to GCP very easily. Hope App Engine 
> Standard itself is not going to get deprecated!
>
> On Friday, June 14, 2019 at 3:43:41 PM UTC-7, Andrew Gorcester wrote:
>>
>> We don't have a replacement for that functionality yet, but I'll record 
>> that that's a missing link for people migrating. Thank you!
>>
>> On Fri, Jun 14, 2019 at 3:02 PM Nicolas Grilly  
>> wrote:
>>
>>> On Friday, June 14, 2019 at 11:10:21 PM UTC+2, Andrew Gorcester wrote:

 If you don't mind me asking, what are the features of dev_appserver.py 
 that are still useful with the newer runtimes, which do not have App 
 Engine-specific APIs and client libraries that dev_appserver was 
 originally 
 intended to mock and emulate?

>>>
>>> dev_appserver.py seems still useful to emulate dispatch.yaml and static 
>>> handlers locally. Is there an alternative?
>>>
>>> -- 
>>> 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-a...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-appengine/e827acfd-b148-4d49-a8d8-da676e9c79f4%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e08af061-dacf-40a6-b521-09e46f052d04%40googlegroups.com.


Re: [google-appengine] Re: Future of dev_appserver.py - deprecated?

2019-06-16 Thread dir Ls
The purpose of app engine standard is so developers can focus no the app 
and not worry about the rest. To me, dev_appserver.py is a pre-req to 
encourage app developers to get on to GCP very easily. Hope App Engine 
Standard itself is not going to get deprecated!

On Friday, June 14, 2019 at 3:43:41 PM UTC-7, Andrew Gorcester wrote:
>
> We don't have a replacement for that functionality yet, but I'll record 
> that that's a missing link for people migrating. Thank you!
>
> On Fri, Jun 14, 2019 at 3:02 PM Nicolas Grilly  > wrote:
>
>> On Friday, June 14, 2019 at 11:10:21 PM UTC+2, Andrew Gorcester wrote:
>>>
>>> If you don't mind me asking, what are the features of dev_appserver.py 
>>> that are still useful with the newer runtimes, which do not have App 
>>> Engine-specific APIs and client libraries that dev_appserver was originally 
>>> intended to mock and emulate?
>>>
>>
>> dev_appserver.py seems still useful to emulate dispatch.yaml and static 
>> handlers locally. Is there an alternative?
>>
>> -- 
>> 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-a...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/e827acfd-b148-4d49-a8d8-da676e9c79f4%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b4e3f367-c21b-47f4-b6cc-c361e1984efc%40googlegroups.com.


Re: [google-appengine] Re: Future of dev_appserver.py - deprecated?

2019-06-14 Thread 'Andrew Gorcester' via Google App Engine
We don't have a replacement for that functionality yet, but I'll record
that that's a missing link for people migrating. Thank you!

On Fri, Jun 14, 2019 at 3:02 PM Nicolas Grilly 
wrote:

> On Friday, June 14, 2019 at 11:10:21 PM UTC+2, Andrew Gorcester wrote:
>>
>> If you don't mind me asking, what are the features of dev_appserver.py
>> that are still useful with the newer runtimes, which do not have App
>> Engine-specific APIs and client libraries that dev_appserver was originally
>> intended to mock and emulate?
>>
>
> dev_appserver.py seems still useful to emulate dispatch.yaml and static
> handlers locally. Is there an alternative?
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/e827acfd-b148-4d49-a8d8-da676e9c79f4%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJvgea0PLXyRvcXP%3DDg-Lhoo2VDUXiVfNKT%2BYMxR%2BBCBg%40mail.gmail.com.


Re: [google-appengine] Re: Future of dev_appserver.py - deprecated?

2019-06-14 Thread Nicolas Grilly
On Friday, June 14, 2019 at 11:10:21 PM UTC+2, Andrew Gorcester wrote:
>
> If you don't mind me asking, what are the features of dev_appserver.py 
> that are still useful with the newer runtimes, which do not have App 
> Engine-specific APIs and client libraries that dev_appserver was originally 
> intended to mock and emulate?
>

dev_appserver.py seems still useful to emulate dispatch.yaml and static 
handlers locally. Is there an alternative?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e827acfd-b148-4d49-a8d8-da676e9c79f4%40googlegroups.com.


Re: [google-appengine] Re: Future of dev_appserver.py - deprecated?

2019-06-14 Thread 'Andrew Gorcester' via Google App Engine
The recommended alternative is to use what is idiomatic for your framework
or other development process, as you would outside of Google Cloud. This is
now possible because we no longer require the use of App Engine-specific
APIs, handlers definitions, etc. However, dev_appserver.py did have some
features beyond emulating App Engine APIs and processing handlers that some
people have integrated into their workflows, so if this new approach
doesn't work well for you, please let us know where the pain points are.

On Fri, Jun 14, 2019 at 2:10 PM James Crowley 
wrote:

> If there are alternatives I'm missing this would be awesome? The feedback
> cycle is super slow when testing Google cloud specific code when it takes
> 30 seconds+ to update a running app (and that's ignoring the downsides of
> only being able to work online)
>
> Thanks
>
> J
>
> On Friday, 14 June 2019 01:32:52 UTC+2, James Crowley wrote:
>>
>>
>> Am I right in inferring that dev_appserver.py is on the way to being
>> deprecated, given the later language versions are not supported?
>>
>> I've tripped up trying to use it in the php7 environment - it prompts me
>> to provide a --php_executable argument for php72 environments (making me
>> think it was supported), but then doesn't seem to actually support the
>> environment ("The url "/" does not match any handlers." which goes away
>> when you use the php55 app.yaml syntax for specifying handlers rather than
>> the single entrypoint parameter)
>>
>> I then noticed it's not mentioned in the docs for php72/Java 11 etc at
>> all?
>>
>> Thanks!
>>
>> James
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/23ab05d6-eb3b-45f2-8282-479f7c3f14ec%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFLGEJAHFMnAAvcfkTNYfRQVa6DnqKCEb50R1PTxbuDKGA%40mail.gmail.com.


[google-appengine] Re: Future of dev_appserver.py - deprecated?

2019-06-14 Thread James Crowley
If there are alternatives I'm missing this would be awesome? The feedback 
cycle is super slow when testing Google cloud specific code when it takes 
30 seconds+ to update a running app (and that's ignoring the downsides of 
only being able to work online)

Thanks

J

On Friday, 14 June 2019 01:32:52 UTC+2, James Crowley wrote:
>
>
> Am I right in inferring that dev_appserver.py is on the way to being 
> deprecated, given the later language versions are not supported?
>
> I've tripped up trying to use it in the php7 environment - it prompts me 
> to provide a --php_executable argument for php72 environments (making me 
> think it was supported), but then doesn't seem to actually support the 
> environment ("The url "/" does not match any handlers." which goes away 
> when you use the php55 app.yaml syntax for specifying handlers rather than 
> the single entrypoint parameter)
>
> I then noticed it's not mentioned in the docs for php72/Java 11 etc at all?
>
> Thanks!
>
> James
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/23ab05d6-eb3b-45f2-8282-479f7c3f14ec%40googlegroups.com.


Re: [google-appengine] Re: Future of dev_appserver.py - deprecated?

2019-06-14 Thread 'Andrew Gorcester' via Google App Engine
We're aiming to build all of our new runtimes so that they don't require
dev_appserver.py, by making them support the same APIs and idiomatic local
development practices that one would use on any platform. If you don't mind
me asking, what are the features of dev_appserver.py that are still useful
with the newer runtimes, which do not have App Engine-specific APIs and
client libraries that dev_appserver was originally intended to mock and
emulate?

On Fri, Jun 14, 2019 at 9:31 AM 'Nicolas (Google Cloud Platform Support)'
via Google App Engine  wrote:

> Hi James,
>
>
>
> Thanks for opening this thread,
>
>
>
> To answer your question you are right the dev_appserver.py
> 
> is not supported with the PHP 7.2 and PHP 7.3 runtimes.
>
>
>
> To test your app locally you can download and install PHP 7.2 or PHP 7.3
> and set up a web server.
>
>
> Dev_appserver.py will still be available for PHP 5/7
> 
> and no deprecation is planned for the moment.
>
>
>
>
>
> On Thursday, June 13, 2019 at 7:32:52 PM UTC-4, James Crowley wrote:
>>
>>
>> Am I right in inferring that dev_appserver.py is on the way to being
>> deprecated, given the later language versions are not supported?
>>
>> I've tripped up trying to use it in the php7 environment - it prompts me
>> to provide a --php_executable argument for php72 environments (making me
>> think it was supported), but then doesn't seem to actually support the
>> environment ("The url "/" does not match any handlers." which goes away
>> when you use the php55 app.yaml syntax for specifying handlers rather than
>> the single entrypoint parameter)
>>
>> I then noticed it's not mentioned in the docs for php72/Java 11 etc at
>> all?
>>
>> Thanks!
>>
>> James
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/478d514d-d1b4-46a4-9e91-9fb715cc7439%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJkJkRJJRqpMeCjB4LSY50oYS4TnB67TLqAgf6cbLQ9Ww%40mail.gmail.com.


[google-appengine] Re: Future of dev_appserver.py - deprecated?

2019-06-14 Thread 'Nicolas (Google Cloud Platform Support)' via Google App Engine


Hi James, 

 

Thanks for opening this thread, 

 

To answer your question you are right the dev_appserver.py 

 
is not supported with the PHP 7.2 and PHP 7.3 runtimes. 

 

To test your app locally you can download and install PHP 7.2 or PHP 7.3 
and set up a web server.

 
Dev_appserver.py will still be available for PHP 5/7 

 
and no deprecation is planned for the moment.





On Thursday, June 13, 2019 at 7:32:52 PM UTC-4, James Crowley wrote:
>
>
> Am I right in inferring that dev_appserver.py is on the way to being 
> deprecated, given the later language versions are not supported?
>
> I've tripped up trying to use it in the php7 environment - it prompts me 
> to provide a --php_executable argument for php72 environments (making me 
> think it was supported), but then doesn't seem to actually support the 
> environment ("The url "/" does not match any handlers." which goes away 
> when you use the php55 app.yaml syntax for specifying handlers rather than 
> the single entrypoint parameter)
>
> I then noticed it's not mentioned in the docs for php72/Java 11 etc at all?
>
> Thanks!
>
> James
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/478d514d-d1b4-46a4-9e91-9fb715cc7439%40googlegroups.com.