Support Debian 11 #17
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
🎉 Debian 11 was recently released 🎉
Adding support for it to Web-V2 (and required modules)
List of submodules
1 - Repository availability
2 - Testing
Checking if packages form repo are all available - Validated
Checking if configs needs updating - Existing configs worked
Checking wich scripts need to be updated- Done
3 - Updating
Add modifications of Testing phase - Done
Vaidate if if no new bugs where created with this update - Done
Added disto flag for debian 11 and updated if statements - Done
Updated way of adding repo keys (See
Generalrepo) - Done4 - Test updating on existing Web-V2 server
Check on test server wich changes need to be made
Make script to update for existing machines
Tested
General
├── AddCMS.sh
├── AddModule.sh
├── Install.sh
├── Unattended-Security-Updates
├── MariaDB
├── MySQL
├── PhpMyAdmin
├── Redis
├── Postfix
├── Backup-Util
└── Repo's
Nginx
├── CMS
│ ├── None
│ ├── WordPress
│ ├── NextCloud
│ └── FrontController
└── Modules
└── !AcmeSH
Apache
├── CMS
│ ├── None
│ ├── WordPress
│ └── NextCloud
└── Modules
└── AcmeSH
Notes
For testing using temporary MariaDB module instad of MySQL since this is not yet avalible on Debian 11AcmeSH for Ngix has a upstream bug (See https://git.ictmaatwerk.com/VPS-scripts/AcmeSH/issues/1)-Fixed upstreamMySQL repo is now available for Debain 11 (Bullseye), mirror.nxdi.nl has also been set up for this.
Extenal MySQL module has been updated, and tested
MariaDB Module is disabled and Achived/Deprecated
Week 36 target for merge
Debain11Testingtomaster, after testing and validatingEverything was validated, merged to
masterbranchFeel free to reopen if there are problems with the Debian 11 implementation
Upgrade script for existing Debian 10 Web-V2 Systems
The script will first upgrade the current release, then it wil ask you to reboot the system.
When the system is rebooted re-run the script to upgrade to the new release, when this completed the script wil wil ask you to reboot the system
Tested
Two ways of running the Script
The normal way
The safe way (Recomended when using SSH session)
!WARNING: The scipt will just run, and not wait for confirmation