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
{{ message }}
This repository has been archived by the owner on Sep 16, 2021. It is now read-only.
I am hoping to release PHPCRSH 1.0 around the new year. I think we should switch the tutorial to using the shell rather than the CLI and that it should be included as a dev dependency in the tutorial composer.json.
or we could assume the user has started the shell via php app/console doctrine:phpcr:shell and simple show the command:
PHPCRSH> node:list /
But I know that a number of developers wouldn't use the shell in an efficient way, i.e. they login, run a command, then logout again because they don't know about tabs / tmux etc.
The text was updated successfully, but these errors were encountered:
difficult to say indeed. but i tend to say we should switch to use the shell. and explain that there is the shell (just like postgres/mysql/... cli clients) and link to phpcr.github.io that explains the details. and point out (maybe in a couple of strategic places) that the shell can be scripted through the symfony console - this is the main reason to not use the shell i think.
the whole change should only be merged when phpcrsh is released, phpcr-odm released in a version that includes the shell and the sandbox and CMF SE come with the shell.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am hoping to release PHPCRSH 1.0 around the new year. I think we should switch the tutorial to using the shell rather than the CLI and that it should be included as a
dev
dependency in the tutorialcomposer.json
.For example
Would be replaced with
or we could assume the user has started the shell via
php app/console doctrine:phpcr:shell
and simple show the command:But I know that a number of developers wouldn't use the shell in an efficient way, i.e. they login, run a command, then logout again because they don't know about tabs / tmux etc.
The text was updated successfully, but these errors were encountered: