add option to make convertConfig easier in most cases
When setting up a new LLNG instance, users would typically
- edit lemonldap-ng.ini to change their config backend
- discover that convertConfig needs the original lemonldap-ng.ini
- copy lemonldap-ng.ini to oldlemonldap-ng.ini and revert it to the file storage
- run convertConfig, possibly mixing up --current and --new because --current is supposed to be the oldlemonldap-ng.init
Long story short, this whole process is needlessly complicated and error prone.
Not all users change configuration backend once they have migrated to DB/LDAP, but ALL users have to go to the process of converting their config when setting up LLNG for the first time.
When started without any arguments, convertConfig could convert the default conf storage (/var/lib/lemonldap-ng/conf) to what is currently in lemonldap-ng.ini. User would be prompted for confirmation to avoid accidental use.
Or perhaps add a new option to explicitely trigger this same behavior:
Or simply a flag to select the default conf backend:
convertConfig --from-default --new /etc/lemonldap-ng/lemonldap-ng.ini
The same could be done with convertSessions too