Add section on completeness/status to README

[magro]

Based on information from querqy#25

[epugh]

This is great!

So here is more of an open ended question.. If you were to adopt Chorus directly, versus pulling in some of the parts individually, what would you need Chorus to do to be your "Development" environment? One reason I pushed with Docker-compose was of course to make demos easier, and that's the point of the quickstart.sh script. Maybe should be called demo.sh instead ;-).

However, what would need to change for it to be "I am developing stuff in Dev for my firm"? What would be the steps to go from "I downloaded Chorus from the repo" to "I need to add a new feature to the ecomm search, so I do X on my laptop to get started". Is it a well understood way to load my own data? My own Solrconfigs etc? Could I take quickstart.sh and create mywebstore_developer_environment.sh?

While Chorus ships with the default /solr/solr_home/ecommerce dir, you could just as easiliy load /solr/solr_home/mywebstore dir!

[magro]

So here is more of an open ended question.. If you were to adopt Chorus directly, versus pulling in some of the parts individually, what would you need Chorus to do to be your "Development" environment?

A good question, and not easy to answer :-)
For one thing it probably depends on the tooling that the team chose for the local environment (docker-compose/minikube/kind etc). I can imagine to use solr and smui locally, I've never worked with Quepid or RRE so far, so I right now I cannot tell s.th. about that.

However, what would need to change for it to be "I am developing stuff in Dev for my firm"? What would be the steps to go from "I downloaded Chorus from the repo" to "I need to add a new feature to the ecomm search, so I do X on my laptop to get started". Is it a well understood way to load my own data? My own Solrconfigs etc? Could I take quickstart.sh and create mywebstore_developer_environment.sh?

While Chorus ships with the default /solr/solr_home/ecommerce dir, you could just as easiliy load /solr/solr_home/mywebstore dir!

In my last project with Solr we kept solrconfig/managed-schema in our application git repo, and during continuous deployment these files got pushed to Solr via Zookeeper by some application/startup code.
For indexing in a local environment I'd use our indexer (we should have one ;-)), which needs to get product data from somewhere (locally or from some external system).

Not sure if I'd use chorus directly, probably it would rather be picking parts of it and integrating these parts (maybe somehow adjusted) in the project specific local environment...

[magro]

That was a rough guess, is that correct?

[epugh]

I think so!

[magro]

That was a rough guess, is that correct?

[epugh]

and yes, I agree...

[magro]

That was a rough guess, is that correct?

[epugh]

Yep. and I'll be doing some Katas specific to each of those tools as well to provide more support to users.

[epugh]

Once it's aged a bit more, I'll merge querqy#23 and it'll add a lot more "production" oriented logging to Chorus as well.. We'll monitor SOlr, ZK, etc...