Show Navigation
Notices tagged with alfresco
-
wouldn't be my choice, but #Alfresco was unusable (I wonder if the new owners are going to fix it) and #OpenKM got the nix (and needs a UI refresh anyway)
-
@musicman As far as #Alfresco vs { #Drupal + extensions } vs #OpenKM, I think part of it is the level of work involved in making a web-based document store ... after doing so much work, they really want to put "the good stuff" into a paid offering and leave raw pieces for those who won't pay.
-
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)
-
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
```
-
I am giving up on #Alfresco for the time being to see if there is something else we support.
Once we get a process for taking things off the supported list, Alfresco should be the first one to go.
-
That machine was not on a UPS, so my time of experimenting with #Alfresco ended when a power outage followed by a power surge damaged the disk
-
Back in the olden days of 2006 / 2007, it was easy. Install #Tomcat. Stop Tomcat (so it isn't running). Grab the #Alfresco .WAR file and drop it into the proper directory within Tomcat. Start Tomcat. Once it has extracted the WAR file, stop Tomcat again and edit some configs (for example, enter database info, enable or disable various services and functionality). Start it again.
Depending on what gets enabled, there could be other shutdowns and restarts and config editing needed.
-
the #tomcat web manager doesn't look nearly as slick as #wildfly, but I am glad I got it working finally...and it looks like it picked up my app, so yay for that. The instructions from #Alfresco leave something to be desired.
-
Speaking of #Alfresco, do they still have the document converter function? Back in the day, they used a #OpenOffice library as a background process. It could convert to and from any file formats that OO supported.
-
The #Alfresco manual install has the same issue that the docker containers do...maybe more so. The package downloads are not getting any updates. At least with the containers you can easily replace the container (not that it is guaranteed to work, but it did with the search services I tried yesterday)
-
I missed the standup today, but it might have been mentioned there. We don't do any hosting, so we just wait for people to ask...usually. It's possible we would reach out to customers we know would have this.
I only vaguely watch the queue at this point.
I don't see a lot of Tomcat tickets, but there is one from yesterday. It doesn't *seem* related, but I can't say for sure without digging in, which is probably not going to happen.
I should check to see what version of Tomcat #Alfresco is using, but Alfresco isn't public facing, so I'm not that worried about it. And right now, there's not really any data to worry about losing.
-
How do people feel about #Solr 6? That's what #Alfresco uses. Latest Solr is 8.5.2
-
sure, but what if your user search page is broken? https://docs.alfresco.com/6.0/tasks/admintools-user-delete.html #alfresco
-
back on the #Alfresco train...which might be the #docker train. something weird was happening, so I blew it all away. We will see if the new stuff has the same issue.
-
one thing I like about zsh is timestamps. idk how long it is taking to pull down this #alfresco docker image, but it is not fast
-
@musicman I ran #Alfresco at home over a decade ago. It was way more than I needed (and I don't think they were competing with #SharePoint yet ). A HDD crash while I was out of state ended that.
Good to see they're still around.