Not sure if it should be in Ideas or the new category… please move if needed.
Are there any plans to split the ReFramework into branches for working with Orchestrator and without it?
While I admire the amount of work you’ve put into it, I think it might be trying to do a little too much and it might become confusing.
Splitting it, maybe not yet but in the not too distant future, would allow it to evolve with a clear goal focus:
- for Orchestrator version to enable as quick start of actual implementation and reliable/repeatable configuration as possible while leveraging Queues etc.
- for non-Orch version (which by definition would be different scale) to provide “plumming” that eases not having Queues, Assets etc. available.
I don’t really have a horse in that race. Just a thought that I’d like to share