"sessions" table does not exist in Dev setup about traewelling HOT 8 CLOSED

Do you overwrite SESSION_DRIVER in you env? This should be database when seeding.

from traewelling.

Do you overwrite SESSION_DRIVER in you env? This should be database when seeding.

Did not change anything about this value – as there was nothing in the documentation.

Would you mind summarizing the necessary steps to have a seeded database in the dev setup? I'd be happy to add it to the documentation.

from traewelling.

Would you mind summarizing the necessary steps to have a seeded database in the dev setup?

Iirc there's only a few steps:
Clone, composer install, npm install, npm run dev

DB-wise you'll have to define your database. Either use sqlite (DB_HOST should point to a .sqlite file) or mysql/maridb.

Once that is set up you'll need the following commands:

• php artisan key:generate
• php artisan migrate:fresh --seed
• php artisan passport:install

from traewelling.

Ohhhhh. You meant the docker setup. Sorry, i didn't see that the first time.
I haven't used the docker setup until now. Maybe @jeyemwey can help here?

from traewelling.

The sessions table is usually the first table that is queried on a page request, and that fails when the database isn't available.

The error presented is a MySQL error, so the connection and login seems to work, but the database is empty. Can you try php artisan migrate before the db seed command? That should initialize empty tables.

from traewelling.

The sessions table is usually the first table that is queried on a page request, and that fails when the database isn't available.

The error presented is a MySQL error, so the connection and login seems to work, but the database is empty. Can you try php artisan migrate before the db seed command? That should initialize empty tables.

So what you're saying is:

1. Run compose up without SEED_DB=true
2. Run php artisan migrate
3. Run compose up WITH SEED_DB=true

Correct?

from traewelling.

from traewelling.

Please retry with the changes from #2074 and reopen if the error still exist for you.
If you don't overwrite SESSION_DRIVER in your environment the table should be created.

from traewelling.