You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Certain types of projects will require additional steps beyond simply cloning the Git repo, such as installing composer dependencies or building assets.
The site manager should have some concept of "tasks" that allows us to specify commands that should be run after a clone or pull. Each task would be stored as its command with a friendly name as a key, e.g.
Eventually a subset would be predefined for each project type / template / whatever they end up being called. For example a PHP project would use composer, but a Laravel project would use bothcomposer and laravel-migrate.
The text was updated successfully, but these errors were encountered:
Certain types of projects will require additional steps beyond simply cloning the Git repo, such as installing composer dependencies or building assets.
The site manager should have some concept of "tasks" that allows us to specify commands that should be run after a clone or pull. Each task would be stored as its command with a friendly name as a key, e.g.
Eventually a subset would be predefined for each project type / template / whatever they end up being called. For example a PHP project would use
composer
, but a Laravel project would use bothcomposer
andlaravel-migrate
.The text was updated successfully, but these errors were encountered: