we still have a lot of cleanup before I'd use this as a model, but the rough strategy we employed is:
1. Hide sensitive code behind an API
2. Open source everything else (regardless of Platform/Self-Hosted
3. Use env vars and feature flags to determine what is visually displayed
The docker-compose for self-hosted is the same stack as every project on the Platform which helps.
Comments
Any more details you are willing to share on how the shared code is imported and extended on the platform side?
We have a similar split, and currently use lerna to publish a collection of individual packages that get imported and extended on the other side.
we still have a lot of cleanup before I'd use this as a model, but the rough strategy we employed is:
The docker-compose for self-hosted is the same stack as every project on the Platform which helps.