search

matthewbdaly / artisan-standalone

Allows you to use Artisan outside of a Laravel install.
MIT License
32 stars 10 forks source link

Seems array cache is being ignored? #2

Closed roblesterjr04 closed 4 years ago

roblesterjr04 commented 5 years ago

I get this error: In PackageManifest.php line 168: ... bootstrap/cache directory must be present and writable.

matthewbdaly commented 5 years ago

Yes, the specified directory must exist and be editable.

I normally use this package in conjunction with matthewbdaly/laravel-package-boilerplate, which is set up to create that directory on install. It could possibly do with having a more general solution, though.

How are you using it? Have you pulled it in as a dev dependency on a package you're working on?

roblesterjr04 commented 5 years ago

Well, i realized i wasn't actually using array cache - i have a .env file ignored but present locally in the project that i use for running unit tests (sensitive keys) - It was setting the cache to file. Anyway, i created and ignored the bootstrap/cache directory and the artisan console works, but it won't really work for me because i ultimately was trying to get tinker to work.

matthewbdaly commented 5 years ago

Yes, the main intent of this package is to make the generator commands work. It's not really set up to work with a database. Though I could take a look this weekend and see how practical it might be to do that.

matthewbdaly commented 5 years ago

Just FYI, I've been able to resolve this issue, at least with laravel-package-boilerplate. It now pulls in Tinker by default, and I've added the config files for the database, so it should support working with the database as you'd normally expect.

If you're able to verify that it works for your use case, that would be great.