Patrick Dawkins

@SecondeJK environments now automatically rebuild whenever you change a variable, so there is a workaround available: ```sh platform vset _redeploy "$(date)" ```

Yes, the commit => build connection is still very much in place. I'm not sure why a rebuild would be needed without a change in source code, unless the build...

Platform.sh container updates for security/maintenance are applied on redeploy, without the need for a rebuild of the application code. If it's an application-level dependency, then ideally the update should be...

For now, if you have the platform.rc file included, remove it. You won't have autocompletion unfortunately. This needs some investigation to support (in the symfony console completion library https://github.com/stecman/symfony-console-completion)

@dmsmidt since v2.6.0, I suppressed autocompletion error output so that the platform.rc file does not attempt to `eval` it, and you won't have a crash with Fish. Autocompletion won't work

This was always intended to be separate, it would just create an SSH key via the normal `ssh-keygen` (which defaults to `~/.ssh/id_rsa`) and then you'd proceed to use SSH via...

Sorry for the rather late reply (!) - does this still fail, and what particular command fails? (and do you know of other Symfony Console applications that successfully support Eshell?)

Not yet. It's a feature request we have in the queue (an API feature first, then CLI) It is possible to set environment variables in .platform.app.yaml, if that works for...

@DuaelFr good tip If you do open the project's root folder, you should mark the `builds` directory as Excluded, and mark `www` as a Resource.

Hm. With my method I'm not getting a dialog for function declarations. Just to confirm, it looks a bit like this: