Hi! Thanks for all the great work so far. I wanted to make a request for a basic UI based backup system. Where you could pull the configuration onto the workstation/desktop you are accessing Komodo's web UI from. The current Komodo CLI based backup system is a little cumbersome, and frankly, a bit poorly documented in my opinion. It's not exactly clear to me whether you should deploy the Komodo CLI container from the remote backup machine (like a NAS) or add the container in the Komodo Core stack where the server is deployed, and then mount a network share.
A simple UI based backup system would negate some of that headache and most only need a backup at incremental stages of using Komodo.
Originally created by @epoch-philosophy on GitHub (Aug 24, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/763
Hi! Thanks for all the great work so far. I wanted to make a request for a basic UI based backup system. Where you could pull the configuration onto the workstation/desktop you are accessing Komodo's web UI from. The current Komodo CLI based backup system is a little cumbersome, and frankly, a bit poorly documented in my opinion. It's not exactly clear to me whether you *should* deploy the Komodo CLI container from the remote backup machine (like a NAS) or add the container in the Komodo Core stack where the server is deployed, and then mount a network share.
A simple UI based backup system would negate some of that headache and most only need a backup at incremental stages of using Komodo.
If you create the Backup Core Database Procedure, you can run that from the UI. Its created automatically for new installs, but not for existing ones, so you just have to create it.
<!-- gh-comment-id:3239002988 -->
@mbecker20 commented on GitHub (Aug 30, 2025):
If you create the Backup Core Database Procedure, you can run that from the UI. Its created automatically for new installs, but not for existing ones, so you just have to create it.
1. Create new Procedure "Backup Core Database"
2. Set "Backup Core Database" as Stage 1, and Save
3. (Optional.) define a schedule for the task.
More info: https://komo.do/docs/setup/backup
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @epoch-philosophy on GitHub (Aug 24, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/763
Hi! Thanks for all the great work so far. I wanted to make a request for a basic UI based backup system. Where you could pull the configuration onto the workstation/desktop you are accessing Komodo's web UI from. The current Komodo CLI based backup system is a little cumbersome, and frankly, a bit poorly documented in my opinion. It's not exactly clear to me whether you should deploy the Komodo CLI container from the remote backup machine (like a NAS) or add the container in the Komodo Core stack where the server is deployed, and then mount a network share.
A simple UI based backup system would negate some of that headache and most only need a backup at incremental stages of using Komodo.
@mbecker20 commented on GitHub (Aug 30, 2025):
If you create the Backup Core Database Procedure, you can run that from the UI. Its created automatically for new installs, but not for existing ones, so you just have to create it.
More info: https://komo.do/docs/setup/backup