Workshop Playground Unsaved runtime in browser memory
/

Site Manager

File browser and live preview

/wordpress/wp-config.php
1 <?php define( 'CONCATENATE_SCRIPTS', false );
2 /**
3  * Base configuration for WordPress Playground.
4  * Database values are generated for the browser runtime.
5  */
6 define( 'DB_NAME', 'database_name_here' );
7 define( 'DB_USER', 'username_here' );
8 define( 'DB_PASSWORD', 'password_here' );
9 define( 'DB_HOST', 'localhost' );
10 define( 'DB_CHARSET', 'utf8mb4' );
11 define( 'DB_COLLATE', '' );
12 $table_prefix = 'wp_';
13 require_once ABSPATH . 'wp-settings.php';
1 {
2   "$schema": "https://playground.wordpress.net/blueprint-schema.json",
3   "meta": {
4     "title": "Playground Welcome Page",
5     "description": "Landing page for WordPress Playground",
6     "categories": [ "meta" ]
7   },
8   "login": true,
9   "landingPage": "/hello-from-playground/",
10  "preferredVersions": { "php": "8.3", "wp": "latest" },
11  "steps": [
12    { "step": "runPHPWithOptions", "options": { "code": "<?php" } }
13  ]
14 }
Database management is an early access feature WordPress Playground emulates MySQL using SQLite. Tools are still improving.
Database driverMySQL emulation backed by SQLite
SQLite database path/wordpress/wp-content/database/.ht.sqlite
Size452 KB
TableRowsUpdated
wp_posts11after launch
wp_options187after launch
wp_users1install
[10:42:06] Playground boot completed.
[10:42:09] WordPress latest mounted at /wordpress.
[10:42:13] No problems so far. Runtime notices and errors appear here.
Unsaved Playground consequence: Apply Settings & Reset destroys the temporary site. Saved Playgrounds use Save & Reload after configuration changes.