This command could not be more official.
Though, full support for “Micro” and “Nano” stacks will be completed later today.
I just need to fix the Virtualmin installation script and update the YUM groups. The rest is ready.
This command could not be more official.
Though, full support for “Micro” and “Nano” stacks will be completed later today.
I just need to fix the Virtualmin installation script and update the YUM groups. The rest is ready.
no, i mean the general command i was using. Thank you for working on Sunday to fix this.
sudo sh -c "$(curl -fsSL https://software.virtualmin.com/gpl/scripts/virtualmin-install.sh)" -- --bundle LEMP -m
Depends on how long you are willing to wait for the next ‘official’ release of Virtualmin? You aren’t really going ‘off script’ here. If you do what @Ilia suggests you don’t get anything weird that might bite you in the future. You aren’t really tinkering with the sub systems.
i don’t think the installer is related to official release. it install the latest release as it is, the issue is in the installer and not the virtualmin itself.
hi @Ilia, is it still pending to be published? fix minimal installation proftpd postfix · Issue #4 · virtualmin/virtualmin-lamp-stack-ubu · GitHub
It will be released whenever Joe decides to make it available. For now, you can use the prerelease repositories to give it a try if you wish. It’s described in here.
@Joe is there any eta? i know i can use the prerelease but i still wish to use the live version.
See
thanks, i understand the delay and it’s okay. i was not aware that it would get this much delayed. i was avoiding using the prelrease and waited a month because i am not an expert and afraid to break things. i will not ask for it anymore.
There is nothing wrong with using prerelease repos. They are currently the same as the production ones.
I wouldn’t recommend the pre-release repos because they will diverge in the future.
OP should just do what I’ve already said to do. This is not a dramatic situation that requires dramatic solutions. There are at least a couple of ways to solve it that are not dramatic nor will they impact you in the future. These ways are fine, there is no reason to wait on anything. (Preinstall proftpd
or run the config-system
step to explicitly exclude ProFTPd
).
Using pre-release repos does have long-term consequences and will work fine, and if someone is nervous about doing the things that don’t have long-term consequences, why recommend something that will have long-term consequences?
I think the better solution is to undo the change to dependencies and put ProFTPd back. It’s a bug to alter the stack in incompatible ways during a major version release cycle. Removing ProFTPd is a big change that will surprise a lot of people.
If you want to remove ProFTPd from the minimal
stack, it needs to happen during a major release (e.g. with Virtualmin 8), and it needs to be documented.
Yeah, agreed! Fixed now!
is it okay if i install full stack and then uncheck the features not needed in “features and plugins section” ? unchecking will remove those packages?
No, unchecking merely disables the feature in Virtualmin. It does not remove or install packages.
Start a new topic if you have follow ups about installing or uninstalling packages or working with features.