Daily Log for #alfresco IRC Channel

Alfresco discussion and collaboration. Stick around a few hours after asking a question.

Official support for Enterprise subscribers: support.alfresco.com.

Joining the Channel:

Join in the conversation by getting an IRC client and connecting to #alfresco at Freenode. Our you can use the IRC web chat.

More information about the channel is in the wiki.

Getting Help

More help is available in this list of resources.

Daily Log for #alfresco

2019-10-21 09:01:23 GMT <AFaust> ~later tell angelborroy: Any chance you can get the team to ensure ASS on GitHub is buildable? I.e. all the dependencies (including the Alfresco-patched ones) are in accessible artifact repositories?

2019-10-21 09:01:23 GMT <alfbot> AFaust: The operation succeeded.

2019-10-21 09:50:19 GMT <alfresco-discord> <yreg> Morning guys

2019-10-21 09:50:59 GMT <alfresco-discord> <yreg> interesting news I read this morning, Alfresco seems to have acquired Pernexas : https://www.alfresco.com/news/press-releases/alfresco-acquires-integration-specialist-pernexas

2019-10-21 09:51:00 GMT <alfbot> Title:Alfresco acquires Pernexas (at www.alfresco.com)

2019-10-21 09:57:21 GMT <AFaust> What the heck....

2019-10-21 10:12:27 GMT <AFaust> ~later tell angelborroy: It looks like the pre-emptive deletion of any existing index documents (both ERROR and actual node documents) when an updated / new node is indexed is causing the significant slow down / index commit overhead I am observing. For every node added to the index, the commit phase must execute two queries to find those index documents to delete, which costs a low of time in calculating query weights.

2019-10-21 10:12:27 GMT <alfbot> AFaust: The operation succeeded.

2019-10-21 10:15:10 GMT <AFaust> ~later tell: The more nodes that have already been indexed, the more significant this overhead becomes. Currently at 20 million nodes indexed, and "time remaining" has climbed to 16 days compared to 6 days on Friday. Taking just the performance of the last two hours, it should have already climbed to 18 days, but I guess the SOLR calculated value considers longer time frames for averages.

2019-10-21 10:15:10 GMT <alfbot> AFaust: Error: The "Later" plugin is loaded, but there is no command named "tell:" in it. Try "list Later" to see the commands in the "Later" plugin.

2019-10-21 10:15:16 GMT <AFaust> ~later tell angelborroy: The more nodes that have already been indexed, the more significant this overhead becomes. Currently at 20 million nodes indexed, and "time remaining" has climbed to 16 days compared to 6 days on Friday. Taking just the performance of the last two hours, it should have already climbed to 18 days, but I guess the SOLR calculated value considers longer time frames for averages.

2019-10-21 10:15:16 GMT <alfbot> AFaust: The operation succeeded.

2019-10-21 10:58:27 GMT <alfresco-discord> <mbui> I have this requirement from a customer where they would like to be able to use RSS-feeds (from various sites document library) for display on other places (Info screens etc) without requiring authentication. That sounds like a big security flaw, opening up those webscripts for the public, i.e. anyone could access any data in the repository. Anyone have ideas on how to tackle this? 馃檪

2019-10-21 11:35:13 GMT <AFaust> mbui: I definitely would not expose anything without authentication.

2019-10-21 11:37:47 GMT <AFaust> The only way I could be convinced to do this is by defining a separate, technical user account which is transparently authenticated via HTTP headers (e.g. set in Apache / nginx), but only when those requests are being submitted from a defined / trusted client, e.g. relayed by a portal software which I could identify via IP (in an internal network) or client certificate.

2019-10-21 11:38:24 GMT <AFaust> And that separate user account would require explicit membership / access grants in Alfresco sites, so people would have control over what is visible in those RSS feeds.

2019-10-21 11:39:33 GMT <AFaust> I also would tightly control the scope of RSS URLs which would allow this kind of scheme, so it cannot be used to call some other services (non RSS-feed URLs) to get more data than it should.

2019-10-21 11:40:56 GMT <AFaust> E.g. in one customer system I actually have something like this. A WordPress system includes links to files in Alfresco for download / in-line rendering, and most of the users are only authenticated in WordPress without a matching user account in Alfresco.

2019-10-21 11:43:33 GMT <AFaust> The Apache proxy contains a specific URL rewrite which allows for some relative URLs to be resolved against a defined folder path in Alfresco. Additionally, WordPress sets a secure cookie (user name + logged in timestamp + crypto-hash) which a custom RemoteUserMapper in Alfresco validates and uses to set the authenticated user to the technical account

2019-10-21 11:51:32 GMT <alfbot> hi-ko: Sent 2 days, 19 hours, and 48 minutes ago: <AFaust> Ehm, typically only less and my mk-1 eye balls

2019-10-21 11:51:33 GMT <alfbot> hi-ko: Sent 2 days, 19 hours, and 39 minutes ago: <AFaust> From all the jstack traces so far, I never see any thread stuck or otherwise active in IO. It all looks to be CPU bound, e.g. the computational cost of doing index merges. Since that is exclusive, everything else blocks on that, when that occurs. I am currently trying to see how solrconfig.xml params (buffer/mergeFactor) impact this.

2019-10-21 12:12:43 GMT <alfresco-discord> <mbui> AFaust: Thanks for the detailed explanation, i'll look into this.

2019-10-21 15:44:12 GMT <alfresco-discord> <jpotts> In the Alfresco Content App, how do metadata properties get mapped to the components used to render them? By default, multi-value props are just comma-separated lists. Instead I want to render a drop-down with my own labels and some client-side validation.

2019-10-21 15:44:57 GMT <alfresco-discord> <jpotts> I'm looking at the docs for the content metadata card component. They are not helpful.

2019-10-21 15:45:59 GMT <alfresco-discord> <jpotts> I guess my next resource will be the ADF source for that component

2019-10-21 16:16:00 GMT <AFaust> jpotts: Since neither ADF nor ACA make use of any dictionary lookups (there is no capability for this in Public v1 ReST API), I doubt there can be any automatic mapping and everything must be specified explicitly somewhere (assume app.config.js)

2019-10-21 16:16:08 GMT <AFaust> app.config.json I mean

2019-10-21 16:20:00 GMT <AFaust> As far as I can see, the default distinction between various display renderings should be handled by the card-view-item-dispatcher (https://github.com/Alfresco/alfresco-ng2-components/blob/development/lib/core/card-view/components/card-view-item-dispatcher/card-view-item-dispatcher.component.ts)

2019-10-21 16:20:01 GMT <alfbot> Title:alfresco-ng2-components/card-view-item-dispatcher.component.ts at development 路 Alfresco/alfresco-ng2-components 路 GitHub (at github.com)

2019-10-21 16:22:07 GMT <AFaust> Some kind of type mapping is done in the card-item-types service (https://github.com/Alfresco/alfresco-ng2-components/blob/development/lib/core/card-view/services/card-item-types.service.ts)

2019-10-21 16:22:08 GMT <alfbot> Title:alfresco-ng2-components/card-item-types.service.ts at development 路 Alfresco/alfresco-ng2-components 路 GitHub (at github.com)

2019-10-21 16:26:44 GMT <AFaust> https://github.com/Alfresco/alfresco-ng2-components/blob/cd7e21a23dae9ea0ccd14a0d5c53ab24501c9665/docs/core/services/form-rendering.service.md should document everything, if I am not mistaken

2019-10-21 16:26:45 GMT <alfbot> Title:alfresco-ng2-components/form-rendering.service.md at cd7e21a23dae9ea0ccd14a0d5c53ab24501c9665 路 Alfresco/alfresco-ng2-components 路 GitHub (at github.com)

2019-10-21 16:27:49 GMT <AFaust> Though that is only for forms - there is a different one for card-view: https://github.com/Alfresco/alfresco-ng2-components/blob/cd7e21a23dae9ea0ccd14a0d5c53ab24501c9665/docs/core/services/card-item-types.service.md

2019-10-21 16:27:50 GMT <alfbot> Title:alfresco-ng2-components/card-item-types.service.md at cd7e21a23dae9ea0ccd14a0d5c53ab24501c9665 路 Alfresco/alfresco-ng2-components 路 GitHub (at github.com)

2019-10-21 16:28:37 GMT <AFaust> I am still unclear where the "type" string is supposed to originate...

2019-10-21 16:32:09 GMT <AFaust> If it is supposed to be a config in app.config.json or app.extensions.json, it is not documented or any examples provided.

2019-10-21 17:18:43 GMT <alfresco-discord> <dgradecak> just be careful with the extensions, as far as I know it is being "refactored", maybe it is already done. But I think it is going to be different than what it is today

2019-10-21 17:21:50 GMT <alfresco-discord> <dgradecak> on a couple of apps, I stoped using ADF at all, since I spent too much time trying things and finding out how it should work instead of doing things. But I guess I will give it a try again soon (maybe with more luck this time). I find it too "opinionated" but there might be some components that are ok. Currently I always use "angular material" + alfresco JS API

2019-10-21 17:22:17 GMT <alfresco-discord> <dgradecak> getting the job done much faster than trying to "cusotmize" ADF 馃槮

2019-10-21 17:34:53 GMT <alfresco-discord> <jpotts> Yes, I feel the same way @dgradecak. I find it highly unlikely that any of my customers would be able to determine how to customize/extend every aspect of the ACA/ADW and/or maintain my customizations/extensions of the same.

2019-10-21 17:35:42 GMT <alfresco-discord> <jpotts> We gained by having a client based on a widely-adopted development framework. But, at least for now, we've lost by having insufficient documentation and extension points.

2019-10-21 17:37:45 GMT <alfresco-discord> <jpotts> I think my recommendation to clients is going to be to use ACA/ADW only if you like it as-is or with the most minimal of tweaks. Otherwise, stick with Share or build your own.

2019-10-21 17:39:01 GMT <alfresco-discord> <dgradecak> latey a client wanted to use ADW but needed a "folder template", however this exists in share but not in ACA/ADW

2019-10-21 17:39:31 GMT <alfresco-discord> <dgradecak> building it it would take me quite a lot of effort and while they moved to 6.1 they stick with share too

2019-10-21 17:40:15 GMT <alfresco-discord> <dgradecak> such a "simple" feature would take me quite a lot of time to be done based on the extensions in ADF

2019-10-21 17:40:56 GMT <alfresco-discord> <dgradecak> and like I said, they told me (ADF team) not to do "extension" work since it is being changed, but I did not ask for the status for a 2-3 months

2019-10-21 17:44:31 GMT <alfresco-discord> <jpotts> I sent support a list of customizations that are relatively simple when done in Share and asked them, "How do you do these in ACA/ADW?". Their initial response was that's "developer support" or professional services, but they say they are going to do their best. We'll see what they come back with.

2019-10-21 17:44:52 GMT <alfresco-discord> <jpotts> It's frustrating that this so-called framework is so poorly documented or hard to customize that even support might not be able to help big-name customers figure out how to do simple customizations.

2019-10-21 17:45:43 GMT <alfresco-discord> <dgradecak> framwork is a big word, I call it "library"

2019-10-21 17:45:59 GMT <alfresco-discord> <jpotts> "Framework" is literally in the name 馃檪

2019-10-21 17:46:07 GMT <alfresco-discord> <dgradecak> but let us know here please about your support request once oyu get a response

2019-10-21 17:46:21 GMT <alfresco-discord> <jpotts> Will do!

2019-10-21 17:52:25 GMT <AFaust> jpotts: Yeah, "Framework" is literally in the name, just like "climate protection" is literally in the name of some of our laws / set of policies that will do anything but...

2019-10-21 17:55:06 GMT <AFaust> I think around the time that ADF got started, product / project names started to become more and more marketing driven, rather than a proper description of what they are...

2019-10-21 17:55:50 GMT <AFaust> I am still waiting on public communication about ASS to change to some new acronym I heard Alfresco internally communicated should be used in all future mentions...

2019-10-21 18:10:16 GMT <alfresco-discord> <jpotts> I name all of my SDK 4.0.0 projects "jpotts-kicks" so that when I start up my containers it says "jpotts-kicks-ass_1" in the log

2019-10-21 18:11:30 GMT <AFaust> nice one

2019-10-21 18:11:43 GMT <alfresco-discord> <jpotts> 馃榿

2019-10-21 18:11:56 GMT <AFaust> Any you can always rename the project later one when the customer won't pay...

2019-10-21 18:12:10 GMT <AFaust> "later on" I mean

2019-10-21 18:12:45 GMT <AFaust> acme-sux....

2019-10-21 18:13:10 GMT <AFaust> Man - my typos are all over the place today. Just noticed the "Any" <=> "And" one...

2019-10-21 18:13:28 GMT <AFaust> Though the project name was a deliberate one

End of Daily Log

The other logs are at http://esplins.org/hash_alfresco