Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Sounds like a good idea!
Even there is Domino on Docker, which allows a quite seamless update.
Having a product that can update itself would be very convenient.
There are some challenges to solve specially on Linux/AIX, because Domino is using as a normal user acocunt and not root.
The installation will still need some down time. Unless you:
- copy the existing binary directory
- apply the update to the copy
- shutdown Domino
- swap the binaries
-start
- This might be too complex. How long would a downtime be? Would be 2-4 minutes OK
- What about roll-back if it did not work?
- So maybe the cloned binary directory might be a good idea for both?
Daniel Nashed (https://blog.nashcom.de)
So this would need an Upgrade Task, and a Database with Content. This should require authorisation to do, and should restart the server afterwards as well.
It should be an additional option, NOT replace the current installer.
-Rudi