jasonpatrick02

Sep 20th, 2021 02:14 PM

hello everyone! I was hoping someone could help me out with this issue I'm having when I try to run 'composer install' - below is the error I am getting:

Installing dependencies from lock file (including require-dev) Verifying lock file contents can be installed on current platform. Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run composer update or composer update <package name>. Nothing to install, update or remove Generating optimized autoload files

Illuminate\Foundation\ComposerScripts::postAutoloadDump @php artisan package:discover

Doctrine\DBAL\Driver\PDO\Exception

SQLSTATE[HY000] [1049] Unknown database 'c-app'

at C:\Users\Jason\Sites\c-app\vendor\doctrine\dbal\lib\Doctrine\DBAL\Driver\PDO\Exception.php:18 14▕ final class Exception extends PDOException 15▕ { 16▕ public static function new(\PDOException $exception): self 17▕ { ➜ 18▕ return new self($exception); 19▕ } 20▕ } 21▕

1 C:\Users\Jason\Sites\c-app\vendor\doctrine\dbal\lib\Doctrine\DBAL\Driver\PDOConnection.php:44 Doctrine\DBAL\Driver\PDO\Exception::new(Object(PDOException))

2 [internal]:0 Illuminate\Foundation\Application::Illuminate\Foundation{closure}(Object(App\Providers\AppServiceProvider))

I also tried running 'composer require doctring/dbal' and got the following:

Using version ^3.1 for doctrine/dbal ./composer.json has been updated Running composer update doctrine/dbal Loading composer repositories with package information Updating dependencies Your requirements could not be resolved to an installable set of packages.

Problem 1 - tcg/voyager is locked to version 1.4.x-dev and an update of this package was not requested. - tcg/voyager 1.4.x-dev requires doctrine/dbal ^2.5 -> found doctrine/dbal[v2.5.0, ..., 2.13.3] but it conflicts with your root composer.json require (^3.1).

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Any help would be greatly appreciated.

alexzerbach

Sep 20th, 2021 06:44 PM

I posted the same error today. Going to follow this thread as well in hopes someone can help you solve it.

bobbyiliev

Sep 20th, 2021 11:06 PM

Hi there,

As far as I can see you’ve added a dash in the database name. Note that this is not a valid name. This is not a Wave specific thing but it is a convention for most database engines.

Also first connect to your MySQL instance and create the database. Only once the database has been created, specify it in Wave.

Let me know how it goes.

Best,

Bobby

jasonpatrick02

Sep 21st, 2021 07:23 AM

Hi Bobby -

Thank you so much for your help, it seems that it was an issue with how I setup the database. I started with a fresh db and was now able to complete all of the steps, including composer install, artisan migrate, and artisan seed. Now the issue that I'm having is that I cannot see the app at my test URL. I changed wave.test to myapp.test and I'm getting DNS_PROBE_FINISHED_NXDOMAIN in my browser. Any help on this new issue would be greatly appreciated :)

**EDIT - I've installed Valet for Windows and now when I try to access the test site I get "Valet - Not Found" in the tab and '404 not found' within the browser. I will keep investigating to see if I messed up the Valet install or missed a step.

jasonpatrick02

Sep 21st, 2021 07:31 AM

@Alex I don't really have experience with MySQL and I was setting up the DB completely wrong. What fixed the issue for me was creating the database in MySQL CLI, I created a user and granted permissions, and then setup the ODBC connection.

jasonpatrick02

Sep 22nd, 2021 07:55 AM

Update: I've installed Valet for Windows and now when I try to access the test site I get "Valet - Not Found" in the tab and '404 not found' within the browser. I have not been able to figure out why :(

bobbyiliev

Sep 22nd, 2021 09:56 AM

Hi there,

Happy to hear that you've got the database problem all sorted out.

Regarding Valet, actually according to the Laravel documentation Valet is only available for macOS:

https://laravel.com/docs/8.x/valet

For Windows, you could either just use the WAMP stack and visit your project via localhost directly. Or you could try using Laragon. I've personally not used it actually but it is quite popular for Laravel on Windows.

What I like to do is to use VS Code and do a remote development on a DigitalOcean server:

https://devdojo.com/alexg/remote-development-in-visual-studio

Hope that this helps!

jasonpatrick02

Sep 22nd, 2021 10:15 AM

Thank you Bobby I will give that a try!

bobbyiliev

Sep 22nd, 2021 11:19 AM

No problem! Let me know how it goes.