Error on migration on sqlite about pulse HOT 7 CLOSED

@jessarcher we use SQLite for our tests in github actions. Now our actions pipeline fails every time when trying to run migrations. Is there a way we can disable the pulse migration if the environment is testing?

You could tell the environment that pulse isn't enabled. That way, it won't run the migration. E.g.:

// config/pulse.php
'enabled' => env('PULSE_ENABLED', true),

// phpunit.xml
<server name="PULSE_ENABLED" value="false"/>

@jessarcher I thought it was a bug at first as well, but I'm leaning towards maybe it should be a warning in the Pulse docs rather than a code fix? Great work on Pulse, btw. :)

from pulse.

Hi @nezaboravi,

Pulse currently only works with a MySQL database, as mentioned at https://laravel.com/docs/10.x/pulse#installation.

I can see how this would be annoying in a project that uses SQLite for local development. I think we'll look at making it possible to disable the Pulse migrations in a local environment.

I've done some work in #64 to add Postgres support. It might be trivial to add SQLite support as well, although I don't think I'd recommend using Pulse with SQLite in production.

from pulse.

@jessarcher we use SQLite for our tests in github actions. Now our actions pipeline fails every time when trying to run migrations. Is there a way we can disable the pulse migration if the environment is testing?

from pulse.

// phpunit.xml
<server name="PULSE_ENABLED" value="false"/>

This is the way 👍

from pulse.

Thanks for the hint, @joelhinz 👍

from pulse.

Thanks for the hint @joelhinz and @timacdonald!

from pulse.

// phpunit.xml
<server name="PULSE_ENABLED" value="false"/>

This is the way 👍

This is the way.

from pulse.