Posts by theprincy
-
-
exactly!
it is not only about a fork, you can just fork it on github and go on. but to maintain a project, there is a lot more to do. in first place the organization and management.
most OS projects fail not because for lack of code-contributions, but because for lack of organization and a solid leadership. as far anyone can bring that in, there will be no successful fork.
so in your opinion if there is an organization now here, can the project continue to grow? but who puts the code? oorganizing the thing it takes very little the problem for coem I see it is who develops
-
So in the end after all these complaints no decision? whether to create a "fork" whether to create a new GIT where everyone can work to create a new 2020 or 2021 version by inserting the various corrections ... nothing? it just complained that it does not respect what it says that it has not released anything it is not doing anything ... in light of that I too would have done the same if I have no support from the community
-
a question: does the comunity exist? did it exist? I do not personally believe that we still have time to recover everything whether it is an open project or not, just give yourself a guideline and talk to Laurent in a peaceful way without creating fuss and giving a new course to imscp or whatever it will be called in the future
-
I think that we all have a small responsibility for where the project has ended, the code is present on github, there are corrections, bugs to correct well let's start making them or marking them in the forum let's not complain only that Laurent is absent and does not care to the project. Unfortunately not all of us are developers but we can all help to ensure that the project does not die, it is unique that in two years it has remained "stable" and functioning.
As we all have seen alternatives more or less valid but if we are still here it means that we believe in the project so we do our small part we make the latest version 100% compatible with the latest versions of debian / ubuntu at least and the rest will come by itself, because more than a community I see people who think only of if not the project .. in my opinion this is what Laurent is seeing here in the forum, it takes very little for things to change and the project resumes living as it did two years ago ..
-
I don't know if it's the wrong section but the site https://wiki.i-mscp.net gives as error Error 526 Invalid SSL certificate
-
Do you have some news about this plugin?
Thank you.
-
I installed the php 5.6 7.1 7.2 7.3 7.4 versions in the db in the php_switcher_version table I see the configuration of the various versions of php, in the control panel of the plugin comes out "Bad Request", while in the domain management I see all the php version available but not are selectable, if I re-run the configuration it exits
perl /var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler/php_compiler.pl --zts --packaged --register 5.6 7.1 7.2 7.3 7.4
[INFO] Registering PHP versions in the PhpSwitcher plugin...
[INFO] Registering the packaged PHP 5.6 version with data:
- PEAR directory path : /usr/share/php
- FastCGI binary path : /usr/bin/php-cgi5.6
- FPM binary path : /usr/sbin/php-fpm5.6
- FPM configuration file path : /etc/php/5.6/fpm/php-fpm.conf
- FPM pool directory path : /etc/php/5.6/fpm/pool.d
[INFO] Registering the compiled PHP 7.1 version with data:
- PEAR directory path : /opt/phpswitcher/static/php7.1/share/pear
- FastCGI binary path : /opt/phpswitcher/static/php7.1/bin/php-cgi
- FPM binary path : /opt/phpswitcher/static/php7.1/sbin/psw7.1-fpm
- FPM configuration file path : /opt/phpswitcher/static/php7.1/etc/php-fpm.conf
- FPM pool directory path : /opt/phpswitcher/static/php7.1/etc/php-fpm.d
[INFO] Registering the compiled PHP 7.2 version with data:
- PEAR directory path : /opt/phpswitcher/static/php7.2/share/pear
- FastCGI binary path : /opt/phpswitcher/static/php7.2/bin/php-cgi
- FPM binary path : /opt/phpswitcher/static/php7.2/sbin/psw7.2-fpm
- FPM configuration file path : /opt/phpswitcher/static/php7.2/etc/php-fpm.conf
- FPM pool directory path : /opt/phpswitcher/static/php7.2/etc/php-fpm.d
[INFO] Registering the compiled PHP 7.3 version with data:
- PEAR directory path : /opt/phpswitcher/static/php7.3/share/pear
- FastCGI binary path : /opt/phpswitcher/static/php7.3/bin/php-cgi
- FPM binary path : /opt/phpswitcher/static/php7.3/sbin/psw7.3-fpm
- FPM configuration file path : /opt/phpswitcher/static/php7.3/etc/php-fpm.conf
- FPM pool directory path : /opt/phpswitcher/static/php7.3/etc/php-fpm.d
[INFO] Registering the compiled PHP 7.4 version with data:
- PEAR directory path : /opt/phpswitcher/static/php7.4/share/pear
- FastCGI binary path : /opt/phpswitcher/static/php7.4/bin/php-cgi
- FPM binary path : /opt/phpswitcher/static/php7.4/sbin/psw7.4-fpm
- FPM configuration file path : /opt/phpswitcher/static/php7.4/etc/php-fpm.conf
- FPM pool directory path : /opt/phpswitcher/static/php7.4/etc/php-fpm.d
[DONE] PHP versions scheduled for update:
- PHP 5.6 (Packaged)
- PHP 7.1 (Compiled)
- PHP 7.2 (Compiled)
- PHP 7.3 (Compiled)
- PHP 7.4 (Compiled)
Default PHP Version in use: 5.6.40-14+0~20191128.24+debian9~1.gbpa5b195
I-MSCP Version: [tt]i-MSCP 1.5.3 Build: 2018120800 Codename: Ennio MorriconeOS: Debian 9.11 stretch
Phpswitcher Version: Current 5.0.5Additional PHP version installed from package and used in phpswitched 7.1 7.2 .7.3 .74
the plugin log does not report errors
I also ran the "perl /usr/local/src/imscp-1.5.3/imscp-autoinstall -a -s -r httpd" command but without result
Edit : I restarted the server and gave the command above "perl /usr/local/src/imscp-1.5.3/imscp-autoinstall -a -s -r httpd" and the problem was solvedcommand but with no result
How can I solve the problem ?
P.S : image error2.png is old file -
I did coem it was written in the guide but I haven't solved anything, always the same problem . in order to use the domains I have to change domain_status and restart the imscp configuration
-
no new installation via download template from proxmox, the version is the
proxmox-ve: 6.0-2 (running kernel: 5.0.18-1-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)