Using Velocity, you can have some results-driven HTML served by Solr and
all your JS, CSS etc 'assets' served by Apache from /var/www/html.
Warning: the Velocity learning curve is steep and you still need a
separate front-end web app for security because Velocity is a templating
output filter. Eric, please correct me!
cheers -- Rick
On 01/04/2018 11:45 AM, Erik Hatcher wrote:
All judgements aside on whether this is a preferred way to go, have a look at
/browse and the VelocityResponseWriter (wt=velocity). It can serve static
resources.
I’ve built several prototypes this way that have been effective and business
generating.
Erik
On Jan 4, 2018, at 11:19, Matthias Geiger <matzschman...@gmail.com> wrote:
Hello,
i have a web application that delivers static html content to the user.
I have been thinking about the possibility to deliver this content from
solr instead of delivering it from the filesystem.
This would prevent the "double" stored content (html files on file
systems + additional solr cores)
Is this a viable approach or a no go?
In case of a no go why do you think it is wrong
In case of the suggestion of a nosql database, what makes noSql superior to
solr?
Regards and Thanks for your time
