Download the PHP package aaemnnosttv/wp-cli-dotenv-command without Composer

On this page you can find all versions of the php package aaemnnosttv/wp-cli-dotenv-command. 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 wp-cli-dotenv-command

WP-CLI Dotenv Command

Travis Build Packagist

All dotenv commands accept a --file=<path> parameter to specify the location of the environment file.
Defaults to .env.
If used, this parameter can be an absolute or relative path to the environment file, but which must include the file name (it does not have to be .env).

init

Initializes a new environment file.

By default, this command will only create the environment file if it does not already exist, but it can do much more.

--template=<file>

You may optionally initialize the environment file using another file as a template (eg: .env.example, a common convention). Run wp dotenv init --template=.env.example to use that file as the basis for the new environment file.

By default, the new file will be a copy of the template, but you may also set new values on the fly interactively! Passing the --interactive flag with the same command will prompt for each defined variable in the template. You may specify a new value to use, or simply leave it blank to keep the template-defined value. Any other lines/comments from the template are preserved.

--with-salts

Initialize the new environment file with fresh salts provided by the wordpress.org salt generator service. Any existing keys by the same name will not be overwritten. See salts.

--force

Overwrites an existing environment file, if it exists.

list [<pattern>...]

Prints out all of the key/value pairs as defined in the environment file.

You may also optionally limit the output to specific keys, or even keys that match simple patterns using glob pattern syntax. Eg: wp dotenv list DB_* *AWS* would produce a list with the following hypotheical keys:

The list command supports all of the same options for --format=<out> you've known to grow and love (table,json,csv,..etc). Default: table.

get <key>

Get the value of a defined key from the environment file.

set <key> <value>

Set the value of a key in the environment file.

By default the value that is set is not quoted in the file. If you need your value to be quoted a certain way, you may optionally pass a flag for the preferred style of quote you want: --quote-single or --quote-double.

delete <key>...

Remove one or more definitions for the given keys from the environment file.

salts

generate

Adds variable definitions to the environment file with fresh salts provided by the wordpress.org salt generator service.

By default, any existing keys by the same name will not be overwritten. However, if all of the defined salts in the environment file have the same value, then it is assumed that they are placeholders and will be updated. It is also possible to force regenerate them using --force, or simply use the regenerate command (see below).

regenerate

Same as generate, but will update all keys for salts with new values.

Installation

Recommended

As of WP-CLI v0.23, you may install the dotenv command using the new package command:

For installation with prior versions of WP-CLI, see the wiki.

That's it! Now you should see the dotenv command as an option when you run wp from any directory.

All versions of wp-cli-dotenv-command with dependencies

PHP Build Version
Package Version
Requires php Version ^5.6 || ^7.0 || ^8.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 aaemnnosttv/wp-cli-dotenv-command contains the following files

Loading the files please wait ....