-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Git Deploy to Cloud Platform always FAILED. #304
Comments
Hey @chuycepeda, I tried git deployment with the vanilla gae-boilerplate, and got an error as well. I clicked the "Deploying" link (one that has an error) and saw that it was a file not found error. Could you see if you have the same error when you click on one of the failed "Deploying" links? |
try with an older version of app.cfg (If you have one that is), I had a On 6 November 2014 11:54, movero notifications@github.com wrote:
|
Interesting.... This is what Deploying link has: http://cl.ly/image/1Y3N1B2Y2p1q Any idea? I'll try to see other app.cfg versiones as you refer, @peterretief...if any success I'll let you know. Thanks ! |
rather app.yaml :) On 6 November 2014 18:35, Chuy.Cepeda notifications@github.com wrote:
|
My error message said it could not find the static error handlers, but your screenshot does not show the same message. I made a small fix for that in app.yaml (not sure if @peterretief had the same issue) which you can find here: |
hahaha, yeah *.yaml, we were speaking of the same file... I'll give a try |
Hi,
I've been developing a project in the Google Cloud Platform and recently I decided to take advantage from your boilerplate implementation since project was growing exponentially. I've deployed using git, console and GoogleAppEngineLauncher on a Mac.
Everything works fine except the git deployment, it always throws a FAILED status and the code never reaches the serving app. See: http://cl.ly/image/471l1A0M1q2w
Every successful deployment on that screenshot is considering previous, non-boilerplate, implementation.
Do you have any suggestion?
Cheers,
Chuy
The text was updated successfully, but these errors were encountered: