I am using xampp v3.2.1 with PHP 5.6.8. now i want to use PHP APC caching techiniques but unable to use. can anyone please tell how shall i enable this caching on my xampp.
In short: when you are using PHP 5.6.8:
enable the Opcache
forget about APC
if you need a userland cache use APCu
Since PHP 5.5 the Bytecode-Cache "OpCache" is part of the core, making the APC extension itself useless. In other words: APC is only usefull for 5.4 and lower versions and those reached EOL.
Since PHP 5.5 there is the User Cache-Extension "APCu" as a replacement for APC.
https://github.com/krakjoe/apcu
Related
By default, Laravel will use the phpredis extension to communicate with Redis but We can install predis in application.
do I need to install predis in project? what is difference between phpredis and predis in laravel?
phpredis is a binary package and pecl extension for php.which makes it faster than predis.
but you need root permission to install phpredis extension.when you use some webhost that do not support customize environment,make it impossible to run you appllication.
on the other hand.predis use pure php code to communicate with redis server.so there is no local php extension requirements.but it's a little slower.
so you can deploy you application to any webhost that support php.
As I remember.laravel default use predis to make it minial requirements.
PhpRedis is a PHP extension for communicating with the Redis storage.
Predis is the alternative for PhpRedis on pure PHP and does not require any additional C extension by default, but it can be optionally paired with phpiredis.
I will recommend that phpredis provide a lot of better performance.
I am using Symfony 5.1.8 in an existing project and installed Api Platform, version 2.5.7:
composer req api
I added an #ApiResource() Annotation to one of my entity classes.
When calling the /api/ route there is always just a message saying "No operations defined in spec!". The problem does only occur on my dev system (php 4.7.11, macOS Catalina 10.15.6, xdebug... ). So I do not think it's a configuration problem...
When I deploy this to my testsystem (debian with docker containers) everything works as expected - there are shown 6 resources I can interact with.
I tried to update my composer dependencies, clear the cache several times, clear the cache folder... nothing of this helped.
When calling
bin/console debug:router
on my test system, I get all 6 resources. In my dev system there are no routes shown.
Do you have any ideas where to start debugging to better understand the problem?
What are further interesting details?
Edit:
It works in the dev system when changing the environment to "test". But I do still not have a clue, why...
regards
Stephan
I found the answer.
I am using redis for system cache, so the deletion of the cache folder (./var/cache) didn't help.
A normal cache:clear didn't help, too:
bin/console cache:clear
But a cache clear of the system cache did the trick:
bin/console cache:pool:clear cache.system_clearer
Does Magento 1.9.0.1 need php-redis extension for using Redis Cache?
I can't seem to be able to find the answer through google.
Edited: it looks like there is an option whether to use phpredis or standalone PHP
<force_standalone>0</force_standalone> <!-- 0 for phpredis, 1 for standalone PHP -->
Magento 1.9.0.1 comes along with Cm_RedisSession the way it is for magento 1.8. You need to have redis installed on your server, you need to have a PHP extension for interfacing with Redis. The details can be found at http://pecl.php.net/package/redis.
And you can refer to http://www.magentocommerce.com/knowledge-base/entry/redis-magento-ce-ee#config-mage for configuring redis.
i am using magento 1.3.2 3 changing server from 5.2php to 5.3 php will it effect the website
would there be any compatibility issues ?
hosting people:
As discussed on live chat we have migrated your all account from your VPS to new dedicated server.
Also, the OLD server has php version 5.2 ,cPanel is no longer providing support for php 5.2. Your server has php version 5.3. Please check if your all sites are compatible with the php 5.3 and let us know the convenient time period to change the nameserver IPs as bellow.
would there be issues with magento functionality ?
will it effect the website
Yes.
would there be any compatibility issues
Magento didn't support PHP 5.3 until version 1.4
would there be issues with magento functionality ?
Again, yes, but they're too myriad to list. Upgrading to modern version of Magento won't be a turn key project. Get a 5.3 server, practice moving your site and fixing all the bugs. Do it again. Keep doing it until you're ready to move your production system.
Trying to hash a password in laravel four using Hash::make('password'); and get the error Bcrypt hashing not supported. in return.
Mcrypt is installed and phpinfo() confirms this, what else could be wrong?
Debian 6.0 X64 with PHP 5.3.3-7.
The Laravel requirements are PHP >=5.3.7
You said you are running 5.3.3-7 - which is less than 5.3.7
Can you upgrade your PHP version?
As The Shift Exchange said, 5.3.7 is the minimum for a 'vanilla' Laravel 4, but there is at least one option, if you really cannot upgrade your PHP server. This one will drop the minimum PHP version for Laravel 4 to 5.3.2:
https://github.com/robclancy/laravel4-hashing
Before using it, weigh your security needs, because it will also drop the security level of your hashes.