- HCL Connections Newsletter v2 and Join Community requests
- Show Community Create Button only to users with role "community-creator"
- Makefile to process all Asciidoctor files in a directory
- Update on the Touchpoint workaround
- Linkdump Week 44 / 2020
- Linkdump Week 42 / 2020
- Linkdump Week 41 / 2020
- Elasticsearch index creation problem
- Linkdump Week 40 / 2020
- Selfhost Shaarli
Since IBM Connections 6.0CR4 we can use a new newsletter format which needs still (now with HCL Connections 7) be activated separately in LotusConnections-config/notification-config.xml. Today some users asked how they can add other users to their private communities (visible in Community catalog) without manually adding them. As we investigated the question I had a look at the old notification format. So there a community owner got following e-mail when a user requested to join: So he could directly add the requesting user to the community. Now we switched to the new v2 format and the mail looks like this:
Since the update to the new HCL Connections Community Card-Based Overview (Connections 6.0 CR4) I search for a way to hide the button "Create Community" from users without the role "Community-Creator". This was always possible in the earlier versions of Connections, but the button was shown always since the update. During the year I mostly forgot about it, but yesterday I opened a case with HCL Connections Support and got immediatly following answer: There is a new gatekeeper flag, CATALOG_CARD_UPDATED, which was introduced in IC6.0CR5 to help enhance the community card based view. This will need to be set to false to address this issue.
I write most of my documents (blog posts, documentation, recipes and so on) with Asciidoctor. Everything is organized in Git repositories. During GPN 19 (Gulaschprogrammiernacht) I showed how to build html and pdf with a Gitlab CI/CD pipeline. That’s quite handy, but lots of documents I build, I just need locally. So today I played with WSL2 and a Makefile to build all Asciidoctor files in a directory. Commandline to make pdf asciidoctor-pdf source.adoc -o build/source.pdf This builds a pdf in the directory build, but how can we create a pdf of some files? Makefile docs = $(wildcard *.
Last week I didn’t find very useful links to read or articles to share. This week I read more books, so a recommendation for a book this week and two articles with awk basics. The Kubernetes Workshop Still preparing for CKA, so I read a lot around Kubernetes. This book is brand new and the first chapters are already useful. I think it’s more detailled than the books I read about Kubernetes before. Bug Bytes #94 - Breaking Symfony apps Again a great collection of things worth reading all around bug bounty and pentesting.