GAE + Github = Cannot Get Push-to-Deploy for Actual Work

Question

I am trying to get Push-to-Deploy to work with GAE by setting up GitHub as the source of the repo code.

It is now Day 3, and I encountered several errors, for example:

• Creating the Release pipeline for no apparent reason

• Getting error 500 when I finally managed to get the source ported to GAE

• Changes on Github apply to GAE (they are visible in Source Code → Overview), but the release procedure does not start and (of course, this is the case) the application is not served on the web address.

I tried to create some new projects, and I showed different versions of the errors above.

Here where I am now:

I created a completely new project, installed Github as my repo, created Release Pipeline, and then clicked (on Github) to try to run the Deploy routine to no avail. The code tree is visible in the Source Code → Overview, as well as commit dates, etc., but the release pipeline does not start.

The skill identifier of the application is 695, and the platform of choice is php.

Any ideas?

Update:

Almost 24 hours after I set up the project and ran the test to run the Release pipeline, it was finally done! His result is marked as "SUCCESS".

Now, if I try to hit the project URL, I get a:

Error 500 - The server encountered an error and could not complete your request. 

Any help would be greatly appreciated!

Update 2:

I got more information by looking at the logs:

 A problem was encountered with the process that handled this request, causing it to exit. This is likely to cause a new process to be used for the next request to your application. (Error code 204) 

Maybe something is wrong with my (fairly simple) app.yaml?

 application: skillful-signer-695 version: 1 runtime: php api_version: 1 threadsafe: false handlers: # Serve images as static resources. - url: /(.+\.(gif|png|jpg))$ static_files: \1 upload: .+\.(gif|png|jpg)$ application_readable: true # Serve PHP s. - url: /.* script: index.php 

It seems that many different people are experiencing the same thing, and this is related to app.yaml, but I can’t understand what I am doing wrong ... The above example is very similar to the example in the docs.

Answer 1

we were finally able to get this work - it turned out that there were some problems with the code base for the website, which led to a 500 error (for me, probably, for Code Igniter).

In addition, we had to add some lines to app.yaml for CSS and fonts. Here we are done:

 application: skillful-signer-695 version: 1 runtime: php api_version: 1 threadsafe: false handlers: - url: /assets/(.*\.(css|js|ttf))$ static_files: assets/\1 upload: assets/.*\.(css|js|ttf)$ # Serve images as static resources. - url: /(.+\.(gif|png|jpg))$ static_files: \1 upload: .+\.(gif|png|jpg)$ application_readable: true # Serve PHP s. - url: /.* script: index.php 

Besides the problems on our part, I believe that we encountered several GAE errors (inconsistent shipping time from GitHub, problems with the Dashboard, incomplete documents, etc.), which are normal for Beta software, but nevertheless unpleasant. Thanks for the help!

ps We started something else that could save someone when you dig - if you try to use sockets (for example, to send email via SMTP from your support form hosted in GAE, because the standard PHP mail command does not work ), you "Find that sockets are allowed only after entering your payment information. They do not charge you anything for easy use, but I think that Google considers this a premium feature.

All the best!

Answer 2

I'm having problems with the Push 2 Not Deploy function, because - at least for now - GAE does not allow git submodules.

If you have submodules or ignore the necessary files from git , your application will not work.

For example: I send emails from GAE, and my login_data.py ignored by git via .gitignore

If you use appcfg.py update --oauth . Your login_data.py will be sent. Using push2deploy in this situation will result in a big error, for example:

 Error: Server Error The server encountered an error and could not complete your request. Please try again in 30 seconds.