[google-appengine] Re: What's the best way to keep Requirements up-to-date?

I'm on GAE standard but I don't think that makes a difference. The thread you share is interesting but goes into the direction of having versioned packages in the requirements file for even your dev environment. Trying to be more specific on the workflow I imagine, I would describe the followi

Re: [google-appengine] Re: Deploy app into two environments: Staging and Production.

Thanks a lot Elliot! That is really so much helpful! On Fri, Jan 8, 2021 at 12:01 AM 'Elliott (Cloud Platform Support)' via Google App Engine wrote: > Hello Bill, > > I was able to find the information you need at least to get started. The > following document >

[google-appengine] Re: Environment Variables inside cloud_build.yaml + PHP

Hello, I think it is possible but you have to use "options" field and "env" subfield. According to documentation [1] in "env" subfield you can specify "a list of global environment variable definitions that will exist for all build steps in this build. If a variable is defined in both globally a

Re: [google-appengine] Re: Environment Variables inside cloud_build.yaml + PHP

The documentation says use options to define a list of global env variables to be used within all build steps. Are these env variables going to persist when Laravel app (PHP) runs and reads the system environment variables? That's the tricky part. On Fri, Jan 8, 2021 at 12:26 PM 'jstsetinin' via

[google-appengine] Re: Run Runnable inside GAE task

A possible limitation you might encounter is your task taking too long. By default, the HTTP target task handlers time out after 10 minutes. You can increase this value to 30 minutes. With GAE targets, the time out depends on the scaling type the target service uses: 10 minutes for automatic,

[google-appengine] Re: What's the best way to keep Requirements up-to-date?

Managing dependencies can be tricky! You might want to check Pipenv as suggested above as it acts as a package and virtual environment management tool. It also uses a [Pipfile][1] and a [Pipfile.lock][2] rather than a requirments.txt file. The advantage of a Pipfile is it will be more accommoda

Re: [google-appengine] Re: Deploy app into two environments: Staging and Production.

My .02 but keep in mind that I don't use cloud build Build your apps to be identity aware, app.yaml doesn't even include the app id anymore, the app can know whether it's in staging or production So basically, in theory, previously you only needed a build step that renamed app.yaml's project ID

Re: [google-appengine] Re: Deploy app into two environments: Staging and Production.

The only difference is the env variables. I am considering defining this inside build_cloud.yaml file under "options" to make them global ones. However, I am not sure Laravel/PHP will pick up those env variables. I still need to try it out. On Fri, Jan 8, 2021 at 9:24 PM Kaan wrote: > My .02 bu