Development environment for containerized Teaclave services

[bigdata-memory]

I found there seems no straightforward way to prepare a development environment for containerized Teaclave services. I think it could improve the collaboration efficiency and dev. productivity if we can streamline it using standard approaches with comprehensive documentation.
Firstly, I often use Emacs to develop, so those bother me don’t necessarily apply to developers who use other IDE at all, e.g. VS.
I lists my consideration here for your reference, perhaps, we may identify some more associated opportunities later.

1. Adding both trusted and untrusted parts of code tags to LSP system.
2. Containerizing the Teaclave source code in a local docker volume instead of host FS.
3. Containerizing development tools e.g. Emacs, VS in a development container mounted with Teaclave source code volume.
4. The Build Container can rebuild the topic branch triggered by the changes from development container.
5. The RT containers could reuse the same containers images for different service.
6. The RT service containers can be instructed or automatically detect the service binaries updates to roll up in dev. mode.

[mssun]

Thanks for raising this issue.

Yes, this is very important for all collaborators. Currently, we only have a simple document about some tips for Teaclave development: https://teaclave.apache.org/docs/development-tips/.

[bigdata-memory]

The crate cmake is capable to manage the build of native code well. it looks possible to address the problem of separated rust codes in LSP.