googlearchive/appengine-php-wordpress-starter-project

Starter project for running WordPress on Google Cloud Platform

This project is no longer actively developed or maintained.

For new work on this check out A helper command for running WordPress on Google Cloud Platform

WordPress on App Engine Starter Project

Note: This repo is essentially the "source" of the starter projects, allowing you to browse our code, suggest changes, etc. We provide already-built-and-zipped WordPress projects for Windows, Mac, and Linux at Quick Start WordPress for Google App Engine.

Prerequisites

1. Install the PHP SDK for Google App Engine
2. Install MySQL
3. Sign up for a Google Cloud Platform project, and set up a Cloud SQL instance, as described here, and a Cloud Storage bucket, as described here. You'll want to name your Cloud SQL instance "wordpress" to match the config files provided here. To keep costs down, we suggest signing up for a D0 instance with package billing.
4. Visit your project in the Google Cloud Console, going to the App Engine section's Application Settings area, and make a note of the Service Account Name for your application, which has an e-mail address (e.g. <PROJECT_ID>@appspot.gserviceaccount.com). Then, visit the Cloud Storage section of your project, select the checkbox next to the bucket you created in step 3, click Bucket Permissions, and add your Service Account Name as a User account that has Writer permission.

Cloning and setup

Step 1: Clone

Clone this git repo and its submodules by running the following commands:

git clone --recursive https://github.com/GoogleCloudPlatform/appengine-php-wordpress-starter-project.git
cd appengine-php-wordpress-starter-project/

You now have a copy of WordPress, the App Engine plugin for WordPress, Batcache, and Memcached Object Cache.

Step 2: Edit the config files

Edit wp-config.php and app.yaml, replacing your-project-id to match the Project ID (not the name) that was assigned to your Google Cloud Platform project.

Step 3: Move files into place:

Because of GitHub and licensing limitations, we can't put these files in the right places for you.

Run this script to move all the files into place:

move_files_after_editing.sh

This script:

1. Moves wp-config.php from root into wordpress/, replacing the file there.
2. Moves batcache/advanced-cache.php to wordpress/wp-content/
3. Moves batcache/batcache.php to wordpress/wp-content/plugins/
4. Moves wp-memcache/object-cache.php to wordpress/wp-content/
5. Moves the contents of appengine-wordpress-plugin/ to wordpress/wp-content/plugins/

Running WordPress locally

First, edit wp-config.php so that the local environment password for root is not literally the string "password" -- unless that's what you used when setting up MySQL locally.

Using MySQL's command line version, run databasesetup.sql to set up your local database. For a default installation (no root password) this would be:

mysql -u root < databasesetup.sql

But really, all it's doing is running this line -- the WordPress installation script will do the heavy lifting when it comes to setting up your database.

CREATE DATABASE IF NOT EXISTS wordpress_db;

To run WordPress locally on Windows and OS X, you can use the Launcher by going to File > Add Existing Project or you can run one of the commands below.

On Mac and Windows, the default is to use the PHP binaries bundled with the SDK:

$ APP_ENGINE_SDK_PATH/dev_appserver.py path_to_this_directory

On Linux, or to use your own PHP binaries, use:

$ APP_ENGINE_SDK_PATH/dev_appserver.py --php_executable_path=PHP_CGI_EXECUTABLE_PATH path_to_this_directory

Now, with App Engine running locally, visit http://localhost:8080/wp-admin/install.php in your browser and run the setup process, changing the port number from 8080 if you aren't using the default. Or, to install directly from the local root URL, define WP_SITEURL in your wp-config.php, e.g.:

define( 'WP_SITEURL', 'http://localhost:8080/');

You should be able to log in, and confirm that your app is ready to deploy.

Deploy!

If all looks good, you can upload your application using the Launcher or by using this command:

$ APP_ENGINE_SDK_PATH/appcfg.py update APPLICATION_DIRECTORY

Just like you had to do with the local database, you'll need to set up the Cloud SQL instance. The SDK includes a tool for doing just that:

google_sql.py <PROJECT_ID>:wordpress

This launches a browser window that authorizes the google_sql.py tool to connect to your Cloud SQL instance. After clicking Accept, you can return to the command prompt, which has entered into the SQL command tool and is now connected to your instance. Next to sql>, enter this command:

CREATE DATABASE IF NOT EXISTS wordpress_db;

You should see that it inserted 1 row of data creating the database. You can now type exit -- we're done here.

Now, just like you did when WordPress was running locally, you'll need to run the install script by visiting:

http://<PROJECT_ID>.appspot.com/wp-admin/install.php

Or, to install directly from the root URL, you can define WP_SITEURL in your wp-config.php, e.g.:

define( 'WP_SITEURL', 'http://<YOUR_PROJECT_ID>.appspot.com/');

Activating the plugins, configuring email, and hooking up WordPress to your Cloud Storage

The following steps should be performed on your hosted copy of WordPress on App Engine

Activating the plugins

Now, we just need to activate the plugins that were packaged with your app. Log into the WordPress administration section of your blog at http://<PROJECT_ID>.appspot.com/wp-admin, and visit the Plugins section. Click the links to activate Batcache Manager and Google App Engine for WordPress.

Configuring email and hooking WordPress up to your Cloud Storage

Now visit Settings > App Engine. Enable the App Engine mail service - this will use the App Engine Mail API to send notifications from WordPress. Optionally, enter a valid e-mail address that mail should be sent from (if you leave this blank, the plugin will determine a default address to use). The address of the account you used to the create the Cloud Console project should work.

Stay on this page, because in order to be able to embed images and other multimedia in your WordPress content, you need to enter the name of the Cloud Storage bucket you created when going through all the Prequisites earlier under Upload Settings.

Hit Save Changes to commit everything.

That's all! (PHEW)

Congratulations! You should now have a blog that loads rapidly, caches elegantly, sends email properly, and can support adding images and other media to blog posts! Most importantly, it will take advantage of Google's incredibly powerful infrastructure and scale gracefully to accomodate traffic that is hitting your blog.

Maintaining

You'll want to keep your local copy of the application handy because that's how you install other plugins and update the ones that are packaged with this project. Due to the tight security of the App Engine sandbox, you can't directly write to files in the application area -- they're static. That's also why we hooked your uploads up to Cloud Storage. So, to install plugins, you log into the admin area of your local WordPress instance, install or update any plugins you want there, and redeploy. Then go into the admin area for your hosted WordPress instance to activate the plugins.

appengine-php-wordpress-starter-project's Issues

Font awesome fonts fail to load properly for wordpress

I found that when using this wordpress starter project that font awesome fonts, which are used by a lot of themes, fail to load.

I was able to fix by adding the following to my app.yaml file:

• url: /(..(eot|svg|ttf|woff))$
  static_files: wordpress/\1
  upload: wordpress/..(eot|svg|ttf|woff)$
  application_readable: true

Css Js not loading

i have want to run wordpress on root so i have the below

• url: /(..(htm|html|css|js))$
  static_files: /\1
  upload: /..(htm|html|css|js)$
  application_readable: true
• url: /wp-content/(..(ico|jpg|jpeg|png|gif|woff|ttf|otf|eot|svg))$
  static_files: /wp-content/\1
  upload: /wp-content/..(ico|jpg|jpeg|png|gif|woff|ttf|otf|eot|svg)$
  application_readable: true
• url: /(..(ico|jpg|jpeg|png|gif|woff|ttf|otf|eot|svg))$
  static_files: /\1
  upload: /..(ico|jpg|jpeg|png|gif|woff|ttf|otf|eot|svg)$
  application_readable: true
• url: /wp-includes/images/media/(..(ico|jpg|jpeg|png|gif|woff|ttf|otf|eot|svg))$
  static_files: /wp-includes/images/media/\1
  upload: /wp-includes/images/media/..(ico|jpg|jpeg|png|gif|woff|ttf|otf|eot|svg)$

but css , js files are not loading

Setup instructions might need changing for local dev & object-cache

I'm using a local environment as defined by: https://codex.wordpress.org/Installing_WordPress_Locally_on_Your_Mac_With_MAMP

I moved over my local wordpress installation to be an appengine wordpress start project as per the GitHub instructions. If I include the object-cache.php file in my local wordpress wp-content directory, then that breaks the local wordpress site from loading (nothing loads).

Problems with the MySQL command line tool

I had this problem and solved it, so I just wanted to put it here for people to have a visibility on it.

I followed all the steps on deploying the app to App Engine but it would never work to create the wordpress_db database via the MySQL console.

I found out two problems:

1. the google_sql.py script uses a method that is not supported anymore, so you have to create the database yourself.

2. there can be mismatches between the MySQL versions you use. If you, like me, downloaded MySQL just for this project, you'll download the 5.6 version and usually the SQL instance you create on Google's Cloud is set to 5.5 by default. Besides that the command in the documentation didn't work, the console returned an error message saying the sintax was wrong. I'm not familiar with this language to pinpoint the mistake but what did work was to open the MySQL connection wizard and add the root password and Address of the Cloud SQL instance there. It connected fine and to run the

   CREATE DATABASE IF NOT EXISTS wordpress_db;

Command you can just open a script for querying and run it from there.

Besides this, it all ran fine =)

And a little warning: make sure you don't forget the initial password you add to wordpress while first accessing it, the installation you now have does not have the mail functionalities enabled and the root password does not give you access to the front-end ;)

How to get uploaded images to serve through Appengine's ImagesService

How to get uploaded images to serve through Appengine's ImagesService?
Currently images serve directly from cloudstorage, would be very useful to serve them via imagesService.

https://cloud.google.com/appengine/docs/php/googlestorage/images

Or maybe there is a plugin for this?

Thanks

update to WP 4.1

I was considering using this as a template but noticed it hasn't been updated in 7 months and is still at WP 3.9.1 😢 And the WP sources are included as zip files 😭 Is there a newer repo somewhere?

You might consider an approach like https://github.com/xyu/heroku-wp which uses PHP Composer to handle WP and plugin dependencies. Of course unlike Heroku, GAE doesn't allow custom install scripts, but at least you could dynamically install and lock the deps locally before deploying.

Cloud SQL Wordpress DB connection always on.

I have just managed to do this basic installation including the Batcache and the Gapp engine plugin.
I just saw that the total usage is 42 hours of the Cloud SQL instance.

My site has no posts and is fairly new.
There are no followers neither visitors.
I am wondering why the SQL is always on ?

Builds - Wordpress version & other inconsistencies

The Wordpress version included in the build for Windows is 4.0-alpha(?), also the Mac build is using the old 3.8.1.

Can we please get both builds updated with the latest stable release (3.9.1)?

There is also an inconsistency with the Windows build, the archive's contents being in a folder called "wp39 - Copy" instead of one with a more appropriate name.

It's also missing the readme file that's present in the Mac archive.

On a similar note of folders/directory structure, wouldn't it also be better if the contents of the App Engine plug-in are in their own folder instead of sitting in the root of wp-content/plugins ?

It looks much cleaner this way, especially once you start adding more plug-ins.

Write a Google Compute Engine startup script to make WP app engine deployment easier

I wrote GCE startup script (http://storage.googleapis.com/wordpress123/wa.sh) to make deployment easier based on this document. With this script, you can start VM on GCE like the following
gcutil addinstance wordpressintance --metadata=project_id:xxxx --metadata=sql_pwd:xxxx --metadata=startup-script-url:http://storage.googleapis.com/wordpress123/wa.sh

Once the startscript finishes executing, everything is ready. Do you think it is useful to be checked in?

GAE can't support more then a handful of plugins

Trying to move over are large WordPress website that uses about 25 plugins. It's a Buddypress based social website. When sending the static files over to GAE you receive this notice:
Max number of files and blobs is 10000

According to GAE:
https://cloud.google.com/appengine/docs/quotas?hl=en
Deployments
An application is limited to 10,000 uploaded files per version. Each file is limited to a maximum size of 32 megabytes. Additionally, if the total size of all files for all versions exceeds the initial free 1 gigabyte, then there will be a $ 0.026 per GB per month charge.

GAE will work for small WordPress website but WordPress websites that use more then handful of advance plugins reach that quota quite quickly. I've reached out to Google Billing and they are working on it but it's been weeks now and no word.

Image URL becomes secured link regardless of whether use Secure URL is checked

First off, this plugin is awesome. Now I'm able to upload media on my Wordpress site, just the way I wanted. Thanks guys! :)

But I've faced an odd issue on getting the full size image link for this site that I'm playing around with. I'm not sure if it's because of the theme that I'm using or what, but the full size image (not the thumbnails) doesn't appear and a popup tells me that

Image cannot be loaded. Make sure the path is correct and image exist.

Oddly, the href is pointed to a secured URL when I did not check the "Use secure URLs for serving media files" checkbox. Just to double check, the URL for the image that I've uploaded is on an unsecured URL. Is there anyway to identify what could have been the cause for this problem?

I don't have an SSL certificate for the website that I'm setting up. So an unsecured link would be perfect.

Some background on the themes and plugins that I'm using:
Theme: Storefront
Plugins:

1. Woocommerce
2. WP Editor (although this doesn't seem to work at all since I can't edit the style.css on the fly)
3. Batcache Manager
4. Google App Engine for Wordpress (duh, of course)

You may replicate the issue by visiting https://pandanpoetry-wp.appspot.com/shop/cookies/ and clicking on any of the images that you see.

Using wordpress in GAE free tier

As I understand MySql is unavailable in free tier, is it possible to substitute it with available database or use some external storage to use wordpress in free tier?

Can't really see if batcache is working...

Even if I change the debug=true instead of false in the batchche settings of the wp-config.php I never really see any batcache stats in the rendered page. In GAE I can see that memcache is working and there are some entries including batcache in them so I assume it's working. Anyone else see the batcache info displayed before the tag?

Ultimate CSV Importer

Hi,

I cannot make this plugin work when using the WordPress starter project & installation on Google App Engine.

Any ideas ?

App Engine Error

WP does not accept .zip file with theme

i am trying to add a new theme via upload of a 7MB .zip file, but page returns error saying that its size is bigger than what is allowed on php.ini
how to solve this?
thanks

Unable to view site after upgrading to Wordpress 4.2

After updating to wordpress 4.2 I can access the admin area but not view the site.

Unable to find the socket transport "ssl"

Warning: stream_socket_client(): unable to connect to ssl://wordpress-blog-1.appspot.com:443 (Unable to find the socket transport "ssl" - did you forget to enable it when you configured PHP?) in /base/data/home/apps/swordpress-blog-1/wp.371384475208587749/wordpress/wp-includes/class-http.php on line 787 Warning: Cannot modify header information - headers already sent by (output started at /base/data/home/apps/swordpress-blog-1/wp.371384475208587749/wordpress/wp-includes/class-http.php:787) in /base/data/home/apps/s~wordpress-blog-1/wp.371384475208587749/wordpress/wp-includes/pluggable.php on line 899

Update the WordPress Version (from 4.2 to 4.6.1)

Update the WordPress Version (from 4.2 to 4.6.1)

Kindly refer to the WordPress site below:

https://wordpress.org/download/

Backing up wordpress Installation in Another .git repo

I don't know if this could be an issue (but somewhat related).

I know that codes are automatically backed up using Google App Engine (GAE) Version instances. However, I'm trying to back it up anyway using remote .git repository, but I get fatal errors each time I use git add.

After adding the files in a new repository to prepare the backup, I get these errors:

fatal: Could not chdir to '../../../appengine-wordpress-plugin': No such file or directory
fatal: 'git status --porcelain' failed in submodule wordpress/wp-content/plugins

Which setting do I change?

Cloning - not all files clone - app engine 1.8.7 os x 10.9

Here's the output of terminal when cloning to Google Apps Engine:

Line 11 <= This looks wrong as there's 2572 app files stated in line 10

Starting update of app: cycopress, version: v1
12:52 PM Getting current resource limits.
12:52 PM Scanning files on local disk.
12:52 PM Scanned 500 files.
12:52 PM Scanned 1000 files.
12:52 PM Scanned 1500 files.
12:52 PM Scanned 2000 files.
12:52 PM Scanned 2500 files.
12:52 PM Cloning 1280 static files.
12:52 PM Cloning 2572 application files.
12:52 PM Cloned 2000 files.   <======== This looks wrong as there's 2572 app files
12:52 PM Compilation starting.
12:52 PM Compilation completed.
12:52 PM Starting deployment.
12:52 PM Checking if deployment succeeded.
12:52 PM Deployment successful.
12:52 PM Checking if updated app version is serving.
12:52 PM Completed update of app: cycopress, version: v1
12:52 PM Uploading cron entries.

Uploading image from wordpress pages showing default type binary/octate-stream

While i upload image from wordpress pages it shows default type i.e binary/octate-stream. But when i upload using dashboard it shows correct type.

Zip Files not updated with new app.yaml

The ZIP files need to be updated with the latest app.yaml file. App Engine refuses to deploy with the old one.

port!=80 and networked/multi-user sites?

I'd love to run Wordpress MU (networked, multi site), but when I try and enable it, I get warned that it won't work (on my local copy) as I'm not running on port 80.
I can't seem to start AppEngineLauncher on port 80, even though there are no other port 80 listeners on my mac.
Any suggestions?

Repository directory structure for OSX

My project name is: ultrapressor
so I gcloud init ultrapressor
I now have this dir:
~/google-cloud-sdk/ultrapressor

Inside is already a default dir

Should the contents of your repository go inside default with the .git folder like so:
~/google-cloud-sdk/ultrapressor/default/
.git
app.yaml
cron.yaml
php.ini
wordpress

I'm not clear of the correct directory structure that should happen here so

1. I can deploy to production
2. Have a clean https://source.developers.google.com/p/ultrapressor/ folder
   I bring this up as my last repo from 8 months showed in the console but would not init or pull

Thanks all...

uploaded Media files in WordPress don't work at the next local developoment environment

The media file was saved localhost:8080/_ah/gcs/app_default_bucket/filename
It worked during the development time.
But when I continuously developed next day, the file in the Media library has been missing.

Avada Google App Engine - PLUGIN Installation issue

Using the local installation; I've installed the Avada theme without issue but then it prompts for required plugins

---

This theme requires the following plugin installed or update: Fusion Core.
This theme recommends the following plugin installed or updated: Revolution Slider.
Begin installing plugins | Dismiss this notice

---

Clicking Begin installing plugins directs to this page and it throws an error

http://localhost:8080/wp-admin/themes.php?page=install-required-plugins

You do not have sufficient permissions to access this page.

I have tried all the usual checks and even re-installed a fresh copy of WordPress 3.9.1 from your ZIP file and a blank database and then installed the theme again. It even happens when doing this so something is very odd about the theme installation and the Google App Engine.

The theme authors believe the issue is one of the hosting environment and security, e.g something strange about the WAMP type setup etc...

Thoughts anyone ?

Deprecate this repository

I'm planning to deprecate this repository, in favor of the new script for setting up WordPress project both for App Engine standard and flexible environments (and in the future, for kubernetes).

The new script is better because 1) It always fetches the newest WordPress. 2) It can download arbitrary version of WordPress (older version, localized version, etc) 3) The script asks few questions and config files are ready to deploy 4) It also installs a tool named wp-cli for maintenance work 5) It supports both App Engine standard and flexible

@johndmulhausen Let me know if you have any concerns.

Enabled SSL won't let use custom Domain

I have installed the Wordpress starter project and it runs fine under my domain under appspot.com

But I have setup google custom domain for my app and the Wordpress starter project won't run there because it requires ssl. I have tried to disable SSL with
define(‘FORCE_SSL_ADMIN’, false);
but still no luck.

Thanks for the help

obselete

Activating CURL

Hi,
I'm looking to activate CURL can you help me with that please
Thanks

When updating to wp 4.0 media upload trows http error

I was trying to update this project since all plugins and wp itself have new versions.

I simply changed the wp folder to the new version with batcache and GAE plugin in its folders.

After that I changes the wp-config.php to match the DB config settings for CloudSQL and project ID to wp-config.php and app.yaml

Everything works fine in wp-admin, except that the media file is uploaded to the bucket, but instead of showing the files in the media list, at the end of the upload the wp-admin says that was an http error.

Does someone knows what it may be? one time debug sayd that the app had a problem with batcache, but I'v just followed all the configs in batcache installation. Is there a special config for batcache in this GAE-wp project?

Media files not application_readable causing PHP Warnings

/wp-includes/images/media/ needs to be application_readable for use by wp_mime_type_icon() in wp-includes/post.php (at least in WordPress 3.9)
Otherwise you will get PHP warnings like:

PHP Warning:  array_keys() expects parameter 1 to be array, null given in /base/data/home/apps/.../.../src/wp-includes/post.php on line 5014
PHP Warning:  asort() expects parameter 1 to be array, null given in /base/data/home/apps/.../.../src/wp-includes/post.php on line 2347
PHP Warning:  Invalid argument supplied for foreach() in /base/data/home/apps/.../.../src/wp-includes/post.php on line 2348

wp_mime_type_icon() scans for jpg, png and gif, so we only need to upload those

Therefore I needed to make the following addition to app.yaml (right after the first two URL handlers with application_readable set to true).

- url: /wp-includes/images/media/(.*\.(jpg|png|gif))$
  static_files: wordpress/wp-includes/images/media/\1
  upload: wordpress/wp-includes/images/media/.*\.(jpg|png|gif)$
  application_readable: true

Could not create directory for the new theme installation

I've done putting define('FS_METHOD', 'direct'); and define('WP_SITEURL', 'http://localhost:8080/');
to both wp-config.php of the root directory of the project and one inside of the wordpress directory.
Also did chmod -R 755 wordpress/wp-content but no luck.. I'm trying it with the local drive on my mac.

Google Apps domain authentication for wordpress projects not working

I want to lock down a wordpress project on GAE to be accessible only to domain users. I set up my app.yaml so all routes are login: required or login: admin , and in the appengine.google.com console, set it to use the "Google Apps domain" authentication type.

At first, it worked. However, now even if you are signed in to the domain, it behaves as if you are not authorized (returns error 500). I suspect that the difference is the instance was already warmed up the first time, whereas the second time, it was not.

Any way around this / has anyone experienced this problem and found a solution?

Distorted view on localhost. pls help

Page Builder Plugin Failures

My wordpress installation went well and deployed locally and to the cloud without issue. However, whenever I attempt to install a page builder plugin, on activation it either 1) fails to load properly or 2) it crashes the site (localhost and appspot) and shows a Fatal error that has some version of : Class 'xxx' not found. I have tried various page builder plugins such as:
Siteorigin page builder (wont load), live composer (crashes with fatal error), elementor (wont load), beaver builder (crashes with fatal error) ...etc.

The error from live composer is the following: Fatal error: Class 'DSLC_Html' not found in C:\xxxxx\wordpress\wp-content\plugins\live-composer-page-builder\includes\functions.php on line 141

Some help would be appreciated.

Thanks!

obselete

Font mimetypes not supported/detected on GAE

Please add font mimetype detection on app.yaml

- url: /wp-content/(..ttf)$
static_files: wordpress/wp-content/\1
upload: wordpress/wp-content/..ttf$
mime_type: application/x-font-ttf

- url: /wp-content/(..otf)$
static_files: wordpress/wp-content/\1
upload: wordpress/wp-content/..otf$
mime_type: application/x-font-otf

- url: /wp-content/(..woff)$
static_files: wordpress/wp-content/\1
upload: wordpress/wp-content/..woff$
mime_type: application/x-font-woff

Update the docs to point users towards the Cloud SDK

We want to instruct users to use gcloud app for deploying PHP applications!

typo

In https://googlecloudplatform.github.io/appengine-php-wordpress-starter-project/

... "and enter the MySQL shell after the fist command:" ...

I believe you meant "first" rather than "fist"

No "Publish" Button when adding/editing post or page

I'm testing my project locally however I'm unable to save or publish my new post or page because there is no "Save Draft" or "Publish" button. Please see the image below

I believe it should be on the right side/column on the screen.

Is there something I missed or need to do to fix this?

css not load in wp-admin

In wp-admin ( in backend ) the css not load because there is a function that get content through 'realpath', that in app engine is not supported, so js and css not load correctly.
I try to fix by adding a little block of code.

Question on Instances

@tmatsuo

If I have one instance created and want to create multiple wordpress sites, do I have to create each instance for each project?

Can I run more than one database on a single instance?

What is the benefit and disadvantage of either?

Deploying and Using Cloud SQL

I'm trying to install Wordpress using this Mac version. I was able to deploy it locally using the following settings:

    define('DB_NAME', 'db_name');
    /** Local environment MySQL login info */
    define('DB_HOST', 'localhost');
    define('DB_USER', 'root');
    define('DB_PASSWORD', 'whatever');

However, when I tried to deploy it using Cloud SQL, I can't seem to figure out the correct settings.

In the DB_HOST, I have tried the following:

• ":/cloudsql/project-id:custom-db-instance"
• :/cloudsql/project-id:region:custom-db-instance"
• ":/cloudsql/project-id:wordpress"
• :/cloudsql/project-id:region:wordpress"
• IP address of Cloud SQL
• Setting app.yaml env_variables to the following:
  • MYSQL_DSN: mysql:unix_socket=/cloudsql/INSTANCE_CONNECTION_NAME;dbname=DATABASE
  • MYSQL_USER: root
  • MYSQL_PASSWORD: ''

I'm wondering what is the real setting because the documentation does not seem unified. Here are the documentation I read:

• https://cloud.google.com/appengine/docs/php/cloud-sql/
• https://googlecloudplatform.github.io/appengine-php-wordpress-starter-project/
• https://github.com/GoogleCloudPlatform/appengine-php-wordpress-starter-project

Local updates and plugin installs - "Missing zlib extensions" - OS X 10.9

All is well running locally except for any update or install functions as seen below

This message below is displayed upon attempting a local install via the wordpress admin

   Downloading install package from https://downloads.wordpress.org/plugin/wp-editor.1.2.2.zip…
   Unpacking the package…
   Abort class-pclzip.php : Missing zlib extensions

Please note

1. I have deployed here: https://cycopress.appspot.com/
   here are the freshly installed pindom stats: http://tools.pingdom.com/fpt/#!/t0XoQ/https://cycopress.appspot.com/
2. I used your prescribed method for installing mysql
3. I typically use homebrew for local installations for items such as zlib - homebrew confirms zlib is installed, however I realize this particular instance is probably only effective for the homebrew "cellar" environment.
4. When answering this please assume I am not an expert but decent at following instruction.

• I'm guessing maybe I need to install zlib so GoogleAppEngineLauncher.app can use it too?? If so what is best practice for this?

I greatly appreciate any guidance : )

cant start wordpress locally

i am getting this error:

2016-06-14 22:54:23 Running command: "['C:\Python34\pythonw.exe', 'C:\Program Files\Google\google_appengine\dev_appserver.py', '--skip_sdk_update_check=yes', '--port=8080', '--admin_port=8000', 'C:\Users\Colin Schwebke\Documents\Websites\vahle-taxi']"
Traceback (most recent call last):
File "C:\Program Files\Google\google_appengine\dev_appserver.py", line 84, in
_run_file(file, globals())
File "C:\Program Files\Google\google_appengine\dev_appserver.py", line 80, in _run_file
execfile(PATHS.script_file(script_name), globals)
NameError: name 'execfile' is not defined
2016-06-14 22:54:24 (Process exited with code 1)

Please tell me what i am doing wrong.

Regards
Colin

How to Update Wordpress to last version ?

Hi, Do you have any idea about this ?

google_sql.py <your-projectid>:wordpress

Hello- i had a Problem running that command on SDK, because all files needed for that were installed a folder before, in googleapp_engine. So i reinstalled SDK in that folder were the files were in and i only managed to install it, when i run SDK as Administrator- just want to mention it because it took me some time figuring it out XD-
I hope it helps the next one.
Thanks for that great Tutorial, i tried that before with the google tutorials, but didnt succed.
Best Regards

How to Migrate Existing Wordpress Site to Google App Engine

Hi, i have successfull launch my wordpress on GAE, However, if i want to migrate my existing wordpress site. Do you have any idea ? thanks

OSX Python 2.6 Stops AppEngine Launcher but system reports 2.7.6 installed

rocketadmin at rocket in ~ $ python --version Python 2.7.6

FROM CONSOLE
*** Running dev_appserver with the following flags:
--skip_sdk_update_check=yes --port=8080 --admin_port=8000
Python command: /usr/bin/python2.7
Error: Python 2.6 is not supported. Please use version 2.7.

But FROM TERMINAL
which python
/Library/Frameworks/Python.framework/Versions/2.7/bin/python

If I cat ~/.bash_profile
PATH="/Library/Frameworks/Python.framework/Versions/2.7/bin:${PATH}"

I have sourced my profile, restarted - I'm stuck at this point
What steps do I take remedy this?