Download the PHP package sajidifti/laravel-command-center without Composer

On this page you can find all versions of the php package sajidifti/laravel-command-center. 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 sajidifti/laravel-command-center

Informations about the package laravel-command-center

Laravel Laravel Command Center

Latest Version on Packagist Total Downloads

A database-independent Laravel Command Center for Laravel applications that works even when your database is down. Perfect for emergency maintenance, system management, and troubleshooting.

Features

Installation

Option 1: Install from Packagist (Production)

For production use, install the package from Packagist:

Then run the installation command:

The installer will guide you through an interactive setup process, asking you to:

For each environment variable, you'll be prompted with secure defaults:

Option 2: Install for Local Development

For local development or contributing to the package:

  1. Clone or add the package to your Laravel project:

  2. Add the local repository to your root composer.json:

  3. Install the package:

  4. Run the installation command:

Accessing the Command Center

After installation, the command will display your access URL. Navigate to the route prefix you configured (e.g., https://yourdomain.com/command-center/somesecret) and login with the credentials you set during installation.

Security Note: Your route prefix includes a random secret path for security. Keep this URL private and use HTTPS in production.

Available Commands

command-center:install

Interactive installation wizard that guides you through setting up the Laravel Command Center.

Interactive Mode (Default)

Simply run the command and answer the prompts:

You'll be asked:

  1. Publish configuration file? (yes/no) [yes]
  2. Publish compiled assets (CSS/JS)? (yes/no) [yes]
  3. Add environment variables to .env (and .env.example)? (yes/no) [yes]

If you choose to add environment variables, you'll be prompted for:

Flag-Based Mode

Skip interactive prompts by using flags to install only specific components:

Note: The --only-* flags are mutually exclusive. When you use one, only that specific component will be installed. To install multiple components, run the command multiple times or use interactive mode.

Full Installation Mode (Non-Interactive)

For automated deployments or CI/CD pipelines:

This will:

What Happens When You Skip Steps

If you answer "no" to any step, the installer will show you manual instructions:

Skipped Config:

Skipped Assets:

Skipped Environment Variables:

command-center:clean-sessions

Cleans up expired session files from the command center's file-based session storage.

What it does:

When to use:

Manual Publishing (Advanced)

You can also manually publish specific components using Laravel's vendor:publish command:

Configuration

The package is configured via config/command-center.php. After installation, you can customize various aspects of the Command Center.

Basic Configuration

Customizable Features

The configuration file includes several customizable sections:

System Information Items

Customize which system information is displayed on the dashboard:

Environment Settings Categories

Define which environment variables are editable through the UI:

Command Sections

Organize and customize available Artisan commands:

Allowed Commands

For security, only whitelisted commands can be executed:

Note: Any command you add to command_sections must also be added to allowed_commands for security validation.

Usage

Accessing the Command Center

  1. Navigate to your configured route prefix (e.g., https://yourdomain.com/command-center/somesecret)
  2. Login with credentials from .env
  3. Use the interface to manage your application

Features Available

System Information

Artisan Commands

Environment Management

Maintenance Mode

How It Works

Database Independence

The Laravel Command Center is completely independent of your application's database:

  1. File-Based Sessions: Uses its own session storage in storage/framework/management_sessions/
  2. No Web Middleware: Bypasses Laravel's database-dependent middleware
  3. Standalone Routes: Loads without web middleware group
  4. No Database Queries: Authentication uses .env, not database

Security Features

Requirements

Prebuilt Assets

This package ships with prebuilt Tailwind CSS v4 in the public directory, so consumers do not need Node.js or NPM to use the package in production.

Development / Rebuilding Assets

If you need to modify the frontend and rebuild the assets, the package includes a Vite + Tailwind v4 build setup. From the package root run:

The build writes compiled JS/CSS into the package public directory. After building, publish the package assets into your application with:

Notes:

Troubleshooting

Command Center Not Loading

  1. Check that route prefix is correct in .env
  2. Clear config cache: php artisan config:clear
  3. Verify storage permissions: storage/framework/management_sessions/ needs to be writable

Session Issues

Assets Not Loading

Cannot Access During Database Outage

This is the main feature! The command center should work even when:

If it's not working, check your view composers aren't querying the database.

Advanced Configuration

Custom Session Path

Custom Middleware

Register additional middleware in bootstrap/app.php:

Scheduled Session Cleanup

Add to your routes/console.php or scheduler:

Security Best Practices

  1. Change Default Route: Use a unique, hard-to-guess route prefix
  2. Strong Credentials: Use strong username and password
  3. HTTPS Only: Always use HTTPS in production

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

The MIT License (MIT). Please see License File for more information.

Credits

Support

For support, email [email protected] or open an issue on GitHub.

All versions of laravel-command-center with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
illuminate/support Version ^12.0
blade-ui-kit/blade-heroicons Version ^2.6
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 sajidifti/laravel-command-center contains the following files

Loading the files please wait ...