Download the PHP package own3d/bunny-cli without Composer

On this page you can find all versions of the php package own3d/bunny-cli. 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 own3d/bunny-cli

Informations about the package bunny-cli

Bunny CLI - Replicate and store your files to the edge!

Please use Bunny CLI for development purposes only. We have not yet released a stable release.

What is Bunny CLI?

Bunny CLI is a tool for the console to upload frontend frameworks such as Angular, Vue.js, React, or more recently, Blazor quickly to the Edge Store on Bunny CDN.

With Bunny CDN's Storage Edge, your web applications benefit from replicated storage zones, a global content delivery network that hosts files in 5 different regions worldwide and accelerates everything through a worldwide content delivery network with over 54+ PoPs.

How do I use Bunny CLI?

To install Bunny CLI, you need to be using Composer. For more details about Composer, see the Composer documentation.

If you want to update the Bunny CLI, just execute the following command:

After you install Bunny CLI, the next step is typically run the bunny init command to perform initial setup tasks. You can also run bunny init at a later time to change your settings or create a new configuration.

Run Bunny Init

To initialize Bunny CLI:

  1. Run bunny init:

  2. Configure your API credentials.

In order for the Bunny CLI to work properly you need to store your Bunny CDN API token. You can find your API token in your Account Settings.

  1. Choose a current Storage Zone if prompted.

If you only have access to one storage zone, including the default pull zone, bunny init selects it for you.

When bunny init finishes, it saves the environment variables in your .env file.

You can view these environment variables at any other time using the bunny env:list command.

Deploy your first project

With the bunny deploy command, you can easily synchronize your dist folder with your edge storage.

IMPORTANT: All files in the edge storage that are not in your local dist directory will be deleted.

How do I integrate Bunny CLI into my GitHub Actions workflow?

We offer you a GitHub Action for Bunny CLI for free. You can easily upload your distributable files to your edge storage during your deployment process with this action. Just put your storage password (BUNNY_STORAGE_PASSWORD) and your API key (BUNNY_API_ACCESS_KEY) in the secrets of your GitHub repository and adjust your workflow as follows.

Environment Variables

You can customize your environment file at any time. The following commands are available for this purpose:

Command Description
env:list List all current environment variables.
env:set {key} {value} Set and save an environment variable in the .env file.
env:backup {file} Backup .env file into a given file.
env:restore {file} Restore .env file from a given file.

Secure your .well-known/bunny-cli.lock file

Bunny CLI generates a lock file, which is located at .well-known/bunny-cli.lock by default. This file locks the files of your project to a known state. To prevent this from being publicly accessible it is recommended to create a new edge rule in your pull zone. You can use the following example as a template:

Action: Block Request
Condition Matching: Match Any
Condition: If Request URL Match Any */.well-known/bunny-cli.lock

Now the file should no longer be accessible. It can take a few minutes until your Edge Rule is active.

Frequently Asked Questions

Q: Is this a zero-downtime deployment?

A: Depends. Only when the sync of the files is complete, the pull zone cache is cleared. Therefore if the CDN cache is not present because the cache has expired or miss, then an unanticipated event may occur.

We hope that together with Bunny CDN, we can solve this problem.

Q: Is this an official tool of Bunny CDN?

A: No. Bunny CLI is a community-driven tool and is not affiliated with Bunny CDN.

License

Bunny CLI is an open-source software licensed under the Apache 2.0 license.

All versions of bunny-cli with dependencies

PHP Build Version
Package Version
Requires php Version ^7.4|^8.0
ext-json 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 own3d/bunny-cli contains the following files

Loading the files please wait ....