How to maintain appsody support without codewind-workspace bind mount

[makandre]

Codewind version: 0.6.0
OS:

Che version:
IDE extension version:
IDE version:
Kubernetes cluster:

Question synopsis:

This is somewhat related to #564

With the /codewind-workspace docker bind mount going away, Appsody support will break because it Appsody relies on being able to bind mount things into their container:

1. The appsody-controller (tracked by Copy controller into container instead of mounting appsody/appsody#467 Appsody on K8S should avoid separate mount for the controller appsody/appsody#399)
2. Various files or directories in the project dir; what's actually mounted is dependent on the stack used

How do we ensure 2 still works?

** options for pfe **

• Have an appsody-workspace that is created in a location that can be bind mounted to (like we currently do in 0.5.0 for codewind-workspace). PFE will not sync files and the appsody cli will directly mount to the appsodsy-workspace. User has to create their project in this workspace.
• PFE will create a build area somewhere in the docker share space. On a sync, PFE will copy the files to that location for the the appsody cli to then bind mount to. User can create their project anywhere they like
• We call the appsody-cli directly on the users workspace

[makandre]

(options above suggested by @tobespc )

Both options 1 or 2 sounds feasible. Just have to make sure the host path of that space where appsody projects are put into will be made known to the appsody extension (perhaps via env var)

[makandre]

Short term solution to keep a mounted-workspace on Codewind side is mostly done. However we need appsody/appsody#399 to address the controller mount

[makandre]

Closing this one. Use #1160 to track long term solution.