Download the PHP package rbfraphael/wp-composer without Composer

On this page you can find all versions of the php package rbfraphael/wp-composer. 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 rbfraphael/wp-composer

Informations about the package wp-composer

Wordpress Boilerplate with Composer

Composer and Wordpress

Git-ready version of Composer-based Wordpress. Very useful for development, easy deployment and CI/CD configurations. With a compact, easy-to-understand and easy-to-maintain file structure.

0. Requirements

1. Installing

Just clone this repository and run inside this folder. After that, jump to next step.

2. Configure

The configuration process is simple. You only need to duplicate and rename to , then edit that file, inserting your site's database configuration, URL and salt keys (that you can generate at WordPress.org secret-key service or at my own Salt generator which outputs in .env format). After that, all configuration can be done from your web browser, accessing your site's URL and following normal Wordpress installation process.

Note (1): To access Wordpress admin panel, you need to access your site's URL followed by or (for example, http://mywebsite.com/cms/wp-admin or http://mywebsite.com/cms/wp-login.php).

Note (2): If you set environment variable to "auto", the will automatically be set based on requested domain (for example, will set to "https://mywebsite.com/").

3. Adding plugins

To add plugins, you need to edit the file, adding your required plugins into the "require" section, or run to require plugins through Composer. Also, you can install plugins in normal way, by adding them to or via Wordpress panel, but be advised that plugins added this way will be ignored by Composer and by Git (since you don't add them into ) and you'll not be able to update them with Composer. So, be careful.

Note: Custom plugins (plugins that aren't on Wordpress/WPackagist repository) can't be added to file or required by Composer, or it will cause errors while running Composer. To add custom plugins (or your own developed plugins), follow instructions on step 5.

4. Adding themes

Adding themes is done the same way you add plugins. Just edit file and add your themes into the "require" section, or run to require them with Composer. Also, this boilerplate comes with Twenty Twenty-Two theme, so you can follow this example to add your themes. As plugins, you can add new themes in normal way, extracting them to or installing via Wordpress panel. Themes added in normal way will not be updated or installed with Composer, but, unlike plugins, they will not be removed from your Git repository and will not cause problems when running Composer, because they aren't ignored in file (only the "Twenty something" themes are ignored).

Note: Custom themes (themes that aren't on Wordpress/WPackagist repository) can't be added to file, or it will cause errors while running Composer.

5. Adding or developing custom plugins

At some moment, you will need to add or create custom plugins. Since this boilerplate uses Composer to manage plugins that resides on Wordpress' repository, custom plugins will not work properly while using Composer. To add custom plugins, you'll need to add them to your file, and be sure the custom plugins aren't on your file.

6. Hosting and deploying

After deploying your Wordpress application, you need to point your webserver (Apache, NGINX, etc) root path to the directory of your application.

7. Versioning environments

Although not recommended, you can version development, testing and production environments. To do this, you just need to edit the corresponding file at , and all settings set on file will be overridden by settings on respective environment script.

8. Languages

To add a language to your Wordpress, you need to require the desired language from wp-languages.github.io repository. For example, to install Brazillian portuguese (codenamed "pt_br"), run in your project's root, or add to require section of your file.

All versions of wp-composer with dependencies

PHP Build Version
Package Version
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 rbfraphael/wp-composer contains the following files

Loading the files please wait ....