Download the PHP package backdevs/dotenv-sniffer without Composer
On this page you can find all versions of the php package backdevs/dotenv-sniffer. 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:
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.
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 dotenv-sniffer
# Laravel Dotenv Sniffer
A code sniffer for environment variables **not** declared in `.env` files
[](https://github.com/backdevs/laravel-dotenv-sniffer/actions/workflows/test.yml)
[](https://github.com/backdevs/laravel-dotenv-sniffer/releases/latest)
While working on large projects we've noticed that `.env.example` files would often get outdated. \
This tool provides a fast and simple way of constantly checking your code against `.env` files either as a step in your CI/CD pipeline, a Git hook or whatever works best for your project.
Requirements
- PHP
^8.1 - Tokenizer extension
Usage
Docker (recommended)
Inside your app's root directory, run: `
Composer dependency
PHAR
Options and Arguments
Options
--no-fail- Don't fail if errors are found (exit code = 0)-w | --warn-with-default- Treat variables with default values in Laravel\'senv()calls as warnings-c | --fail-code- The exit code to use when failing (default: 1), useful in CI/CD pipelines
Arguments
env-file- The .env file to check against (e.g.:.env,.env.example,.env.dev)paths- One or more files and/or directories to check
Simple Example
The .env.example file:
The config.php file:
Output for vendor/bin/desniff -w .env.example config.php
All versions of dotenv-sniffer with dependencies
PHP Build Version
Package Version
Requires
php Version
^8.1
ext-tokenizer Version *
symfony/console Version ^6.0|^7.0
symfony/validator Version ^6.0|^7.0
vlucas/phpdotenv Version ^5.0
symfony/stopwatch Version ^6.0|^7.0
ext-tokenizer Version *
symfony/console Version ^6.0|^7.0
symfony/validator Version ^6.0|^7.0
vlucas/phpdotenv Version ^5.0
symfony/stopwatch Version ^6.0|^7.0
The package backdevs/dotenv-sniffer contains the following files
Loading the files please wait ....