Download the PHP package wp-spaghetti/wp-boot without Composer

On this page you can find all versions of the php package wp-spaghetti/wp-boot. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of wp-spaghetti/wp-boot

Informations about the package wp-boot

PHP Version Packagist Downloads Packagist Stars GitHub Actions Workflow Status Coverage Status Known Vulnerabilities GitHub Issues

GitHub Release License

WP Boot

WP Boot is a lightweight Composer-based WordPress management system designed for scenarios where you need to manage an existing WordPress installation without restructuring its directory layout.

Requirements

Why WP Boot?

While robust solutions like Bedrock, WP Starter, and Wordplate offer excellent WordPress management through Composer, they typically require significant structural changes to the WordPress directory layout.

WP Boot was created for situations where:

How It Works

WP Boot uses rsync to synchronize WordPress core files from the Composer vendor directory to your public directory, keeping the standard WordPress structure intact.

It only modifies the wp-config.php file, adding a simple bootstrap block:

This approach allows you to:

Installation

Note: During composer create-project, WordPress core will be downloaded to vendor/wordpress/, but files will not be synced to your public/ directory until you set WP_BOOT_SYNC_ENABLED=true in your .env file.

This gives you time to:

  1. Review and configure your .env file
  2. Verify the target public/ directory exists and is correct
  3. Decide when to sync WordPress files

Once configured, run:

This will trigger the sync script and copy WordPress core files to ../../public/.

Then add the bootstrap block to your wp-config.php file (see "How It Works" section above).

Directory Structure

After installation, your project structure will look like this:

The post-cmd.sh script automatically syncs WordPress core files from private/wp-boot/vendor/wordpress/ to public/ after every composer install or composer update.

Optional: Installing Language Packs

WP Boot includes WP Translation Downloader, a Composer plugin that automatically downloads translations from the WordPress.org API for all installed WordPress packages (core, plugins, and themes).

1. Add your desired languages to composer.json:

In the extra.wp-translation-downloader.languages array, add the locale codes you need:

Then run composer update — translations will be automatically downloaded to public/wp-content/languages/.

2. Configure WordPress to use the language in .env:

For more information: https://github.com/inpsyde/wp-translation-downloader

Optional: Disallow Search Engine Indexing in Non-Production

WordPress 5.5+ includes native environment detection via WP_ENVIRONMENT_TYPE. Wp-boot automatically sets this based on your WP_ENV value in .env.

To prevent search engines from indexing staging/development sites, create this file:

public/wp-content/mu-plugins/disallow-indexing.php

This automatically sets "Discourage search engines" in Settings → Reading for non-production environments.

When NOT to Use WP Boot

For new projects or when you have full control over the infrastructure, consider these more robust alternatives:

References

Changelog

Please see CHANGELOG for a detailed list of changes for each release.

We follow Semantic Versioning and use Conventional Commits to automatically generate our changelog.

Release Process

All releases are automatically created when changes are pushed to the main branch, based on commit message conventions.

Contributing

For your contributions please use:

See CONTRIBUTING for detailed guidelines.

Sponsor

Buy Me A Coffee

License

(ɔ) Copyleft 2026 Frugan.
GNU GPLv3, see LICENSE file.

All versions of wp-boot with dependencies

PHP Build Version
Package Version
Requires php Version >=8.1
composer/installers Version ^2.2
inpsyde/wp-translation-downloader Version ^2.6
johnpbloch/wordpress Version 6.9.4
oscarotero/env Version ^2.1
vlucas/phpdotenv Version ^5.5
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package wp-spaghetti/wp-boot contains the following files

Loading the files please wait ...