-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Troubles with the tutorial: Using Cloud SQL for MySQL (App Engine Flexible Environment) #664
Comments
I found the answer to my Question 2, the instance name is set in |
I'd recommend using the App Engine Standard Environment: https://cloud.google.com/appengine/docs/standard/nodejs/using-cloud-sql Deployment only takes a few seconds instead of 10 minutes. |
Too hard inplement this solution , 1 month try to connect local and when deploy still |
🤖 I have created a release \*beep\* \*boop\* --- ### [3.2.1](https://www.github.com/googleapis/nodejs-dlp/compare/v3.2.0...v3.2.1) (2021-11-03) ### Bug Fixes * **deps:** update dependency mime to v3 ([#663](https://www.github.com/googleapis/nodejs-dlp/issues/663)) ([5d33ead](https://www.github.com/googleapis/nodejs-dlp/commit/5d33ead5c207511a2ef3d268dd804eabc20408d8)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Hi, I followed steps in Using Cloud SQL for MySQL (App Engine Flexible Environment)
Everything worked and deployed successfully (8 min 21 sec for deploying?!!) until
gcloud app browse
that goes to the URL with "Internal Server Error" message.And the log shows
Error: connect ECONNREFUSED 127.0.0.1:3306
Question 1: Why does deploy of a simple app take so long to complete even on subsequent runs?
When testing locally using Cloud SQL Proxy we know that 127.0.0.1 is proxied to the Cloud SQL database that we specify in the command line like this:
but the tutorial does not explain how possibly after deployment it is supposed to connect to the database instance, since we don't have the proxy configuration on the server. And so it fails with the above error as one may expect.
Question 2: How is the app supposed to connect to the sql instance when deployed?
App.flexible.yaml
file says "Do not add this file to your source control." Is that really the recommended way to handle app.yaml files? It does not make sense that the application configuration file should be maintained outside of the repository.Question 3: What is the correct way to manage app.yaml and sensitive data in it?
Thanks!
The text was updated successfully, but these errors were encountered: