More improvements

Author: ryanmats

.travis.yml

@@ -24,13 +24,14 @@ matrix:
   include:
     - php: 5.6
       env: RUN_DEVSERVER_TESTS=true RUN_CS_FIXER=true
-    - php: 7.0
+    - php: 7.0.8
+    - php: 7.1
 
 env:
   global:
     - GOOGLE_APPLICATION_CREDENTIALS=$TRAVIS_BUILD_DIR/credentials.json
     - GOOGLE_VERSION_ID=$TRAVIS_JOB_ID
-    - PATH=${HOME}/google-cloud-sdk/bin:${PATH}
+    - PATH="${HOME}/google-cloud-sdk/bin:${PATH}"
     - PHP_CGI_PATH=/home/travis/.phpenv/shims/php-cgi
     - TEST_BUILD_DIR=$TRAVIS_BUILD_DIR
 
@@ -41,7 +42,7 @@ before_install:
   - mkdir -p build/logs
 
 before_script:
-  - travis_retry pecl install grpc-1.4.1
+  - travis_retry pecl install grpc
 
 script:
   - testing/run_all_tests.sh

appengine/wordpress/README.md

@@ -2,20 +2,19 @@
 
 This is a small command line tool for downloading and configuring
 WordPress for Google Cloud Platform. The script allows you to create a
-working WordPress project for
-[App Engine standard environment][appengine-standard] or
+working WordPress project for the
+[App Engine standard environment][appengine-standard] or the
 [App Engine flexible environment][appengine-flexible].
 
 ## Common Prerequisites
 
 * Install [Composer][composer]
-* Create a new Cloud Project on [Developers Console][dev-console]
+* Create a new Cloud Project using the [Cloud Console][cloud-console]
 * Enable Billing on that project
 * [Enable Cloud SQL API][cloud-sql-api-enable]
 * Install [Google Cloud SDK][gcloud-sdk]
-
-## Prerequisites for standard environment only
-* Install mysql
+* [Install mysql-client][mysql-client]
+* [Install Memcache][memcache-installation]
 
 ## Project preparation
 
@@ -31,22 +30,21 @@ Create an App Engine application within your new project:
 $ gcloud app create
 ```
 
-Then configure the App Engine default GCS bucket for later use. The
-default App Engine bucket looks like
-YOUR_PROJECT_ID.appspot.com. Change the default acl of that bucket as
-follows:
+Then configure the App Engine default GCS bucket for later use. The default App
+Engine bucket looks like YOUR_PROJECT_ID.appspot.com. Change the default Access
+Control List (ACL) of that bucket as follows:
 
 ```
 $ gsutil defacl ch -u AllUsers:R gs://YOUR_PROJECT_ID.appspot.com
 ```
 
-### Create and configure a Cloud SQL 2nd generation instance
+### Create and configure a Cloud SQL for MySQL 2nd generation instance
 
 Note: In this guide, we use `wp` for various resource names; the instance
 name, the database name, and the user name.
-
-You can create a new Cloud SQL Second Generation instance with the
-following command:
+    
+Create a new Cloud SQL for MySQL Second Generation instance with the following
+command:
 
 ```
 $ gcloud sql instances create wp \
@@ -61,11 +59,11 @@ $ gcloud sql users set-password root % \
   --instance wp --password=YOUR_INSTANCE_ROOT_PASSWORD # Don't use this password!
 ```
 
-To access this MySQL instance, we’ll use Cloud SQL Proxy. Follow
-[these instructions][cloud-sql-proxy-download] to install the Cloud SQL Proxy
-client on your local machine and make it executable.
+To access this MySQL instance, use Cloud SQL Proxy. 
+Download an appropriate binary from
+[the download page][cloud-sql-proxy-download] and make it executable.
 
-If you haven’t created a service account for the project, please
+If you haven’t created a service account for the project, 
 create it on [the Credentials section][credentials-section] in the
 Console. Click 'Create credentials' and then click 'Service account key.' For
 the Service account, select 'App Engine app default service account.' Then
@@ -78,23 +76,20 @@ Run the proxy by the following command:
 $ cloud_sql_proxy \
   -dir /tmp/cloudsql \
     -instances=YOUR_PROJECT_ID:us-central1:wp=tcp:3306 \
-      -credential_file=PATH_TO_YOUR_SERVICE_ACCOUNT_JSON
+      -credential_file=PATH_TO_YOUR_SERVICE_ACCOUNT_JSON_FILE
 ```
 
-Now you can access to the Cloud SQL instance with the normal MySQL
-client. Please create a new database and a user as follows:
+Now you can access the Cloud SQL instance with the MySQL client. Create a new
+database and a user as follows:
 
 ```
 $ mysql -h 127.0.0.1 -u root -p
 mysql> create database wp;
 mysql> create user 'wp'@'%' identified by 'PASSWORD'; // Don't use this password!
 mysql> grant all on wp.* to 'wp'@'%';
 mysql> exit
-Bye
 ```
 
-In the above example, I created a new database wp and a new user wp.
-
 ## How to use
 
 First install the dependencies in this directory as follows:
@@ -104,17 +99,17 @@ $ composer install
 ```
 
 If it complains about extensions, please install `phar` and `zip` PHP
-extesions and retry.
+extensions and retry.
 
 Then run the helper command.
 
 ```
 $ php wordpress-helper.php setup
 ```
 
-The command asks you several questions, please answer them. Then
-you'll have a new WordPress project. By default it will create
-`my-wordpress-project` in the current directory.
+The command asks you several questions, please answer them. Then you'll have a
+new WordPress project. By default it will create `my-wordpress-project` in the
+current directory.
 
 ## Run WordPress locally and create a new user (for standard environment)
 
@@ -134,7 +129,7 @@ $ vendor/bin/wp server --path=wordpress
 
 Then access http://localhost:8080/. Follow the installation steps,
 create the admin user and its password. Login to the Dashboard and
-update if any of the plugins have update.
+update if any of the plugins have updates.
 
 Now it’s ready for the first deployment.
 
@@ -150,25 +145,26 @@ $ gcloud app deploy \
 Then access your site, and continue the installation step. The URL is:
 https://PROJECT_ID.appspot.com/
 
-Go to the Dashboard, and in the Plugins page, activate the following
+Go to the Dashboard at https://PROJECT_ID.appspot.com/wp-admin. On the Plugins page, activate the following
 plugins:
 
 
-- For standard environment
-  - App Engine WordPress plugin (also set the e-mail address in its
-    setting page)
+- For the standard environment
   - Batcache Manager
-- For flexible environment
+  - Google App Engine for WordPress (also set the e-mail address in its
+    settings page)
+- For the flexible environment
   - Batcache Manager
   - GCS media plugin
 
-After activating the plugins, try uploading a media and confirm the
-image is uploaded to the GCS bucket.
+After activating the plugins, try uploading a media object in a new post 
+and confirm the image is uploaded to the GCS bucket by visiting the 
+[Google Cloud console's Storage page][cloud-storage-console].
 
 ## Check if the Batcache plugin is working
 
-On the plugin page in the WordPress dashboard, you should see 2
-drop-ins are activated; `advanced-cache.php` and `object-cache.php`.
+On the plugin page in the WordPress dashboard, click on the Drop-ins tab. You
+should see 2 drop-ins are activated: `advanced-cache.php` and `object-cache.php`.
 
 To make sure it’s really working, you can open an incognito window and
 visit the site because the cache plugin only serves from cache to
@@ -178,14 +174,17 @@ check the hit ratio and number of items in cache.
 
 ## Various workflows
 
-### Install/Update plugins/themes
+### Install/Update Wordpress, plugins, and themes
 
 Because the wp-content directory on the server is read-only, you have
 to do this locally. Run WordPress locally and update plugins/themes in
 the local Dashboard, then deploy, then activate them in the production
-Dashboard. You can also use the `wp-cli` utility as follows:
+Dashboard. You can also use the `wp-cli` utility as follows (be sure to keep
+the cloud SQL proxy running):
 
 ```
+# To update Wordpress itself
+$ vendor/bin/wp core update --path=wordpress
 # To update all the plugins
 $ vendor/bin/wp plugin update --all --path=wordpress
 # To update all the themes
@@ -198,17 +197,10 @@ First Deactivate them in the production Dashboard, then remove them
 completely locally. The next deployment will remove those files from
 the production environment.
 
-### Update WordPress itself
-
-Most of the case, just download the newest WordPress and overwrite the
-existing wordpress directory. It is still possible that the existing
-config files are not compatible with the newest WordPress, so please
-update the config file manually in that case.
-
 ### Update the base image
 
-We sometimes release the security update for
-[the php-docker image][php-docker]. Then you’ll have to re-deploy your
+We sometimes release a security update for
+[the php-docker image][php-docker]. You have to re-deploy your
 WordPress instance to get the security update.
 
 Enjoy your WordPress installation!
@@ -217,8 +209,11 @@ Enjoy your WordPress installation!
 [appengine-flexible]: https://cloud.google.com/appengine/docs/flexible/
 [sql-settings]: https://console.cloud.google.com/sql/instances
 [memcache-dashboard]: https://console.cloud.google.com/appengine/memcache
+[memcache-installation]: https://www.digitalocean.com/community/tutorials/how-to-install-and-use-memcache-on-ubuntu-12-04#install-memcache
+[mysql-client]: https://dev.mysql.com/doc/refman/5.7/en/mysql.html
 [composer]: https://getcomposer.org/
-[dev-console]: https://console.cloud.google.com/
+[cloud-console]: https://console.cloud.google.com/
+[cloud-storage-console]: https://www.console.cloud.google.com/storage
 [cloud-sql-api-enable]: https://console.cloud.google.com/flows/enableapi?apiid=sqladmin
 [app-engine-setting]: https://console.cloud.google.com/appengine/settings
 [gcloud-sdk]: https://cloud.google.com/sdk/

dlp/composer.json

@@ -2,12 +2,13 @@
     "name": "google/dlp-sample",
     "type": "project",
     "require": {
-        "google/cloud-dlp": "^0.1.0",
+        "google/cloud-dlp": "^0.1.2",
         "symfony/console": "^3.3"
     },
     "autoload": {
         "files": [
              "src/inspect_datastore.php",
+             "src/inspect_bigquery.php",
              "src/inspect_file.php",
              "src/inspect_string.php",
              "src/list_categories.php",