Open gilesknap opened 3 months ago
This seems a little complicated. Can this be simplified?
Just working inside the container is very easy and this would work for in cluster testing and development too.
We just need to be able to ensure people don't loose their work.
For further review
In future we need to support a clean workflow for modifying support modules withing the context of a generic IOC that depends upon them.
We have a proposal for:
this would mv the support module into a folder that is a peer to the ioc-xxxx repo folder and symlink the /epics/support/SUPPORT-MODULE to that - plus make it writable. This means that your support module changes are in the host filesystem and will not be lost on container rebuild.
This issue proposes that we as well as making the symlink, also update the devcontainer.json file to mount this folder into epics/support/SUPPORT-MODULE. This means that:
Actions:-
ibek dev support
changeThis is from a conversation with @coretl today.