Posts by sutorinfo

OK, I understand, please excuse some sort of activism from my side!

My understanding of this plugin first was:
Giving the reseller the possibility to edit the (virtual) default page for new customers, in analogy to the customisation of the welcome email. Some sort of reseller owned template.

Concerning the (server) default page:
My intention was, to obtain as few information about installed systems and software as possible (though obscurity is no concept). Well, some thoughts on existing wheels, as you mentioned.

I successfully installed i-mscp 1.3.0.
The FQDN of the server is mysub01.mydoami.top.
When calling http://mysub01.mydoami.top I get the debian/apache server default page with following advice:

Quote from debian

You should replace this file (located at /var/www/html/index.html) before continuing to operate your HTTP server.

Did so with

Calling again http://mysub01.mydoami.top I get a directory listing.

I would prefer this off (Options -Indexes).
As new index.html s. th. like

This issue was seen also in previous versions:

Dedicated server with installed OS from a template (here: debian jessie). As a parameter for the installation I could enter my own hostname (mysub01.mytop.tl). The server got also its own hostname (theirsub123.ispname.tl) which remains as an alias.

When it comes to the suggestion for the panel-FQDN the default is

panel.mytop.tl but should be panel.mysub01.mytop.tl?

mysub01.mytop.tl
mysub02.mytop.tl
mysub03.mytop.tl
...
all have their different IPs each. Any further subdomain (e.g. vu2005.mysub01.mytop.tl) is covered through wildcards.
mytop.tl itself is unused. With the current behaviour all machines would get the same panel-FQDN.

Not severe as one can change this value.

Couldn't find whether it has been discussed so far. Suggestion is to add to the release page
https://github.com/i-MSCP/imscp/releases
a checksum file. People should get used to control installation files.

Thankyou very much @Nuxwin for your answers.

Doesn't seem too complicated and would be a good training. But lack of time makes the solution with the plugin a preferable one! I asume - as I read in other posts - the built in tools will let me build PHP7.0 as the secondary PHP-version.

Can s. o. confirm this:

Doing a completely new installation with Debian Jessie 8.5 and i-MSCP 1.3.0. I could remove the default php 5.6 Version and install php 7.0.8 from dotdeb repositories. Any finishing run (reconfiguration) of i-MSCP resulted in php 5.6 being reestablished again.

Q1: It would be OK to have php 7.0 as the only version, but this seems impossible currently?
Q2: The only solution to get php 7.0 at the moment is PHP-Switcher?
Q3: As is the case in Ubuntu: any plans when debian will have php 7.0 as default supported by i-MSCP?

Thankyou for your answers!

OT-Q4: Nuxwin Purchase possible with payment to IBAN? y/n

I just registered as a new user. In the registration form I noticed 1.2.17 as the highest version of i-MSCP. Mentioning 1.3.0 caused an error. Really brand new stuff!