Download the PHP package cloak-labs/cloakwp-bedrock without Composer

On this page you can find all versions of the php package cloak-labs/cloakwp-bedrock. 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?

Informations about the package cloakwp-bedrock

CloakWP Bedrock - Headless WordPress Boilerplate

This is the official WordPress boilerplate for CloakWP (headless WordPress) projects. It's an opinionated, modern approach to WordPress development. However, it isn't a required piece of the CloakWP stack -- you can opt-out and use your own preferred WordPress development stack while still leveraging the other CloakWP tools.

This opinionated starter leverages many modern WordPress development tools:

Requirements

Installation

cd into your desired installation directory and run:

Then run:

and:

... which installs Spinup Local WP.

Optionally run the following to update your plugins/themes to their latest versions:

Configuration

Env Variables The Composer install command above will automatically copy the `.env.example` file to a `.env` file that you can now edit. - Ensure you modify the `APP_NAME` variable for each project, to ensure you don't end up with clashing Docker Containers. - You may need to modify `VOLUME_WORDPRESS_PATH` if the "run" commands detailed further below don't work. This variable must point to your WordPress installation folder relative to wherever the `spinup-local-wp` node package root is installed; it should work out-of-the-box with NPM, but not with PNPM which installs packages in a different location. - Optionally adjust the `DB_NAME`, `DB_USER`, and `DB_PASSWORD` variables to be more secure and to match your production environment. - Modify `.env.local` to override any production variables from `.env` for local development purposes. It is configured by default to cover the required overrides, such as overriding your decoupled front-end's production URL with `http://localhost:5000` via the `MY_FRONTEND_URL` variable. Note: `.env` is gitignored by default, and you likely want to keep it that way to keep your production values secure/secret. So, remember to manually add your `.env` file to your production server environment, or build your own solution for automating that (this will likely be the topic of a guide in the future).
ACF Pro It is highly recommended to purchase an Advanced Custom Fields (ACF) Pro license [here](https://www.advancedcustomfields.com/pro/#pricing-table). ACF Pro enables content-modelling features that most headless sites will require, such as ACF blocks, repeater fields, options pages, the gallery field, and more. Installing ACF Pro via Composer requires a couple extra steps, because they need to validate your license: 1. Follow [this article](https://www.advancedcustomfields.com/resources/installing-acf-pro-with-composer/) to create an `auth.json` file containing your license key within the CloakWP Bedrock root (i.e. alongside `composer.json`) 2. Open the Docker Desktop app 3. Run the following command from the CloakWP Bedrock root:
JWT Authentication We use the [JWT Authentication for WP-API](https://wordpress.org/plugins/jwt-authentication-for-wp-rest-api/) plugin to use JSON Web Tokens (JWTs) for authentication of protected API routes, such as when requesting Post Revisions from your decoupled frontend while in preview mode. CloakWP Bedrock has pre-configured everything for you, you just need to create your token: 1. Run the project (see below), 2. Make a POST request to the following endpoint, replacing WP_USERNAME + WP_PASSWORD with your own WordPress login credentials (unsure how? try the [Insomnia desktop app](https://insomnia.rest/), which is useful for testing/saving REST API requests throughout the whole lifecycle of headless projects). 3. Copy the `token` value returned by the POST request, and create an environment variable in your decoupled frontend's `.env.local` file to store it (you'll pass this ENV variable into `createWPInstance()` within `cloakwp.config.js` on your frontend).

Run

Make sure you open the Docker Desktop app before running the dev command below:

This runs docker-compose up, and Docker Compose will now start all the services:

🚀 Open http://localhost/wp in your browser to start working with WordPress! Your data will persist across sessions.

PhpMyAdmin

PhpMyAdmin comes installed as a service in docker-compose.

🚀 Open http://127.0.0.1:8082/ in your browser to log in to and manage your local database.

MailHog

MailHog comes installed as a service in docker-compose.

🚀 Open http://0.0.0.0:8025/ in your browser

CLI Tools

Read more about the CLI tools made available to you via the Spinup Local WP package, such as using the WP-CLI, Composer to add/remove/update plugins & themes, or running Docker commands.

All versions of cloakwp-bedrock 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 cloak-labs/cloakwp-bedrock contains the following files

Loading the files please wait ....