This is a brand new script, which is the logical extension to the Nash!Com Domino Start script. A while ago I introduced Docker support for the start script inside the Domino container. It comes with an entry-point script we are also leveraging in out Domino Docker Github community script. This new script is intended to manage and run your Docker and Podman containers. It includes also a systemd script to run a Domino server on Podman in production using the new systemd options introduced in Podman 1.7+. Beside that it includes a simple framework to build and manage your own add-on images

Now that we have the Sametime Premium Meeting Server, there are more customers looking into Domino on Linux. In earlier days I had some issues getting the start script in combination with SLES working. So ST wasn't never on my support list.

Whenever I have a great deal of discretion over how a web app is made these days, I like to push to see how simple I can make the front end portion. I spend some of my client time writing heavy client-JS front ends in React and Angular and what-have-you, and, though I get why they are good, I kind of hate them all.

This post is a drum I've been banging for a long time, from nagging the dev team in the IBM days through to formally requesting it in HCL's Ideas Portal. That idea there has been "Likely to implement" for a little while now, which is heartening, and either way I figured it'd be useful to have a proper blog post explaining the trouble and what a useful better version would be.

There are a number of challenges when it comes to two-way REST and Domino. But one of the biggest challenges for manipulation between NotesDateTime objects and JSON is timezone handling.

When you create mail journaling you can encrypt all documents using the Administrator ID. Last week a customer ask to add access for another user (developer). The Admin remove the database encryption but lots off documents remain encrypted . The solution was to remove the document encryption using the following steps: