The Blog
Laravel Artisan Migration Command: The migrate:install Command
The migrate:install command creates a migrations database table in Laravel. You can specify the database connection to use with the optional database parameter. By default, it uses the connection specified in the database.default configuration entry. An example is provided to illustrate the usage of the migrate:install command. After executing the command, a migrations table with a similar structure will be created.
Laravel Artisan Migration Command: The migrate:refresh Command
Learn how to reset and run all outstanding migrations using the migrate:refresh command in Laravel. This command is a convenient shortcut to calling two separate Artisan commands. You can customize the behavior of migrate:refresh using various options and flags, such as specifying the database connection, forcing migrations to run in a production environment, specifying the path to the migrations file, and more. Additionally, you can execute the db:seed command after the migrate:refresh command by using the --seed flag or supplying a value for the --seeder option.
Laravel Artisan Migration Command: The migrate:reset Command
Learn how to use the migrate:reset command in Laravel to roll back all the migrations in your application. Customize the behavior of the reset using options such as specifying the database connection, running in a production environment, or displaying SQL queries without actually performing any operations. Follow the provided examples to understand how to use the command with different options.
Laravel Artisan Migration Command: The migrate:rollback Command
Learn how to use the migrate:rollback command in Laravel to undo the last database migration. This command supports various options and flags, such as specifying a custom database connection, forcing migrations in a production environment, or previewing the SQL queries that would be executed. Check out the provided examples to see how to use these options effectively. The migrate:rollback command automatically reverts the migrations with the highest batch number, removing any migrations with the same highest batch number.
Laravel Artisan Migration Command: The migrate:status Command
Learn how to check the status of each migration using the migrate:status command in Laravel. This command displays a table with indicators for each migration, showing whether it has been executed or not. You can also customize the command with options to check migrations on different database connections and in different locations. For convenience, default values are provided for the database connection and migrations path options.
Laravel Artisan Queue Command: The queue:failed Command
The queue:failed command in Laravel allows you to easily list all failed queue jobs stored in the failed_jobs database table. When executed, the command displays a table with details including the job ID, queue connection, job class, and failure date. In case there are no failed jobs, the command outputs a message indicating it.
Laravel Artisan Queue Command: The queue:failed-table Command
The queue:failed-table command helps create a migration for the failed_jobs database table, which functions to track failed queue jobs. Running this command multiple times generates multiple migrations, so make sure to change the table name in additional migration files to prevent errors during the migrate command.
Laravel Artisan Queue Command: The queue:flush Command
The queue:flush command can be used to easily clear the log of failed queue jobs. By calling this command, all entries from the failed_jobs database table will be removed. This can be achieved using the flush method on the configured FailedJobProviderInterface instance, which is bound to the key queue.failed in the service container. An equivalent PHP method call would be app('queue.failed')->flush().
Laravel Artisan Queue Command: The queue:forget Command
The queue:forget command in Laravel allows you to remove a single failed queue job entry from the failed_jobs database table. You can pass the job ID as an argument to the command, and it will delete the corresponding entry. If successful, it will display "Failed job deleted successfully!" and if no job matches the given ID, it will show "No failed job matches the given ID.". Alternatively, you can use the forget method on the Illuminate\Queue\Failed\FailedJobProviderInterface instance to accomplish the same task programmatically.
Laravel Artisan Queue Command: The queue:listen Command
Learn how to use the queue:listen command in Laravel to process jobs from the job queue. Customize the command using options such as connection, queue, memory, timeout, sleep, and tries. By default, the queue:listen command will attempt to run a job indefinitely. You can also prioritize queues by specifying multiple queues in the --queue option. Examples of using the command with different options are provided.
Latest posts
Wrapping up Forte Phase 0 with the lexer and parser now in private alpha, and kicking off Phase 1 wi...
Read moreA Forte development update: the parser now supports backtracking, improvements to node metadata, ide...
Read moreWrapping up attribute parsing in Forte's HTML parser, from simple HTML attributes to complex, edge-c...
Read moreExploring how Forte's parser extensions can be used to handle complex Blade directives like nested s...
Read moreDigging into parsing Blade and HTML comments while building Forte's HTML parser for Laravel Blade.
Read moreThis week I’m tackling Forte's HTML parser - consolidating Blade, Flux, and Livewire components into...
Read more