The Future of NextBox
We want to and will continue to maintain the support and current status of the software in the future. Nextcloud, which has proven to be extremely robust in recent months and years, makes an irreplaceable contribution to this.
For those who follow the NextBox GitHub repository, there are currently many exciting developments. In this article, we would like to discuss some of the important new features and our plans for the future.
NextBox System Update
The test phase for the update to Debian 11 ("Bullseye") will begin shortly. We are inviting all interested parties to participate. Do not hesitate to share your experiences with us. Please note, however, that this is a test phase. Make sure to create backups before starting the NextBox system update and make sure that temporary NextBox failures do not cause major problems! In case of problems, a previously set up SSH access can help you. To participate, simply go to the system settings of the NextBox app and follow the instructions under "NextBox System Update". We expect to complete the test phase in June at the latest, so that the update will then be mandatory and automated for everyone. Shortly after that we are already planning the next update of Debian to version 12 ("Bookworm").
New Backup/Restore App
We currently use a system for backup/restore that we developed ourselves. We are currently looking into the possibility of switching to the backup/restore system of the official Nextcloud app "Backup". The official backup app offers a number of advantages:
- Automated backups in individually adjustable time windows
- Full and incremental backups
- Encrypted backups with the option of storing them externally
If our tests are successful and no problems occur, we will switch off the old backup/restore function in the medium term and switch completely to the functionality provided by Nextcloud. Of course, we will ensure a long transition period and inform you about this in a future blog post.
Feel free to write us your ideas for improvements here in the comments or via GitHub Issues.
Comments
Add new comment