Instalation in hostinger

donerak

I've been trying to install the forum package on a hostinger host for two days and I can't.. can someone please help me?

donerak

É um aviso que você precisa alterar algumas configurações, pois nem todos os pacotes foram atualizados.
Estes são os critérios que precisa checar, com os guias que devem te ajudar com isso:
Problem 1
- Root composer.json requires flarum/core ¹.2 -> satisfiable by flarum/core[v1.2.0]. > Problem with composer - Flarum Community

- flarum/core v1.2.0 requires php >=7.3 -> your php version (5.6.40) does not satisfy that requirement. >Help with PHP - Flarum Community

Problem 2
- flarum/tags v1.2.0 requires flarum/core ¹.2 -> satisfiable by flarum/core[v1.2.0]. > Cannot install Flarum
- flarum/tags v1.1.0 requires flarum/core ¹.1 -> satisfiable by flarum/core[v1.2.0]. > Cannot install Flarum
- flarum/tags[v1.0.0, ..., v1.0.3] require flarum/core ¹.0 -> satisfiable by flarum/core[v1.2.0]. > Issues on upgrading - Flarum Community
- flarum/core v1.2.0 requires php >=7.3 -> your php version (5.6.40) does not satisfy that requirement. > Help with PHP - Flarum Community
- Root composer.json requires flarum/tags * -> satisfiable by flarum/tags[v1.0.0, ..., v1.2.0]. > Cannot install with Flarum 1.0.0
Estas questões realmente fogem do escopo do nosso suporte, e precisam ser revisadas pelo teu lado mesmo!

luceos

donerak flarum/core v1.2.0 requires php >=7.3 -> your php version (5.6.40) does not satisfy that requirement.

Your php version is too old. You should upgrade it. It's now 5.6.40 (which isn't even supported anymore).

donerak

friend this version of php 5.6 is installed in the root. why my site doesn't run with another version. I need to install the forum in a subdomain and inside the forum folder it has php 7.4

I've been trying to solve this for days but I'm not a developer and I don't know how to work with linux.. please help me

luceos

donerak you can upgrade your php version from your control panel according to their help center: https://support.hostinger.com/en/articles/1575755-how-can-i-change-my-php-version

ps this has nothing to do with "being a developer", and everything with "being a webmaster".

donerak

luceos my sub has php 7.4

donerak

I know, but when I do this my site doesn't work all the features. and I need to use a subdomain for the forum.

donerak

![https://media.discordapp.net/attachments/360670804914208771/950524239478403132/unknown.png?width=871&height=468](https://)

luceos

Probably when you use composer it uses the default php version. Maybe you can use php74 composer instead of composer. To know for sure you might need to get help from Hostinger support.

010101

luceos Is this new since 1.0 or 1.2 that Flarum forces a certain php version when using composer? I don’t recall this being an issue in the past but I’m noticing it more.

With shared hosting this could end up being an ongoing issue. Many times you can set your php version to 7.4 or 8+ at the directory level. So Flarum will run just fine once installed. But shared hosts sometimes use a lower version of PHP with their SSH / command line access. And, shared hosts won’t usually change that. Or at least not quickly.

I know, “get another host,” but it’s not a reality everyone can make happen.

I don’t think there should be such strict constraints at the composer install level.

I had a similar issue with the Blomstra quick sort extension. It won’t install even though I’m using PHP 8, because my host uses 7.4 wherever their SSH is set up which then blocks the install. And using php8 composer also will not work with all hosts.

It would be better to not rely on composer as much, let the install happen, but have Flarum show an error in the admin that the php version is too low. Because with situations like this person’s and mine, the install then would be successful and everything would work as long as the php version in the directory where core is installed is high enough.

luceos

010101 Is this new since 1.0 or 1.2 that Flarum forces a certain php version

Flarum has always had specific PHP requirements. It is slowly going up now because PHP is actively being developed on and abandoning older versions (see https://www.php.net/supported-versions.php); 7.4 only gets security patches now. This means older versions cause you to be vulnerable to attacks.

010101 forces a certain php version when using composer

Composer is a dependency manager. It checks what you need and whether your platform/server supports it. It warns you - ahead of trying to run your software - whether your server isn't compatible. You can use the --ignore-platform-reqs to force installation regardlessly.

010101 But shared hosts sometimes use a lower version of PHP with their SSH / command line access.

Them not allowing specific versions with SSH/cli is a bad thing. Especially with the speed new PHP versions come out. Unless these hosting providers run some kind of custom platform, not being able to set your PHP version for your website and SSH should be a thing of the past. I've worked at a hosting company over 5 years ago and back then this feature was already wide spread!

010101 I don’t think there should be such strict constraints at the composer install level.

Actually composer does a perfect job. It downloads packages compatible with your php version and operating system. It glues together the foundation that is Laravel, Symfony and many other packages for use on your specific hosting plan; without any fuss. If you'd forsake that, the risk of running into errors (even silent ones) are pretty high, especially when the PHP version difference is a major one (5.x 7.x 8.x).

010101 And using php8 composer also will not work with all hosts.

It doesn't. That's why you can ask your host how to install using composer for different php versions. Or use the flag given above at your own risk.

010101 It would be better to not rely on composer as much, let the install happen,

You cannot install without composer. It understands dependencies and dependencies of dependencies for packages. For instance when installing Flarum it will load flarum/core, check which version of core is compatible with your OS and PHP version. It will download Laravel and Symfony packages that core includes and runs exactly the same checks. Laravel and Symfony also have dependencies, like Flysystem. Well.. you see what is happening? How exactly do you propose these downloads happen without using composer?

010101 Because with situations like this person’s and mine, the install then would be successful and everything would work as long as the php version in the directory where core is installed is high enough.

Your hosting provider should offer a way to configure PHP versions on the webserver level and on the SSH level. This was possible years ago and is widely available in software like CloudLinux, DirectAdmin, CPanel and many more.

You cannot and should not criticize maintainers for providing you with secure software.

010101

luceos Interesting. Your reply gets into a lot about composer almost to an offensive level. I know what composer is.😄

I’m focused on PHP versions and SSH, and how many shared hosts do things, not what composer is or the basics around how it works. I’m simply suggesting this one line should be changed. I’m not saying get rid of composer or make major changes. You answered my questions when you offered the command that forces the install. I suppose I would use that if needed.

You shouldn’t criticize a long time user for expressing opinion that y’all are making Flarum harder to install versus easier. Going the opposite direction. I wasn’t criticizing you or the developers. I was giving you a shared hosting user’s opinion. An opinion which could help to prevent y’all from seeing this same question over and over and over.

You can have super secure software, but have PHP warnings after install. Make the site unusable, after install. Then you still have secure software. And you are accommodating a large group of website owners who can’t control their SSH set up.

Step 1: Install with a much lower PHP constraint in composer.json or no constraint. Step 2: User sees: Sorry, update PHP to use Flarum. And nothing works, site is down, until they update.

Everyone should be less sensitive and work together. This means even considering the evil (sarcasm) shared hosting users.

Slowly I think (hope) most decent shared hosting providers are understanding and updating this stuff faster. But, SSH access alone is a somewhat new offering for shared hosting. Probably for security reasons on their end. Now, we finally have shared hosts with SSH access, but now users are realizing the host will update PHP everywhere, except wherever/however composer is installed.

SychO

010101 I think you're misunderstanding what @luceos tried to explain, there seems to be some confusion about what the PHP constraint is for. Allow me to further elaborate.

It can't be changed just for the PHP used in SSH to work by default, because that's not what it is for. We set the PHP version in composer.json so that composer downloads dependencies that are compatible with the PHP versions that Flarum operates on. Flarum does not work on older PHP versions, so that is necessary otherwise the software would not properly work, and supporting older versions is a major change that would be a very bad decision for the project.

However, that is not to say that the issue you're referring to is not a problem. Different PHP versions used in SSH and web configuration and platform requirement being checked based on the PHP version in SSH is certainly an undesirable and annoying effect, which hopefully our future efforts in the 1.x roadmap will help with improving if it allows us different installation methods, and as you pointed out having constraints displayed on the installation UI instead would be a lot more user friendly.

010101

SychO Ok. Makes more sense I suppose when you put it that way. I don’t understand why composer can’t do it another way. In my mind there are always other just as secure ways to do things. I wonder if composer has other ways of setting up the composer.json file to make everyone happy? But, I guess not; this may be composer’s limit.

So, as a basic example, are you saying that composer will allow symfony to install even if you don’t have the right PHP, if that PHP constraint wasn’t there?

I also think maybe developers think at a highly technical level and might miss my point(s).

We keep saying, Flarum won’t work at lower versions of PHP.

True.

But, usually, shared hosts let you change the PHP version where it matters. Where Flarum will live after install. They just haven’t yet gotten to the point where they let you change it other places like where composer lives.

It’s just another “oh well,” “it is what it is,” moment. I will have to remember that force command as needed. This is free software, developers work very hard on it. And that’s all there is to it. A couple shared hosting users’ opinions won’t change anything.

I shall return to my corner and be quiet. 🤐🙂

luceos

010101 the php version (binary) you install Flarum with using composer implies the version Flarum runs as. A discrepancy between these versions can and - as pointed out between major versions - will cause errors.

PS Billy it's the sole responsibility of the shared hosting companies to offer flexibility of php versions. Not doing this under the current circumstances is not just a lack of foresight, but also poses a risk to client data. Even offering PHP 5.x without a clear warning about the risk involved, is pretty offensive. That a hosting provider in 2022 does not provide clear instructions on how to use PHP in a hosting plan is disappointing to say the least.

SychO

010101 A couple shared hosting users’ opinions won’t change anything.

I shall return to my corner and be quiet. 🤐🙂

Not quite, shared hosting users have been voicing their problems with composer on shared hosting, and we really have been listening, we are aiming to get to a stage where users won't have to use the composer command line and have been working towards it. These things just take time, unfortunately.

But I hope people will not stop voicing their opinions when they feel like it, it is important for the software's continuity.

010101

luceos That a hosting provider in 2022 does not provide clear instructions on how to use PHP in a hosting plan is disappointing to say the least.

They usually do, just not when it comes to composer since traditionally they didn’t offer composer at all. They give instructions on how to update PHP. Just not where they have composer installed. Maybe because it’s shared so it’s not easy to change it. Not sure. I’ll ask my host.

010101

SychO we are aiming to get to a stage where users won't have to use the composer command line and have been working towards it.

But, I like using composer. Even with shared hosting. This whole thread was more about whether or not there's a way to still use composer. There is with an extra force command. But, I wish there was a better way. Sounds like it's impossible. Composer can only detect the PHP version where it is installed. So, now I know.

Maybe this will be a composer 3 feature. Somehow look for the php version where things are being installed.

010101

Turns out my host does have a special command, different from php8 composer or php74 composer to force usage of a different PHP version.

I just had to ask them.

It's like this (although just in case it's a security risk of some sort I'm changing parts):

/fun/places/php8/go/php-cli composer

In my defense, so many times in the past web hosts have not always had solutions when it comes to composer so I gave up asking them. Turns out I probably just need to ask them more. 😀

In short for anyone else, ask your web host. If they are decent, they'll have a solution (besides forcing the install).