Hi, Perhaps you could post your dreams in a form of solr usability suggestion? :)
http://solrstart.uservoice.com/forums/216001-usability-contest/filters/top I hope it is accepting contributions still. What you are saying from the point of view of Solr UI in-built version-control features, I would approach from a different angle: actually build a deployment environment which would pick the necessary config files and binaries and deploy them into an (existing or new) solr instance. We run builds on bamboo where it is possible to configure building from certain branches / trunk and jenkins to deploy the builds. We currently do not use jenkins to deploy solr, but I would imagine that's quite possible. Dmitry On Fri, Aug 16, 2013 at 8:31 PM, SolrLover <bbar...@gmail.com> wrote: > Currently we use multiple stopwords.txt, protwords.txt , elevate.xml and > other solr related config files. We use subversion to maintain various > versions of these files manually. I was thinking of checking the forum on > the process that is being followed to preserve the version history other > than just using a version control tool. > > May be I'm dreaming but it would be great if there is a UI to edit the > files, connect to a version control repository and commit the changes > there. > This way I would be able to view all version of file in SOLR admin panel > and > also revert back to any version needed... > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Best-way-to-version-config-files-tp4085115.html > Sent from the Solr - User mailing list archive at Nabble.com. >
