Marcus Collier

yep, I looked into it and decided nope. Just had the issue that rebooting the solr container lost the core, as it’s in a weird path. Just managed to work out the magical <str name="coreRootDirectory">/var/www/html/.solr/indexes</str> config which appears to be working. Just testing it now.

firesphere

For WebDav, if you look at the project on GitHub, there's a CWP compatibility project. Which will probably end up being a separate module, that adds WebDav store and other current FTS mis-matches to reduce the overhead of migrating

firesphere

So, a separate webserver needs to be set up to handle this, on the Solr machine, if it's remote

firesphere

As Solr requires the configuration files to be in place before a core can get loaded

firesphere

Basically, the post method, is to post to a webserver (not Solr) to create the configuration.

Marcus Collier

question though on the configuration - how does the ‘post’ method work? my take is it sends the config to solr, but does it require anything special (CWP, used webdav) so little confused on how it’s meant to work.

firesphere

But I'm not familiar with how well it actually works, it sometimes does some confusing things