In some cases our default database or settings aren’t good enough, you might need a specific plugin installed, or you might need to screenshot a specific page with your plugin shortcode on it, for those cases you’ll need a custom config file and sql .

Custom config file

For custom settings, create an eyepatch.yml in your theme or plugin folder using the sample below :
# The type of the repository
# If auto it will scan style.css or first level .php files
# for `Theme Name` or `Plugin Name`
# can have one of this values
# type: wordpress-plugin|wordpress-theme|vuejs-kit|auto
type: wordpress-theme

# A list of paths to use
# path:
# – “/home”
# – “/blog”
# – “/page1”
– path_one/
– path_two/

# A list of sizes to use
# size:
# – 1360
# – 480
– 1360
– 480

# The wait time before taking a shot.
wait: 1000

# The theme slug if is a theme
theme: theme-name

# A list of plugins to be installed
# first argument is the plugin slug and the second is the desired version
plugin-one-slug: “1.0.0”
plugin-two-slug: “1.0.0”

# Path to a js file to inject and use before taking screenshots.
extra_js: “

Custom SQL file

  1. Start building your demo website using your favourite plugins/theme.
  2. If you use media files and they are necessary for the environment, you will need to read *)
  3. Export the sql file of the database you have built. If you are using Local by Flywheel you can use adminer and export the database. Make sure you will unselect the wp_users and wp_usermeta tables.
  4. Add the sql file to your product folder and name it import.sql.

*) Loading uploads assets works only if you have the demo online. If you do have it, grab the wp-content/uploads url and save it into this option inside the wp_options table -> upload_url_legacy . if you have access to wp-cli you can do wp option set upload_url_legacy ""