Roundcube last version with autoinstaller

I'm wondering if the Perfect Server Automated ISPConfig 3 Installation will install the Latest RoundCube Webmail like in picture or just it pulls the old version from the repo, if so, should I then skip the RoundCube installation using --no-roundcube and install it manually ( on Nginx )



I want also to customize the subdomain alias to https://mail.site.com instead of https://site.com/webmail

Thank you !

 

Roundcube version from roundcube.net website is 1.6.5.
Roundcube from Debian 12 Bookworm repository is 1.6.5.
Roundcube from Ubuntu 22.04 repository is 1.5.0, so better use Debian if must have latest version.
On the other hand, installing roundcube from somewhere else or compiling it yourself means you must verify it works correctly. When updates come to roundcube, you must repeat the installation or compiling to get the update.
Using distro repository is easier, the maintainer knows how to compile and set up the application so it works as intended, and updates are installed automatically.

 

OK, Got it, thank you !

 

Isn't there a way to hard-link or symlink to the roundcube that was installed/apt-updated already?
Similarly, if I want to have mail.x.tld, mail.y.tld and mail.z.tld all point to the same roundcube dir (while not being domain aliases), isn't that way more efficient than having to copy all of roundcube's files into each new site's folder?

I remember having done this before a decade ago using a separate squirrelmail dir and giving it a separate nginx vhost conf file, but I'd rather have *all* config controlled by ISPconfig and not -again- have all those extra workaround/special case configs that bypass or skip ispconfig on the same server..

 

OK, I did install ispconfig on debian including roundcube. I see it already created a database entry for it in mysql. So, when I install roundcube into some site (webmail.site.tld) for all users, do I then use ispconfig's db config for it, or do I have to install it anew, as a totally separate roundcube? I'm just a little confused as to the existing roundcube under port 8081 or something being some kind of stale entity no user ever goes to. Webmail installs like that tend to become forgotten, and then perhaps excluded from login failure monitoring with all the possible consequences of it being a security hole.

 

How is there no way to use this ISPconfig installation of roundcube under additional domain names (alias domains) or different ports? This sounds really strange to me. Looks to me like I could even create a vhost conf file in nginx that points to the 8081 roundcube install, and then have it listen to a bunch of domain name aliases, so they all can use the ISPconfig roundcube install. I'll try and see how it goes.

 

I think you misunderstand me; I *prefer* to use the central installation that is already there, for which you claim ALL users can access, but I want it to be reachable under all domain names (like webmail.x.tld, mail.y.tld etc.) which should not be too hard. Now the 'central' roundcube is only available under https://ispcdomain:8081/webmail and you wrote that it can't be made accessible under other names. Again, I can reverse proxy ANY hostname to it in nginx. Why not?
That way I do not have to create an extra database, the roundcube is version-maintained by apt and ispconfig, and there are no security issues whatsoever.