WordPress Lite (Project)

WordPress has become more powerful, faster and more compact, introducing the WordPress Lite Project.

This project's goal is to build a version of WordPress that is both as efficient and as space-saving as is reasonably possible. This will be accomplished by combining several server projects into a single reliable application. A variety of server projects will be combined in order to attain this goal. This will be done so that the objective that has been established for the project may be accomplished.

Because WordPress Lite is plug-and-play, no database configuration or installation is required. This is because no installation needs are necessary. WordPress Lite is a much more efficient and space-saving version of WordPress. Here, WordPress Lite is available for free download. It is not essential to update the database or install additional software; it is sufficient to just add it.

Compatible with more recent PHP versions than version 7.2. Compatible with future releases and implementation-ready Due to the fact that adding public dependencies to a project adds just a little amount of new data, the file storage requirements for tracking many versions of your work are surprisingly low. This is the case since adding public dependents offers minimal more data.

---

Features

• "Plug and Play," no installation required.

• No Database or Database Configuration required.

• Optimized for Maximum Efficiency and Performance.

• 90% more small and more efficient than legacy WordPRess.

• Support for the WPackagist Repository and the Composer Repository.

• True version control with Git and GitHub.

• Compatible with PHP versions 7.2 and above.

• Deployment friendly with Environment Variables.

WordPress Lite uses the Roots.io's Bedrock framework employs composer dependencies to facilitate WordPress installation. This not only makes it simpler for our team to manage ".env" files, but also allows us to create a centralized and carefully controlled staging environment. Websites that deviate from normal file path patterns may be resistant to automated assaults and security issues. The reason for this is that file paths provide a security risk. Utilizing non-standard file paths might potentially improve security and protection. These additional delights are entirely optional.

Using public dependencies adds a negligible amount of files to a project; hence, the real file storage needs for monitoring several versions of your work are rather modest. Therefore, the real file storage needs for maintaining several versions of a work are minimal. This is because there are presently few loaded files in the project. It is possible to put the whole Bedrock directory under version control to guarantee that a large number of developers adhere to the same plugin and other standards. Consequently, it is now feasible. WordPress in its most basic form cannot do this alone.

---

A modern WordPress stack

Website    Documentation    Releases    Support

---

Overview

Bedrock is a modern WordPress stack that helps you get started with the best development tools and project structure.

Much of the philosophy behind Bedrock is inspired by the Twelve-Factor App methodology including the WordPress specific version.

---

Features

• Better folder structure
• Dependency management with Composer
• Easy WordPress configuration with environment specific files
• Environment variables with Dotenv
• Autoloader for mu-plugins (use regular plugins as mu-plugins)
• Enhanced security (separated web root and secure passwords with wp-password-bcrypt)

---

Requirements

• PHP >= 7.4
• Composer - Install

---

Installation

1. Create a new project:

   $ composer create-project roots/bedrock

   By default, this installs the dist version of all dependent packages. To install the source versions instead, update composer.json as follows:

    "preferred-install": {
      "roots/wordpress-no-content": "dist",
      "*": "source"
    },

2. Update environment variables in the .env file. Wrap values that may contain non-alphanumeric characters with quotes, or they may be incorrectly parsed.

• Database variables
  • DB_NAME - Database name
  • DB_USER - Database user
  • DB_PASSWORD - Database password
  • DB_HOST - Database host
  • Optionally, you can define DATABASE_URL for using a DSN instead of using the variables above (e.g. mysql://user:password@127.0.0.1:3306/db_name)
• WP_ENV - Set to environment (development, staging, production)
• WP_HOME - Full URL to WordPress home (https://example.com)
• WP_SITEURL - Full URL to WordPress including subdirectory (https://example.com/wp)
• AUTH_KEY, SECURE_AUTH_KEY, LOGGED_IN_KEY, NONCE_KEY, AUTH_SALT, SECURE_AUTH_SALT, LOGGED_IN_SALT, NONCE_SALT
  • Generate with wp-cli-dotenv-command
  • Generate with our WordPress salts generator

3. Add theme(s) in web/app/themes/ as you would for a normal WordPress site
4. Set the document root on your webserver to Bedrock's web folder: /path/to/site/web/
5. Access WordPress admin at https://example.com/wp/wp-admin/

---

Community

Keep track of development and community news.

• Join us on Discord by sponsoring us on GitHub
• Participate on the Roots Discourse
• Follow @rootswp on Twitter
• Read and subscribe to the Roots Blog
• Subscribe to the Roots Newsletter