harlan-zw/laradock-cli

[Unmaintained] Your new best friend for Laradock.

Twitter ▪ @harlan_zw Personal Site ▪ harlanzw.com Consider sponsoring me if you like my work 💖

laradock-cli's Issues

really interesting project but some basic how-to-use are needed

I just started using Laradock and am finding it quite bloated and it's been a chore trying to figure out how to trim all the fat so I can end up with configurations that are lean and viable on production

I was looking for possibly existing examples of such configs and came across your project.

It certainly looks promising! But I don't understand how to use it!

Are we supposed to clone this repo inside of an existing Laravel project? Or inside of a Laravel project already containing Laradock at its root?

I tried to create a "global" installation of your "laradock" but that didn't really work as intended.

When I try to run php laradock init inside a cloned folder it just complains about not finding any env variables

I also notice that your included docker-compose.yml has some opinions, for example it installs apache2 and not nginx.. is this meant to be just an example? and using your cli one is able to modify docker-compose's listed services through a cli interface?

I really want to use this! Just need a bit of guidance on how it's intended to be used across multiple Laravel projects without requiring to pull in lots of code into each.

Thanks for working on this! I think it's very needed

can't install on fresh Laravel 5.8 project + more

Glad to see this moving along :) Of course I understand it's pre-release, don't mind if I fill out bug reports anyway

Right now I can't install this on a fresh Laravel 5.8

laravel new laradock-test
cd laradock-test
composer global require loonpwn/laradock-cli

Using version ^0.1.0 for loonpwn/laradock-cli
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for loonpwn/laradock-cli ^0.1.0 -> satisfiable by loonpwn/laradock-cli[0.1].
    - Conclusion: remove illuminate/container v5.7.20
    - Conclusion: don't install illuminate/container v5.7.20
    - loonpwn/laradock-cli 0.1 requires laravel-zero/framework ^5.8 -> satisfiable by laravel-zero/framework[v5.8.0, v5.8.1, v5.8.2, v5.8.3, v5.8.4, v5.8.5].
    - laravel-zero/framework v5.8.0 requires illuminate/container 5.8.* -> satisfiable by illuminate/container[v5.8.0, v5.8.11, v5.8.12, v5.8.2, v5.8.3, v5.8.4, v5.8.8, v5.8.9].
    - laravel-zero/framework v5.8.1 requires illuminate/container 5.8.* -> satisfiable by illuminate/container[v5.8.0, v5.8.11, v5.8.12, v5.8.2, v5.8.3, v5.8.4, v5.8.8, v5.8.9].
    - laravel-zero/framework v5.8.2 requires illuminate/container 5.8.* -> satisfiable by illuminate/container[v5.8.0, v5.8.11, v5.8.12, v5.8.2, v5.8.3, v5.8.4, v5.8.8, v5.8.9].
    - laravel-zero/framework v5.8.3 requires illuminate/container 5.8.* -> satisfiable by illuminate/container[v5.8.0, v5.8.11, v5.8.12, v5.8.2, v5.8.3, v5.8.4, v5.8.8, v5.8.9].
    - laravel-zero/framework v5.8.4 requires illuminate/container 5.8.* -> satisfiable by illuminate/container[v5.8.0, v5.8.11, v5.8.12, v5.8.2, v5.8.3, v5.8.4, v5.8.8, v5.8.9].
    - laravel-zero/framework v5.8.5 requires illuminate/container 5.8.* -> satisfiable by illuminate/container[v5.8.0, v5.8.11, v5.8.12, v5.8.2, v5.8.3, v5.8.4, v5.8.8, v5.8.9].
    - Can only install one of: illuminate/container[v5.8.0, v5.7.20].
    - Can only install one of: illuminate/container[v5.8.11, v5.7.20].
    - Can only install one of: illuminate/container[v5.8.12, v5.7.20].
    - Can only install one of: illuminate/container[v5.8.2, v5.7.20].
    - Can only install one of: illuminate/container[v5.8.3, v5.7.20].
    - Can only install one of: illuminate/container[v5.8.4, v5.7.20].
    - Can only install one of: illuminate/container[v5.8.8, v5.7.20].
    - Can only install one of: illuminate/container[v5.8.9, v5.7.20].
    - Installation request for illuminate/container (locked at v5.7.20) -> satisfiable by illuminate/container[v5.7.20].


Installation failed, reverting ./composer.json to its original content.

I'm always confused by these darn composer errors, sometimes it's quite obvious but in this case it's not at all, apparently one of the dependencies has a locked dependency for illuminate/container locked at 5.7.20 ? I did some digging around but could not locate which one is causing the error

Maybe you'll have more luck

One other minor thing, I've been building a lot of CLI apps lately and have started using the awesome "php-school/cli-menu" package. Laravel Zero has a wrapper for it but I found it's easier to pull in the original directly as the wrapper adds limitations in my experience. Overall, I ended up finding no reason to use Laravel Zero

It was my understanding that Laravel Zero is meant to be an alternative to Laravel

It's own instructions https://laravel-zero.com/docs/installation/ detail how you install the Zero installer globally and then new up projects using the zero installer instead of the laravel installer

What this means is that if this package is meant to be added to Laravel projects using composer, then it should not be pulling in Laravel Zero as a dependency

It's not how Zero is intended to be used, it's also not necessary at all if you want to build awesome command-line tools that are meant to enhance a Laravel project, including the cli-menu I referenced above.

You can also pre-load your custom project commands as part of your package's service provider so you won't need to do things like ./vendor/bin/laradock and instead just do php artisan laradock directly

I do this in many of my projects and am happy to show you how I do it

and it would be nice if simply typing php artisan laradock (or laradock-cli) would bring bring up a nice CLI menu rather than have to use the commands manually

I've gotten pretty good at developing these menus, with keyboard shortcuts included, with sub-menus and user input where needed

Lastly, bit off-topic of this issue, I read how this package is meant to be "zero configuration" and does things like guess your php version and maybe guess other things.. that's nice and nifty for some users but I'm actually hoping to use this to produce production-ready laradock configurations so I hope it's possible to disable this guesswork and specify exactly what I want the settings to be

Not working on PHP 7.4

PHP version: 7.4
Laradock-CLI version: 0.4.5

I'm getting this error message.

In Figlet.php line 1095:
Invalid characters passed for attempted conversion, these have been ignored