A task dev:serve command should start several other tasks, that can all be defined individually
- task:dev:process:db Start Postgres running in a container with a random port
- That port should get injected as an env variable into all other tasks
- task:dev:process:web:
php artisan serve
- Pre-req: composer install
- task:dev:process:vite:
npm run dev
- task:dev:process:work - start the queue worker. Can't remember exactly what that looks like but docker compose should have an example
- Also should have a general pre-req of
task dev:db:refresh which already exists and re-seeds the database
For pre-flight check, we should have a task that runs a script that makes sure:
- PHP 8.2+ is available
- Postgres is available
- Postgres has the necessary database (this is documented)
Basically what I am thinking is that i want agents to have a one-stop shop to run 1 command to help troubleshoot setup (e.g., installing postgres might depend on agent environment, but validating postgres we can do for nix systems) and then for getting a dev server up and running.
I also would use task:dev:serve myself I think.
A task dev:serve command should start several other tasks, that can all be defined individually
php artisan servenpm run devtask dev:db:refreshwhich already exists and re-seeds the databaseFor pre-flight check, we should have a task that runs a script that makes sure:
Basically what I am thinking is that i want agents to have a one-stop shop to run 1 command to help troubleshoot setup (e.g., installing postgres might depend on agent environment, but validating postgres we can do for nix systems) and then for getting a dev server up and running.
I also would use task:dev:serve myself I think.