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 was archived by the owner on May 1, 2019. It is now read-only.
Platform.sh cli configures its docroot (_www) as a symlink to ./.platform/local/builds/default/web.
When I execute platform-docker start and execute platform-docker ssh http, /var/platform/_www cannot be opened because of the symlink. Docker, afaik, doesn't allow to configure follow hosts' symlinks.
I could solve it manually configuring one of this two options:
Configuring the docroot as ./platform/local/builds/default/web when initializing platform-docker
Mounting ./.platform/local/builds/default/web in _www and configuring docroot with _www.
I like more the first option so I'm thinking about guessing, in InitCommand.php:51, if there is a platform.sh project builded, find which is its docroot and suggest that value to the user when prompting for docroot.
I don't know very well how platform.sh cli works with builds and if this solution is viable.
Platform.sh cli configures its docroot (_www) as a symlink to ./.platform/local/builds/default/web.
When I execute
platform-docker startand executeplatform-docker ssh http,/var/platform/_wwwcannot be opened because of the symlink. Docker, afaik, doesn't allow to configure follow hosts' symlinks.I could solve it manually configuring one of this two options:
./platform/local/builds/default/webwhen initializing platform-docker./.platform/local/builds/default/webin _www and configuring docroot with _www.I like more the first option so I'm thinking about guessing, in InitCommand.php:51, if there is a platform.sh project builded, find which is its docroot and suggest that value to the user when prompting for docroot.
I don't know very well how platform.sh cli works with builds and if this solution is viable.
What do you think about it?