[Workbench] `testbench.yaml` proposed structure for Workbench Improvements
Closed this issue · 1 comments
crynobone commented
workbench:
start: /nova
user: taylor@laravel.com
guard: web
sync:
- from: ./public/
to: public/vendor/nova
build:
- asset-publish
- create-sqlite-db
- migrate:refresh
assets:
- nova-assets
purge:
directories: []
files: []
sync
would be useful if we want to listen to asset changes directly during development by creating symlink instead ofvendor:publish
build
would be useful to simplifycomposer.json
'sscripts
section, instead of having to remember multiple commands user would just need to runworkbench:build
orworkbench:watch
assets
list of asset tags to be executed withvendor:publish
via the newworkbench:build
Proposed new command
workbench:build
This command would be useful to replace common scripts such as the following:
"build": [
"@php vendor/bin/testbench vendor:publish --tag=laravel-assets --ansi --force",
"@php vendor/bin/testbench workbench:create-sqlite-db",
"@php vendor/bin/testbench migrate:refresh"
],
Instead, we can build a set of recipes to be defined under build
configuration.
crynobone commented