Jonas Eberle

This mostly succeeds with calling the scripts through the web now. As noted in the issue it might not solve the ultimate problem, though so I would let that sit...

Hi @gordalina thank you. The results are still not 100% safe. It can still happen that a frontend user hits a thread whose realpath cache has not been cleared. I'll...

This patch mostly succeeds with executing commands now (`stat:clear` and `opcache:reset`). Yet our problems (post-symlink-switching-deployment PHP thinks some files are there which are not) remain and are well described by...

Thank you. For the shared hosting in question ([Hetzner Level 19](https://www.hetzner.com/webhosting/level-19)) this shows: https://gist.github.com/jonaseberle/996d2a7dc930f89b2241bdef9706c3b7 I looked into deactivating the realpath cache: Unfortunately that's not possible on that shared hosting because...

Yes, also with `--web` it happens that we get `404` because it might be just too fast for some hosters to create the file and access it through the web...

From an experiment with some necessary workarounds for the reverse proxy this has become pretty trivial and easy to maintain :) So yes, I am happy and feel honored to...

I never expected that we might need an SSH agent in a non-interactive environment ;) Omitting it [here](https://github.com/jonaseberle/github-action-setup-ddev/blob/master/lib/main.js#L68) was just a minor optimization that might save a second during startup....

In that case we might want to recommend putting keys into the runner's `~/.ssh/` directory directly instead: https://github.com/jonaseberle/github-action-setup-ddev#ssh-keys

Symlinking DDEV `homeadditions` has stopped working at some point. You should copy them ;)

The path in the runner is probably `/var/lib/docker/volumes/ddev-global-cache/`. (`docker volume inspect ddev-global-cache`)