Silverstripe Recipe broken with Silverstripe CMS 6 #4092
Unanswered
wernerkrauss
asked this question in
Bugs
Replies: 1 comment
-
You should ideally use Since CMS 6 still supports the old syntax, if you're using that path to the binary you can still use |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Deployer Version
v.7.5.12
Target OS
Any / Debian
Which PHP version are you using?
PHP 8.4
Content of deploy.php or deploy.yaml
In Silverstripe 6, framework/cli_script.php doesn't exist any more.
Now we have to use
vendor/silverstripe/framework/bin/sake
The command also changed: it's now
run('{{release_or_current_path}}/vendor/silverstripe/framework/bin/sake db:build --flush');
calling
sake -v' returns the version like
Silverstripe Sake CMS Recipe: 6.0.0`Is there a better way to determine the current version of a package during deployment?
Steps to reproduce
Try to deploy a project based on Silverstripe6; the task silversripe:build and silverstripe:buildflush won't do anything, cause {{silverstripe_cli_script}} is empty.
Beta Was this translation helpful? Give feedback.
All reactions