Download the PHP package manyapp/duskapiconf without Composer

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

Informations about the package duskapiconf

Manyapp DuskApiConf

A Laravel module to perform live configuration changes from your Dusk tests

The issue

Currently, the only way to define the configuration of your Laravel app during Dusk tests is to set the relevant variables in a dedicated .env.dusk.local file. This file is copied and read during the application's boot, and therefore cannot be changed within Dusk tests.

This behaviour can be problematic, as a lot of developers need to change the configuration in specific tests to see if the application reacts accordingly.

As mentionned here, there is no easy way to tackle this problem.

The solution

This modules offers an easy possibility to change the configuration of your application during the runtime of your Dusk tests.

See how it works on our blog article.

Installation

Install the module with:

Then, you will have to modify your DustTestCase.php to add three methods. Alternatively, you can add the following methods to the Trait of your choice and use the Trait in your Dusk tests.

Usage

To use it, use the defined methods below directly in your Dusk tests.

Change location of the config temporary file

Type the following commands:

Modify the Storage disk and the name of the temporary file.

Contribute

For any bug or feature request, use Github.

For any other feedback, let us a comment on this blog article or contact us.

License

MIT.

All versions of duskapiconf with dependencies

PHP Build Version
Package Version
No informations.
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 manyapp/duskapiconf contains the following files

Loading the files please wait ....