The idea is to set up platformsh with the local stack. To do that few things has to be done:
[x] provide the .platform and .platform.app.yml
[x] adapt the .platform and .platform.app.yml because ezplatform is not the root now with eZ Launchpad
[x] Adapt and map the services depending on services enabled with the local stack
[x] Put the good .platform and .platform.app.yml into their correct places
[x] update the documentation to explain the approach
Note: To me, there is no real reason to have a command that would "deploy" for Platformsh. The whole point is to deploy through git.
But we need something like ~/ez platformsh:setup that would do the mapping and file copies
[x] Also it might mean a revamp of the Command folder to group commands by "prefix" docker and platformsh for now
[ ] TBD: we could wrap some platformsh command if needed, need to think more on that.
The idea is to set up platformsh with the local stack. To do that few things has to be done:
ezplatformis not the root now with eZ LaunchpadNote: To me, there is no real reason to have a command that would "deploy" for Platformsh. The whole point is to deploy through git. But we need something like
~/ez platformsh:setupthat would do the mapping and file copies[x] Also it might mean a revamp of the Command folder to group commands by "prefix" docker and platformsh for now
[ ] TBD: we could wrap some
platformshcommand if needed, need to think more on that.