Hi, Thanks for this great package, i discovered the latest version 1.4.1 is incompatible with laravel Jetstream livewire stack, I used jetstream and this package, it works great with version 1.3, but after update all packages, i got error 'Livewire\Exceptions\ComponentNotFoundException' Unable to find component: [profile.update-profile-information-form], the same message for all Laravel Jetstream livewire components. It's took me 2 days to debug and finally found this issue related to this package and specially version 1.4.1, after came back to version 1.3 o this package my app works fine again.

return [

    /*
    |--------------------------------------------------------------------------
    | Middleware list for web routes
    |--------------------------------------------------------------------------
    |
    | You can pass any middleware for routes, by default it's just [web] group
    | of middleware.
    |
    */
    'middlewares' => [
        'web',
        'auth',
        'role:' . App\Enums\UserType::ADMIN,
    ],

    /*
    |--------------------------------------------------------------------------
    | Route prefix
    |--------------------------------------------------------------------------
    |
    | Prefix for gui routes. By default url is [/~artisan-gui].
    | For your wish you can set it for example 'my-'. So url will be [/my-artisan-gui].
    |
    | Why tilda? It's selected for prevent route names correlation.
    |
    */
    'prefix' => '~',

    /*
    |--------------------------------------------------------------------------
    | Home url
    |--------------------------------------------------------------------------
    |
    | Where to go when [home] button is pressed
    |
    */
    'home' => '/',

    /*
    |--------------------------------------------------------------------------
    | Only on local
    |--------------------------------------------------------------------------
    |
    | Flag that preventing showing commands if environment is on production
    |
    */
    'local' => false,

    /*
    |--------------------------------------------------------------------------
    | List of command permissions
    |--------------------------------------------------------------------------
    |
    | Specify permissions to every single command. Can be a string or array
    | of permissions
    |
    | Example:
    |   'make:controller' => 'create-controller',
    |   'make:event' => ['generate-files', 'create-event'],
    |
    */
    'permissions' => [
    ],

    /*
    |--------------------------------------------------------------------------
    | List of commands
    |--------------------------------------------------------------------------
    |
    | List of all default commands that has end of execution. Commands like
    | [serve] not supported in case of server side behavior of php.
    | Keys means group. You can shuffle commands as you wish and add your own.
    |
    */
    'commands' => [
        'laravel' => [
            'clear-compiled',
            'down',
            'up',
            'env',
            // 'help',
            'inspire',
            'list',
            'notifications:table',
            'package:discover',
            'schedule:run',
            // 'schema:dump',
            'session:table',
            // 'storage:link',
            // 'stub:publish',
            'auth:clear-resets',
            'tail',
        ],
        'optimize' => [
            'optimize',
            'optimize:clear',
        ],
        'cache' => [
            'cache:clear',
            'cache:forget',
            'cache:table',
            'config:clear',
            'config:cache',
        ],
        /*
        'database' => [
            'db:seed',
            'db:wipe',
        ],
        */
        'events' => [
            'event:cache',
            'event:clear',
            'event:generate',
            'event:list',
        ],
        /*
        'make' => [
            'make:cast',
            'make:channel',
            'make:command',
            'make:component',
            'make:controller',
            'make:event',
            'make:exception',
            'make:factory',
            'make:job',
            'make:listener',
            'make:mail',
            'make:middleware',
            'make:migration',
            'make:model',
            'make:notification',
            'make:observer',
            'make:policy',
            'make:provider',
            'make:request',
            'make:resource',
            'make:rule',
            'make:seeder',
            'make:test',
        ],
        */
        'migrate' => [
            // 'migrate',
            // 'migrate:fresh',
            // 'migrate:install',
            // 'migrate:refresh',
            // 'migrate:reset',
            // 'migrate:rollback',
            'migrate:status',
        ],
        /*
        'queue' => [
            'queue:batches-table',
            'queue:clear',
            'queue:failed',
            'queue:failed-table',
            'queue:flush',
            'queue:forget',
            'queue:restart',
            'queue:retry',
            'queue:retry-batch',
            'queue:table',
        ],
        */
        'route' => [
            'route:cache',
            'route:clear',
            'route:list',
        ],
        'view' => [
            'view:cache',
            'view:clear',
        ],
        'backup' => [
            'backup:clean',
            'backup:list',
            'backup:monitor',
            // 'backup:run',
        ],
        'responsecache' => [
            'responsecache:clear',
        ],
        'opcache' => [
            'opcache:clear',
            'opcache:compile',
            'opcache:config',
            'opcache:status',
        ],
        'schedule-monitor' => [
            'schedule-monitor:list',
        ],
    ],

];

Im using Plesk (panel website admin) extension to manage composer packages. It's gives me error with tag name 2.0.0@beta presumably by the @ . Could you change next tag version to a name without @ . I will try no notify Plesk plugin developer. Thanks.

This PR addresses the issue https://github.com/inFureal/artisan-gui/issues/26 and adds an optional flag to force HTTPS when passing the endpoint and home parameters as props

Hello,

I've been using artisan-gui for over a month now and I really like it. I wanted to try the beta and now I only get a blank page. I tried removing and reinstalling the current version but there's the same issue.

Kind regards,

Maybe it would be possible that if, when in production, it would only allow certain users to access the routes?

this would make it really useful for people on shared hosting with no access to SSH

Hi,

It could be very nice to be able to only display/run commands depending on Gate authorization.

For example, the commands list from config file could be something like:

'commands' => [
    'group-name' => [
        'foo:bar',    // Ok for everyone (who can access artisan gui)
        'can-run-baz' => 'baz'// Only for users with permission 'can-run-baz'
    ]
]

It requires to read the list before building the gui panel. Something like:

use Gate;

class GuiController extends Controller {
    use AuthorizesRequests, DispatchesJobs, ValidatesRequests;

    function index() {
        $commands = array_filter(config('artisan-gui.commands', []), function ($command, $permission) {
            return is_string($permission) ? Gate::allows($permission) : true;
        },  ARRAY_FILTER_USE_BOTH);
        return view('gui::index', [
            'commands' => array_values($commands)
        ]);
    }

This is raw code just to get the idea, a method should retrieve the filtered commands. Permission should also be checked before runningg the command.

This feature should not introduce any BC. I may provide a PR if you're ok with this.

This pull request adds an ability to add middleware from config itself. This ability opens a lot of abilities like adding some role/permission middleware to the route so it can be accessed only by user having certain permissions/role.

Laravel: 8.54 PHP: 7.4 artisan-gui 2.0.0@beta

Hi there,

Just installed this in my project:

• composer require infureal/artisan-gui:2.0.0@beta
• php artisan vendor:publish --tag="artisan-gui-config"
• set local to false
• enable auth middleware
• prefix => '~'

When visiting localhost:3000/~artisan of localhost:3000/~artisan-gui it just throws a 404. I checked my route list and it doesn't contain anything related to artisan-gui. Am I missing something?

Thanks in advance. Great project :)

Hello

I encounter an issue (beta v2) while trying command with interactive question (using $this->ask() or variant of it). Do you plan to support this in the next version?

This code will produce an error

exception: "Error"
file: "/home/vagrant/code/platform/vendor/symfony/console/Helper/QuestionHelper.php"
line: 113
message: "Undefined constant \"STDIN\""

Code example to reproduce the issue :

class MyTestCommand extends Command
{
	protected $signature = 'test';
	protected $description = 'Test command';

	public function handle()
	{

		$this->ask('hello ? ');

		return 0;
	}
}

Hi, I facing an error ("Undefined constant STDIN") when I use this type of command - https://laravel.com/docs/8.x/artisan#prompting-for-input. There is any way to use this command from web GUI?

Hey,

When you have a command without arguments or options, if you click on command, it should show the modal and force you to click on RUN, instead of running the command right away.

Right now if you click, shows only the "running icon"

It's danger without that. :D

Hello there. 👋 I have plans to rework this package, adding new features besides running commands. First, I ask @Catzilla, @saineshmamgain to contact me if you are free to work together.

ℹ️ This package is not abbandoned. As far as possible, I will fix bugs and improve functionality. But most of the time will be spent on a new package.

What are the plans for the new package:

• Handling STDIN/STDOUT with somthing like ChildProcess and ReactPHP itself
• Show more information about laravel app such as migration status etc.
• Reworking UI/UX.
  • If you have good examples of UI, you can attach them.
• Support for custom handlers and plugn support.
  • Need to thing about the architecture

Feel free to write your wishes in this issue.