Download the PHP package shineunited/wordpress-installer without Composer

On this page you can find all versions of the php package shineunited/wordpress-installer. 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 shineunited/wordpress-installer

Informations about the package wordpress-installer

shineunited/wordpress-installer

License Latest Version PHP Version Main Status Release Status Develop Status

Description

A WordPress installer built with Conductor.

Installation

to add wordpress-installer, the recommended method is via composer.

Configuration

The wordpress installer uses the Conductor configuration framework to parse parameters in the 'extra' section of the project's composer.json file.

Parameters

Configurable Parameters

The following parameters can be defined in the 'extra' section of the composer.json file.

wordpress.webroot

(path) Path to the webroot directory. Defaults to 'web'.

wordpress.home-dir

(path) Path to wordpress home directory, used to define WP_HOME and WP_SITEURL. Must be within the webroot. Defaults to '{$wordpress.webroot}'.

wordpress.install-dir

(path) Path to the wordpress installation directory. Must be within the home-dir. Defaults to '{$wordpress.home-dir}/wp'.

wordpress.config-dir

(path) Path to the deployments configuration directory. Must be outside of the webroot. Defaults to 'cfg'.

wordpress.content-dir

(path) Path to wordpress content directory. Must be inside the home-dir but outside of the install-dir. Defaults to '{$wordpress.home-dir}/app'.

wordpress.config.convert-bool

(boolean) If true boolean environment configuration variables will automatically be converted. Defaults to true.

wordpress.config.convert-null

(boolean) If true null environment configuration variables will automatically be converted. Defaults to true.

wordpress.config.convert-int

(boolean) If true integer environment configuration variables will automatically be converted. Defaults to true.

wordpress.config.strip-quotes

(boolean) If true string environment configuration variables will automatically have quotes stripped from them if found. Defaults to true.

wordpress.config.source

(select) Must be one of 'env', 'server', or 'local'. Defines where environment configuration variables come from. Defaults to false (none).

wordpress.config.default-env

(select) Defines the default environment name, used if environment is not defined explicitly elsewhere. Must be 'production', 'staging', or 'development'. Defaults to 'production'.

Calculated Parameters

The following parameters are available for use but cannot be overridden in the project's composer.json file.

wordpress.wpconfig-dir

(path) Path to directory where the wp-config.php file will be created. Locked to the directory above the install-dir.

wordpress.muplugins-dir

(path) Path to the wordpress mu-plugins directory. Locked to '{$wordpress.content-dir}/mu-plugins'.

wordpress.plugins-dir

(path) Path to the wordpress plugins directory. Locked to '{$wordpress.content-dir}/plugins'.

wordpress.themes-dir

(path) Path to the wordpress themes directory. Locked to '{$wordpress.content-dir}/themes'.

wordpress.uploads-dir

(path) Path to the wordpress uploads directory. Locked to '{$wordpress.content-dir}/uploads'.

wordpress.upgrade-dir

(path) Path to the wordpress upgrade directory. Locked to '{$wordpress.content-dir}/upgrade'.

Example

Usage

ExtensionProvider Capability

Extensions to the WordPress configuration can be added via the ExtensionProvider capability by composer plugins.

Example Plugin

The plugin must implement Capable and provide the ExtensionProvider capability.

Example Provider

The provider must implement the capability, and return a list of ExtensionInterface objects.

All versions of wordpress-installer with dependencies

PHP Build Version
Package Version
Requires php Version >=8.0
composer-plugin-api Version ^2.0
shineunited/conductor Version ^1.0
shineunited/conductor-twig-addon Version ^1.0
oscarotero/env Version ^2.1
roots/bedrock-autoloader Version ^1.0
roots/wp-config Version ^1.0
symfony/filesystem Version ^6.0
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 shineunited/wordpress-installer contains the following files

Loading the files please wait ....