將 MySQL 資料庫遷移至 Google Cloud SQL：挑戰實驗室 Reviews

Jomark C. · Reviewed almost 4 years ago

this shii is not working freaking give more steps and command to runnnn

abdirahman I. · Reviewed almost 4 years ago

Mykhailo Z. · Reviewed almost 4 years ago

Katia Kaori K. · Reviewed almost 4 years ago

Nakayama M. · Reviewed almost 4 years ago

ASHISH R. · Reviewed almost 4 years ago

Roland Adrian I. · Reviewed almost 4 years ago

it works...

Carlos V. · Reviewed almost 4 years ago

Carlos V. · Reviewed almost 4 years ago

JUTTUKA H. · Reviewed almost 4 years ago

William M. · Reviewed almost 4 years ago

The lab is broken because the system reports "Your PHP Installation Appears to be Missing the MySQL Extension Which is Required by WordPress". So the blog was not running in the first place.

Kalyan K. · Reviewed almost 4 years ago

The lab is broken because the system reports "Your PHP Installation Appears to be Missing the MySQL Extension Which is Required by WordPress". So the blog was not running in the first place.

Kalyan K. · Reviewed almost 4 years ago

Gopal B. · Reviewed almost 4 years ago

Maksym K. · Reviewed almost 4 years ago

Ewelina K. · Reviewed almost 4 years ago

Piotr M. · Reviewed almost 4 years ago

Przemysław D. · Reviewed almost 4 years ago

Aleksander C. · Reviewed almost 4 years ago

Michael G. · Reviewed almost 4 years ago

Christian B. · Reviewed almost 4 years ago

Paweł M. · Reviewed almost 4 years ago

"Check that the blog instance is authorized to access Cloud SQL" test fails even though both "lab-monitor" and "blog" VMs are able to connect to cloud SQL instance. The message returned by the check is this: Check complete. Points earned: 0. Message: No matching authorization found. Instance IPs: ["34.168.80.26", "35.233.193.251"] Cloud SQL authorization ranges: ["34.168.80.26", "35.233.193.251"] Why? update: if you grant in CloudSQL instance connection whitelist "0.0.0.0/0" then it works, which is not good at all. Another idea would be to set the VM IP in CIDR notation which I have not tried and may fix the problem and be more secure than wildcard

Giorgi J. · Reviewed almost 4 years ago

documentation was linked was vague and unhelpful for the use case

Herleen K. · Reviewed almost 4 years ago

Gaby C. · Reviewed almost 4 years ago