Patrick Dawkins
Patrick Dawkins
Agreed. For now you could use something like: ```sh platform multi --projects "$(platform project:list --title 'test' --pipe)" "project:info" ``` That will run `project:info` on all of your projects that have...
I think this would depend on #670, yes, so you have both a handy link to the environment URL, and a link to the logs (the web UI) via the...
--pipe just prints out the SSH uri(s) for the environment, so I'm not sure what -i should do here
For very detailed output including PHP-level errors or warnings, run the command with `-vvv`, e.g. ```sh platform build -c -vvv ```
This sounds like a good feature request IMO. The GitLab integration runs on the Platform.sh (project's) server, not in the CLI, so it's not the CLI's responsibility (and it's not...
The symlinks aren't hard-coded. What does your repository file structure look like?
OK... the symlinks are created before the build hooks run, so that's why you get the wrong path if you're moving stuff around in the build hooks. The `--abslinks` option...
It might be less complicated to remove Platform.sh's Drupal processes, and build Drupal yourself, something like: ``` yaml # don't build as Drupal automatically build: flavor: composer hooks: build: |...
That's why `platform build` (with no options) uses symlinks; to help ease this pain. But you'd still need to recompile the CSS when you edit your SASS. I believe you...
If you merely want to tweak a little bit of CSS and see the changes immediately so that you can try things out (before editing your SASS later), you could...