Level 80
@wakanda Simple solution would be not to upload the file artisan to your server.
1 like
Apr 27, 2021
14
Level 10
Disable artisan commands
Hi Devs, is there a way to disable the artisan command. For example in the production environment, I never want to run PHP artisan migrate:fresh.
Level 10
@martinbean Thanks for your reply that would work but would still need access to commands for caching, crone, sitemap, and other custom commands
Level 27
// register in your ServiceProvider's boot()
\Event::listen(
\Illuminate\Console\Events\CommandStarting::class,
\Your\Namespace\PreCommand::class
);
namespace Your\Namespace;
use Illuminate\Console\Command;
use Illuminate\Console\Events\CommandStarting;
class PreCommand extends Command
{
/**
* Handle the event.
*
* @param object $event
* @return void
*/
public function handle(CommandStarting $event): void
{
if (app()->environment(['production'])) {
if ($event->command == 'migrate:fresh') {
$this->output = $event->output;
$this->info('Nope. Not running.');
die();
}
}
}
}
3 likes
Level 80
@wakanda You can’t have it both ways. You either want Artisan on the server or you don’t.
Level 10
@martinbean it turns out can be achieved check @laracoft solution and also found a similar solution here https://stackoverflow.com/questions/63588629/is-there-a-way-to-disable-artisan-commands
Level 27
2nd is a command file, just put it anywhere as long as namespace mtaches your folder.
2 likes
Level 122
Don't understand the problem. Artisan Migrate prompts when in production, and should cause no issue if your database has already been migrated.
Level 10
@snapey I know it prompts when in production, but my case is that in the production environment I never want to run php artisan migrate:fresh. So prompting does not mean it cannot run it completely. So just adding an extra protection layer in case of human error.
And to be explicit am worried about migrate:fresh rollback and refresh commands, so disabling them helps me better sleep at night.
Level 122
is why you have backups
1 like
Level 10
@snapey thanks, maybe i need to change my backups from weekly to daily
Level 80
And to be explicit am worried about migrate:fresh rollback and refresh commands, so disabling them helps me better sleep at night.
@wakanda Well who’s SSH-ing into your production server and running migrate:fresh?
Level 1
@martinbean I have a scenario that I'd like you to consider:
- I'm using a container orchestration platform to deploy my Laravel applications
- i'd like to leverage the same Laravel health APIs from my command line that I am for monitoring my server health such that the container orchestrator can do health/liveness probes during start-up
- I don't want artisan to be usable for other scenarios.
Would this be a valid reason to want to have artisan on my server without it being usable for other use cases?
https://github.com/spatie/laravel-health for reference
Please or to participate in this conversation.