Download the PHP package laratusk/supervise without Composer
On this page you can find all versions of the php package laratusk/supervise. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download laratusk/supervise
More information about laratusk/supervise
Files in laratusk/supervise
Package supervise
Short Description Manage Linux Supervisor configuration files using Laravel config
License MIT
Homepage https://github.com/laratusk/supervise
FAQ
Example:
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 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.
Informations about the package supervise
laratusk/supervise
Define your Supervisor workers in Laravel config and generate real .conf files with one command. Your process config lives in code, not on the server.
What is this package?
Supervisor is a process control system for Linux: it keeps long-running processes (queue workers, Horizon, Reverb, etc.) running and restarts them when they crash. You configure it by placing .conf files in a directory (e.g. /etc/supervisor/conf.d/).
laratusk/supervise is a Laravel package that:
- Lets you define those processes in
config/supervise.php(worker name + command + any Supervisor options). - Compiles that config into valid Supervisor
.conffiles. - Can symlink them into your system Supervisor directory and reload Supervisor.
So instead of editing .conf files on each server, you edit one PHP config, commit it, and run php artisan supervise:compile (optionally with --reload) on deploy. Your worker setup is version-controlled and identical everywhere.
Requirements
- PHP 8.2+
- Laravel 10, 11, 12, or 13
- Supervisor installed on the server (for running the processes)
Installation
Publish config and prepare directories (run once per project):
This creates .supervisor/conf.d/, storage/logs/supervisor/, adds .supervisor/ to .gitignore, and publishes config/supervise.php.
Quick start
-
Define workers in
config/supervise.phpunder theworkerskey. Each worker needs acommand(the exact command line to run). The array key is the worker name. -
Compile to generate
.conffiles: -
Link them into Supervisor’s config directory (once per server, or when you add workers):
- Reload Supervisor so it picks up changes. You can do this in one step with compile:
On deploy, many projects only need:
(assuming supervise:link was already run once on that server).
Configuration
Config file: config/supervise.php.
Top-level keys
| Key | Purpose |
|---|---|
conf_path |
System directory where Supervisor reads configs. supervise:link creates symlinks here. Default: /etc/supervisor/conf.d. |
output_path |
Local directory (relative to project root) where compiled .conf files are written. Default: .supervisor/conf.d. Not committed (gitignored). |
defaults |
Supervisor [program:x] options applied to every worker. Any worker can override these. |
workers |
Your process definitions (see below). |
groups |
Optional Supervisor [group:x] definitions: group name => list of worker names. |
Workers
Each entry in workers is one Supervisor program. The key is the program name; the value is an array of options.
Required:
command(string) — The command line to run. Examples:php artisan horizon,php artisan queue:work redis --queue=default,php artisan reverb:start, or any other command.
Optional:
log(bool) — Iftrue, setsstdout_logfiletostorage/logs/supervisor/{worker_name}.log.- Any Supervisor program directive (e.g.
numprocs,user,directory,stopwaitsecs) to override the same key fromdefaults.
Example:
Defaults
The defaults array holds standard Supervisor [program:x] directives (numprocs, autostart, stopsignal, user, stdout_logfile, etc.). They are applied to every worker; workers can override any of them. See the published config/supervise.php for the full list and defaults. For the official directive reference, see Supervisor documentation.
Groups
To define a Supervisor group (so you can control several programs together):
This generates a [group:app-workers] section with programs=horizon,default-queue. Worker names must exist under workers.
Commands
| Command | Description |
|---|---|
php artisan supervise:install |
One-time setup: creates dirs, publishes config, updates .gitignore. |
php artisan supervise:compile |
Generates .conf files from config/supervise.php into output_path. Overwrites existing files. |
php artisan supervise:compile --reload |
Same as above, then runs supervisorctl reread and supervisorctl update. |
php artisan supervise:link |
Creates symlinks from each compiled .conf in output_path to conf_path. Run once per server (or when adding workers). |
Deployment
Typical deploy step:
This regenerates config from your codebase and tells Supervisor to reload. No manual .conf editing on the server.
Testing
License
MIT. See LICENSE.md.
All versions of supervise with dependencies
illuminate/console Version ^10.0|^11.0|^12.0|^13.0
illuminate/support Version ^10.0|^11.0|^12.0|^13.0
spatie/laravel-package-tools Version ^1.16