Customizing the Dockerfile not working as expected

[EvanHerman]

Forgive me if I am doing this incorrectly, but I'm just trying to make a simple change to the Dockerfile to play around with customizing the WordPress playground instance. I commented out the line where Akismet is being removed, and rebuilt the project but I'm not seeing Akismet as an installed plugin in the instance.

I was following the docs here https://wordpress.github.io/wordpress-playground/architecture/host-your-own-playground#install-plugins

Steps I took:

• Commented out the following line in packages/playground/wordpress/build/Dockerfile.
  • RUN rm -rf wordpress/wp-content/plugins/akismet
• Run npm run build or nx build playground-client.
• Run npm run dev.
• Open http://localhost:5400/website-server/ in browser and check wp-admin/plugins.php for Akismet.

https://github.com/WordPress/wordpress-playground/blob/trunk/packages/playground/wordpress/build/Dockerfile#L46

Am I editing the wrong file? How can I get the changes to the Dockerfile working?

[EvanHerman]

Sorry, I see I need to rebuild the docker image, not jus run npm run build. Closing this.

[EvanHerman]

Re-opening this as I'm still not 100% sure.

Rebuilding the image does make the changes inside of my docker image, but I don't see any changes reflected on the local site at http://localhost:5400/website-server/ after restarting it.

Also, I don't see the Hello Dolly plugin code in any of the WordPress directories (wp-6.4, wp-6.3 etc.), and I do see the Akismet plugin. In WordPress playground Hello Dolly is present but Akismet is not. Why is that?

Any tips to get this working? I'm probably just doing something incorrectly.

[adamziel]

@EvanHerman to rebuild WordPress using that Dockerfile, you'll need to run nx bundle-wordpress:all playground-wordpress. I realize that's not documented very well, there's a lot to improve in the developer resources.

What's your goal here? If you want to use Playground with a custom WordPress build, you could setup a regular WordPress site (with the SQLite plugin), zip it up, host it somewhere where it would be served with the proper CORS headers, and then start Playground like https://playground.wordpress.net/?wp=https://mysite.com/wp.zip or https://playground.wordpress.net/?import-site=https://mysite.com/wp.zip. There are nuanced differences between these two options, but their behavior will get harmonized as the Blueprints library gets migrated to PHP..

[EvanHerman]

Hi @adamziel

I'm more or less looking at hosting my own playground instance, so that when a user visits the site there are pre-installed plugins and set a theme, to cut out the multiple installPlugin steps and the installTheme step, with the ultimate goal of decreasing setup time. It sounded like it may have been possible from the documentation, but maybe I misinterpreted?

[adamziel]

@EvanHerman that is absolutely possible!

At the same time, you can achieve what you want without hosting an entire Playground instance. You could run your Blueprint, export the resulting site using the "Download as .zip" feature, and then import that zip using one of the QueryAPI options I mentioned in my previous comment.