New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PHP 5.4 requirement #170

Closed
spikewilliams opened this Issue Jan 25, 2014 · 7 comments

Comments

Projects
None yet
2 participants
@spikewilliams

spikewilliams commented Jan 25, 2014

According to the docs for tdt 4.0, PHP 5.4 is a prerequisite, whereas the docs for tdt 3.0 only required PHP 5.3. This is a problem for those of us running CentOS 6.x, which only supports PHP 5.3 out of the box.

What changed between tdt 3.0 and 4.0 that drove the change in requirement to PHP 5.4? Are there any known workarounds to get tdt 4.0 to work on PHP 5.3?

@coreation

This comment has been minimized.

Show comment
Hide comment
@coreation

coreation Jan 26, 2014

Member

Hi @spikewilliams, as far as we know tdt core will work on 5.3 as well as the docs. However, the phpunit testing will not as some php 5.4 syntax was necessary. Some workarounds have already been implemented for example 5.3 does'nt have a prettyprint in a JSON context, whereas 5.4 does, if no prettyprint function has been found, we've written a function that simulates it.

So you'll most likely be able to run it, as Laravel 4 needs PHP 5.3.7 >= , but since we're selling some SLA's on the datatank and need complete coverage, we mention 5.4 .

Member

coreation commented Jan 26, 2014

Hi @spikewilliams, as far as we know tdt core will work on 5.3 as well as the docs. However, the phpunit testing will not as some php 5.4 syntax was necessary. Some workarounds have already been implemented for example 5.3 does'nt have a prettyprint in a JSON context, whereas 5.4 does, if no prettyprint function has been found, we've written a function that simulates it.

So you'll most likely be able to run it, as Laravel 4 needs PHP 5.3.7 >= , but since we're selling some SLA's on the datatank and need complete coverage, we mention 5.4 .

@spikewilliams

This comment has been minimized.

Show comment
Hide comment
@spikewilliams

spikewilliams Jan 27, 2014

That's encouraging, though it seems that CentOS 6.x (and Red Hat Enterprise Linux 6, for that matter) comes with PHP 5.3.3, which doesn't meet Laravel 4's requirement for 5.3.7.

It seems that the use of the password encryption functionality in 5.3.7 is the only part of Laravel that is driving that requirement. However, there is a project that replaces the Laravel 5.3.7-specific code with something 5.3.3 compatible. I will look into that.

spikewilliams commented Jan 27, 2014

That's encouraging, though it seems that CentOS 6.x (and Red Hat Enterprise Linux 6, for that matter) comes with PHP 5.3.3, which doesn't meet Laravel 4's requirement for 5.3.7.

It seems that the use of the password encryption functionality in 5.3.7 is the only part of Laravel that is driving that requirement. However, there is a project that replaces the Laravel 5.3.7-specific code with something 5.3.3 compatible. I will look into that.

@coreation

This comment has been minimized.

Show comment
Hide comment
@coreation

coreation Jan 28, 2014

Member

Looks something that might help you with the PHP dependencies indeed, let
us know if that helps you to get the datatank running and we'll add it to
the documentation pages :).

On Mon, Jan 27, 2014 at 5:32 PM, spikewilliams notifications@github.comwrote:

That's encouraging, though it seems that CentOS 6.x (and Red Hat
Enterprise Linux 6, for that matter) comes with PHP 5.3.3, which doesn't
meet Laravel 4's requirement for 5.3.7.

It seems that the use of the password encryption functionality in 5.3.7 is
the only part of Laravel that is driving that requirement. However, there
is a project https://github.com/robclancy/laravel4-hashing%22 that
replaces the Laravel 5.3.7-specific code with something 5.3.3 compatible. I
will look into that.

Reply to this email directly or view it on GitHubhttps://github.com//issues/170#issuecomment-33385365
.

Met vriendelijke groeten,

Jan Vansteenlandt

Member

coreation commented Jan 28, 2014

Looks something that might help you with the PHP dependencies indeed, let
us know if that helps you to get the datatank running and we'll add it to
the documentation pages :).

On Mon, Jan 27, 2014 at 5:32 PM, spikewilliams notifications@github.comwrote:

That's encouraging, though it seems that CentOS 6.x (and Red Hat
Enterprise Linux 6, for that matter) comes with PHP 5.3.3, which doesn't
meet Laravel 4's requirement for 5.3.7.

It seems that the use of the password encryption functionality in 5.3.7 is
the only part of Laravel that is driving that requirement. However, there
is a project https://github.com/robclancy/laravel4-hashing%22 that
replaces the Laravel 5.3.7-specific code with something 5.3.3 compatible. I
will look into that.

Reply to this email directly or view it on GitHubhttps://github.com//issues/170#issuecomment-33385365
.

Met vriendelijke groeten,

Jan Vansteenlandt

@coreation

This comment has been minimized.

Show comment
Hide comment
@coreation

coreation Feb 2, 2014

Member

If you really run into troubles, here's a small tutorial on how to update ;). http://askubuntu.com/questions/343560/update-server-php-version-to-5-4-10-via-the-command-line

Member

coreation commented Feb 2, 2014

If you really run into troubles, here's a small tutorial on how to update ;). http://askubuntu.com/questions/343560/update-server-php-version-to-5-4-10-via-the-command-line

@coreation coreation closed this Feb 2, 2014

@spikewilliams

This comment has been minimized.

Show comment
Hide comment
@spikewilliams

spikewilliams Feb 3, 2014

After a bit of experimentation, I've manged to get TDT running on CentOS under PHP 5.3.3. I've documented the steps... what is the best way for me to provide the documentation to you?

spikewilliams commented Feb 3, 2014

After a bit of experimentation, I've manged to get TDT running on CentOS under PHP 5.3.3. I've documented the steps... what is the best way for me to provide the documentation to you?

@coreation

This comment has been minimized.

Show comment
Hide comment
@coreation

coreation Feb 3, 2014

Member

Hi @spikewilliams , great! Well to give you credit I think the best thing you can do is checkout our docs repository (https://github.com/tdt/docs). There you'll find markdown files that cover our documentation, and a section for known pitfalls has yet to be made, but is planned to be in the installation file.

So either you pass the documentation here on the issue tracker, or you add it to the 4.1/installation.md file in a "Pitfalls" section via a pull request to get more Git credit ;). Chances are I'll have to integrate it next to other pitfalls but at least you'll be on the git contributing list :).

Member

coreation commented Feb 3, 2014

Hi @spikewilliams , great! Well to give you credit I think the best thing you can do is checkout our docs repository (https://github.com/tdt/docs). There you'll find markdown files that cover our documentation, and a section for known pitfalls has yet to be made, but is planned to be in the installation file.

So either you pass the documentation here on the issue tracker, or you add it to the 4.1/installation.md file in a "Pitfalls" section via a pull request to get more Git credit ;). Chances are I'll have to integrate it next to other pitfalls but at least you'll be on the git contributing list :).

@coreation

This comment has been minimized.

Show comment
Hide comment
@coreation

coreation Feb 6, 2014

Member

Thanks @spikewilliam, we made some minor changes to your pull request, and added you after the overview of your tutorial page!

Member

coreation commented Feb 6, 2014

Thanks @spikewilliam, we made some minor changes to your pull request, and added you after the overview of your tutorial page!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment