Federati Nu: Federated N-series GNU Socialsolr
https://nu.federati.net/tag/solr/rss
Updates tagged with solr on Federati Nu: Federated N-series GNU Social!lnxw48a1: @musicman I just heard of #MeiliSearch last night, so I did not do any deep diving. I know that #YaCy uses #Solr, but I do not know if it always did.
https://nu.federati.net/notice/3366315
lnxw48a1's status on Friday, 14-May-2021 15:38:57 UTC@<a href="https://nu.federati.net/user/12" class="h-card u-url p-nickname mention" title="Douglas A. Whitfield">musicman</a> I just heard of #<span class="tag"><a href="https://nu.federati.net/tag/meilisearch" rel="tag">MeiliSearch</a></span> last night, so I did not do any deep diving. I know that #<span class="tag"><a href="https://nu.federati.net/tag/yacy" rel="tag">YaCy</a></span> uses #<span class="tag"><a href="https://nu.federati.net/tag/solr" rel="tag">Solr</a></span>, but I do not know if it always did.2021-05-14T15:38:57+00:00LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}musicman: proof is in the pudding, as they say, but sounds like I have learned a variety of things this morning: 1. "Since Alfresco Installer was discontinued from Alfresco 5.2, this project provides a command line installer for Alfresco Community 6.1 and Alfresco Community 6.2 to be used in Docker Compose installations." -- not sure the background on this decision, but paired with the other information, seems as though I may have been mistaken about the #Alfresco community. 2. The Alfresco forums are super useful. 3. Even if you know nothing about a project, it might be worth checking their bug tracker. Of course, you need to know enough about the product to understand the bugs, which I probably didn't have when I started this project. Once I got confident enough in my understanding to post on the forum though, I was almost certainly qualified to go bug hunting at that point. It's funny, because bug reports is where I generally start. I guess the difference here was I wasn't looking for an easy out for a support ticket. I guess when I am doing my own infrastructure work, I should keep some of those fire fighting habits. That said, since we support Alfresco, as well as #solr, and #Tomcat, in the long term it is probably good that I spent some time beating my head against the wall with it. (we never get Alfresco tickets, but we do get Tomcat tickets)
https://nu.federati.net/notice/3327626
musicman's status on Thursday, 06-Aug-2020 16:11:09 UTCproof is in the pudding, as they say, but sounds like I have learned a variety of things this morning:<br /><br /> 1. "Since Alfresco Installer was discontinued from Alfresco 5.2, this project provides a command line installer for Alfresco Community 6.1 and Alfresco Community 6.2 to be used in Docker Compose installations." -- not sure the background on this decision, but paired with the other information, seems as though I may have been mistaken about the #<span class="tag"><a href="https://nu.federati.net/tag/alfresco" rel="tag">Alfresco</a></span> community.<br /><br /> 2. The Alfresco forums are super useful.<br /><br /> 3. Even if you know nothing about a project, it might be worth checking their bug tracker. Of course, you need to know enough about the product to understand the bugs, which I probably didn't have when I started this project. Once I got confident enough in my understanding to post on the forum though, I was almost certainly qualified to go bug hunting at that point.<br /><br /> It's funny, because bug reports is where I generally start. I guess the difference here was I wasn't looking for an easy out for a support ticket. I guess when I am doing my own infrastructure work, I should keep some of those fire fighting habits. <br /><br /> That said, since we support Alfresco, as well as #<span class="tag"><a href="https://nu.federati.net/tag/solr" rel="tag">solr</a></span>, and #<span class="tag"><a href="https://nu.federati.net/tag/tomcat" rel="tag">Tomcat</a></span>, in the long term it is probably good that I spent some time beating my head against the wall with it. (we never get Alfresco tickets, but we do get Tomcat tickets)2020-08-06T16:11:09+00:00Douglas A. Whitfieldmusicman: below is a section of a #docker compose file. Why is it that under environment in share you have different sections such as JAVA_OPTS, but under solr6 the configs just have a - in front of them. I tried adding JAVA_OPTS to solr6 and got a yml syntax error ``` share: image: alfresco/alfresco-share:6.2.0 mem_limit: 1g environment: REPO_HOST: "alfresco" REPO_PORT: "8080" JAVA_OPTS: " -Xms500m -Xmx500m -Dalfresco.host=localhost -Dalfresco.port=8080 -Dalfresco.context=alfresco -Dalfresco.protocol=http " solr6: image: alfresco/alfresco-search-services:1.4.2.1 mem_limit: 4g environment: #JAVA_OPTS: "-Dsolr.log.level=FINE" #Solr needs to know how to register itself with Alfresco - SOLR_ALFRESCO_HOST=alfresco - SOLR_ALFRESCO_PORT=8080 #Alfresco needs to know how to call solr - SOLR_SOLR_HOST=solr6 - SOLR_SOLR_PORT=8983 #Create the default alfresco and archive cores - SOLR_CREATE_ALFRESCO_DEFAULTS=alfresco,archive #HTTP by default - ALFRESCO_SECURE_COMMS=none ```
https://nu.federati.net/notice/3327468
musicman's status on Wednesday, 05-Aug-2020 20:11:28 UTCbelow is a section of a #<span class="tag"><a href="https://nu.federati.net/tag/docker" rel="tag">docker</a></span> compose file. Why is it that under environment in share you have different sections such as JAVA_OPTS, but under solr6 the configs just have a - in front of them. I tried adding JAVA_OPTS to solr6 and got a yml syntax error<br /><br /> ```<br /> share:<br /> image: alfresco/alfresco-share:6.2.0<br /> mem_limit: 1g<br /> environment:<br /> REPO_HOST: "alfresco"<br /> REPO_PORT: "8080"<br /> JAVA_OPTS: "<br /> -Xms500m<br /> -Xmx500m<br /> -Dalfresco.host=localhost<br /> -Dalfresco.port=8080<br /> -Dalfresco.context=alfresco<br /> -Dalfresco.protocol=http<br /> "<br /><br /> solr6:<br /> image: alfresco/alfresco-search-services:1.4.2.1<br /> mem_limit: 4g<br /> environment:<br /> #<span class="tag"><a href="https://nu.federati.net/tag/javaopts" rel="tag">JAVA_OPTS</a></span>: "-Dsolr.log.level=FINE"<br /> #<span class="tag"><a href="https://nu.federati.net/tag/solr" rel="tag">Solr</a></span> needs to know how to register itself with Alfresco<br /> - SOLR_ALFRESCO_HOST=alfresco<br /> - SOLR_ALFRESCO_PORT=8080<br /> #<span class="tag"><a href="https://nu.federati.net/tag/alfresco" rel="tag">Alfresco</a></span> needs to know how to call solr<br /> - SOLR_SOLR_HOST=solr6<br /> - SOLR_SOLR_PORT=8983<br /> #<span class="tag"><a href="https://nu.federati.net/tag/create" rel="tag">Create</a></span> the default alfresco and archive cores<br /> - SOLR_CREATE_ALFRESCO_DEFAULTS=alfresco,archive<br /> #<span class="tag"><a href="https://nu.federati.net/tag/http" rel="tag">HTTP</a></span> by default<br /> - ALFRESCO_SECURE_COMMS=none<br /> ```2020-08-05T20:11:28+00:00Douglas A. Whitfieldlnxw48a1: On search: I really want to host another #YaCy node, but YaCy's results are still not great. Even when my node was crawling & indexing sites in a particular field (at the time, FOSS SQL and NOSQL databases) weekly, searches for things in that field were infested with non-related results such that finding the desired answer was unreliable. . YaCy integrates #Solr ... so its results should be improvable.
https://nu.federati.net/notice/3324776
lnxw48a1's status on Monday, 20-Jul-2020 18:35:22 UTCOn search: I really want to host another #<span class="tag"><a href="https://nu.federati.net/tag/yacy" rel="tag">YaCy</a></span> node, but YaCy's results are still not great. Even when my node was crawling & indexing sites in a particular field (at the time, FOSS SQL and NOSQL databases) weekly, searches for things in that field were infested with non-related results such that finding the desired answer was unreliable.<br /> . <br /> YaCy integrates #<span class="tag"><a href="https://nu.federati.net/tag/solr" rel="tag">Solr</a></span> ... so its results should be improvable.2020-07-20T18:35:22+00:00LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}lnxw48a1: @musicman I only indirectly encountered #Solr when I ran a #YaCy instance, so I have no opinion about Solr 6.
https://nu.federati.net/notice/3323729
lnxw48a1's status on Tuesday, 14-Jul-2020 19:58:52 UTC@<a href="https://nu.federati.net/user/12" class="h-card u-url p-nickname mention" title="Douglas A. Whitfield">musicman</a> I only indirectly encountered #<span class="tag"><a href="https://nu.federati.net/tag/solr" rel="tag">Solr</a></span> when I ran a #<span class="tag"><a href="https://nu.federati.net/tag/yacy" rel="tag">YaCy</a></span> instance, so I have no opinion about Solr 6.2020-07-14T19:58:52+00:00LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}musicman: How do people feel about #Solr 6? That's what #Alfresco uses. Latest Solr is 8.5.2
https://nu.federati.net/notice/3323725
musicman's status on Tuesday, 14-Jul-2020 19:39:57 UTCHow do people feel about #<span class="tag"><a href="https://nu.federati.net/tag/solr" rel="tag">Solr</a></span> 6? That's what #<span class="tag"><a href="https://nu.federati.net/tag/alfresco" rel="tag">Alfresco</a></span> uses. Latest Solr is 8.5.22020-07-14T19:39:57+00:00Douglas A. Whitfieldlnxw48a1: @musicman Good. I think the current implementation of the #YaCy search engine relies on #Solr.
https://nu.federati.net/notice/3278450
lnxw48a1's status on Tuesday, 25-Feb-2020 17:45:15 UTC@<a href="https://nu.federati.net/user/12" class="h-card u-url p-nickname mention" title="Douglas A. Whitfield">musicman</a> Good. I think the current implementation of the #<span class="tag"><a href="https://nu.federati.net/tag/yacy" rel="tag">YaCy</a></span> search engine relies on #<span class="tag"><a href="https://nu.federati.net/tag/solr" rel="tag">Solr.</a></span>2020-02-25T17:45:15+00:00LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}lnxw48a1LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}musicmanDouglas A. Whitfield