[google-appengine] Cloud Tasks alternative for Kubernetes

[Reza Manbachi]

Hi,

I am working on a project which uses task queues on App Engine. We use both 
push and pull queues. We also use ETA and count down features of task 
options.
We are in the process of moving from App Engine to Kubernetes. Is Cloud 
Tasks capable of working outside of App Engine?
What do you recommend to use instead in Kubernetes?
Is Knative eventing a viable alternative for Cloud Task?

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0c2a88cb-7181-48aa-803c-c9e335c42703%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Connecting from app engine instance to compute engine instance directly

[Jason Collins]

Check out 
https://cloud.google.com/appengine/docs/standard/python/connecting-vpc


On Thursday, 18 April 2019 06:33:59 UTC-7, Chris Santos wrote:
>
> Still can't believe we're waiting on this. Are there any updates?
>
> On Thursday, May 7, 2015 at 12:52:39 PM UTC-5, Ian Childress wrote:
>>
>> We (our Go dev team) want to connect our app engine apps to our compute 
>> engine apps directly using internal IP address. From my understanding 
>> through documentation and exhaustive searching, the solution is to use a 
>> public IP address. This solution requires whitelisting an entire ip block 
>> (Google's ip block for app engine). This both increases security risk as 
>> well as charges additional bandwidth. The other solution is to use a 
>> messaging service PubSub. This is fine for submitting tasks to be performed 
>> by the back end app, but it prevents the app engine from receiving the 
>> response from the compute engine. 
>>
>> Have I missed the solution somewhere that allows for internal 
>> communication between app engine and compute engine? Using a job queue or 
>> public IP is not a replacement for an internal socket connection.
>>
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/6a044186-2f58-413d-8ca7-318b0780be3e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: [Newbie Questions] Setting up and test a local php app before deploying in QCP

[Terry Middleton]

Harmit,

This very much does help.  Thank you for your details responses.  This goes 
a long way in helping understand the big picture of GCP and how the pieces 
fit together.   

Truly, Thank You!

Terry

PS.  QCP was a typo.  I meant to type GCP.  Not sure how that happens as 
the G and Q are really far apart on the keyboard.



On Wednesday, April 17, 2019 at 8:25:10 PM UTC-5, Harmit Rishi (Cloud 
Platform Support) wrote:
>
> Hi Terry, 
>
> Thanks for using Google Groups!
>
> I am not too sure what QCP is. Would you be able to clarify what you mean 
> by that?
>
> In regards to your questions: 
>
> 1. What can I use to develop the PHP files locally, then test them?
> Since PHP is a scripting language that is suited for web development and 
> can be used to embed into HTML, you will need a local server to run your 
> PHP code. You can check out the official installation and configuration 
> guide that PHP offers on their official website here 
> .
>
> As for a code editor, there are plenty of free ones offered on the web. 
> Typically, the one you use is based on preference.
>
> 2.Is it truly just creating the php files in a directory structure and 
> declaring the app in the yaml file?
>
> It depends on the size of your application, you may want to consult this 
> documentation 
>  
> that highlights the configuration files required for PHP on App Engine 
> standard. 
>
> 3.How do I setup my local environment?  I followed the instructions on 
> this, yet I'm missing something because I don't see where I test it locally.
>
> You may use the PHP development server for App Engine standard here 
> 
>  
> for local testing. This local dev server stimulates how your application 
> would run in production on App Engine. Additionally, the local development 
> server simulates the services provided by the libraries in the SDK for App 
> Engine (i.e: Datastore, Memcache, Task Queues, etc). You may follow the 
> instructions to set this up here 
> 
> .
>
> Side note: I believe it would be worth it for you to check out the 
> differences between our two App Engine environments (Flexible vs Standard) 
> here . 
>
>
> I hope this helps!
>
>
> On Tuesday, April 16, 2019 at 2:47:23 PM UTC-4, Terry Middleton wrote:
>>
>> Hello GAE Developers,
>>
>> I am wanting to develop a PHP app and deploy in the QCP.   I'm so close, 
>> yet I'm missing something because I'm not there yet.
>>
>> Here's what I have done so far.
>>
>>
>>- Downloaded the GCP SDK, PHP, App Engine, etc.  I've actually walked 
>>through deploying an php application (and it worked).
>>
>>
>> However, I have absolutely no idea what I did.  I just followed the 
>> instructions.  Although, I have somewhat of an idea.  I'm not 100% in the 
>> dark. I now understand what roll QCP plays and what it takes to push an app 
>> to QCP.  
>>
>> What I really want to do is create the app in PHP, test it locally, then 
>> push it out to QCP.
>>
>> My questions are:
>>
>>
>>- *What can I use to develop the PHP files locally, then test them?*
>>- *Is it truly just creating the php files in a directory structure 
>>and declaring the app in the yaml file?*
>>- *How do I setup my local environment?  I followed the instructions 
>>on this, yet I'm missing something because I don't see where I test it 
>>locally.*
>>
>>
>>
>> Any thoughts, directions, or insights would be so appreciated.  
>>
>> Terry
>>
>>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/eca87c1b-b262-42e3-addc-748d1239d917%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: The Link To WebApp3 NonPublic Repository

[Khaled Wagdy]

Yeah, it seems like diogoa said that they are using the frameworks 
mentioned in this page 
. No 
mentioning of Webapp3...

As mentioned on the page..

This quickstart demonstrates a simple Python app written with the Flask 
>  web framework that can be deployed to App 
> Engine. Although this sample uses Flask, you can use any web framework that 
> satisfies the requirements above. Alternative frameworks include Django 
> , Pyramid 
> , Bottle , and web.py .


webapp2 did have some advantages like using deferred library easily for 
example, other frameworks may have other advantages though, specially with 
AppEngine moving to support Python3


On Wednesday, April 17, 2019 at 4:03:49 PM UTC+2, Marcus Eagan wrote:
>
> Hello there, 
>
> I've recently looked into using webapp3 with a few wishes: that there is a 
> lightweight framework  for working with Google App Engine that evolved from 
> WebApp2, and that the next generation framework supports python 3. The 
> repository listed at this website does not appear to exist, perhaps because 
> it is private: https://webapp2.readthedocs.io/features.html
>
> This sort of information is critical for developers looking to adopt the 
> platform or increase our existing footprint.
>
> Furthermore, links to documentation for both WebApp2 and WebApp3 are down. 
> Please advise on what I can do about the repository and what's going on 
> with the documentation.
>
> Thanks,
>
> Marcus
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b79e7df3-d499-493a-b3f6-2aad4d56d38e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Connecting from app engine instance to compute engine instance directly

[Chris Santos]

Still can't believe we're waiting on this. Are there any updates?

On Thursday, May 7, 2015 at 12:52:39 PM UTC-5, Ian Childress wrote:
>
> We (our Go dev team) want to connect our app engine apps to our compute 
> engine apps directly using internal IP address. From my understanding 
> through documentation and exhaustive searching, the solution is to use a 
> public IP address. This solution requires whitelisting an entire ip block 
> (Google's ip block for app engine). This both increases security risk as 
> well as charges additional bandwidth. The other solution is to use a 
> messaging service PubSub. This is fine for submitting tasks to be performed 
> by the back end app, but it prevents the app engine from receiving the 
> response from the compute engine. 
>
> Have I missed the solution somewhere that allows for internal 
> communication between app engine and compute engine? Using a job queue or 
> public IP is not a replacement for an internal socket connection.
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0aca3e79-764c-40cd-a490-3c48789448a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: DevAppServerTest @Rule problem

[Mariateresa Cava]

Thank you for your support. I've already posted this on Stackoverflow. 
Anyone who has other suggestions?

On Wednesday, April 17, 2019 at 11:26:42 PM UTC+2, yka...@google.com wrote:
>
> I think it would be best to post this on Stackoverflow with a code snippet 
> and the stack trace as it is better suited for technical development 
> questions.
>
> You can also check this doc 
> 
>  for 
> an example as well.
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/6366d960-989f-4c5c-8137-dcdd3ddba145%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.